Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The startApplication operation starts a stopped Mule Application. It can be used in build or deploy workflows.

This operation is compatible with the following types of servers:

Server TypeNotes
CloudHub
Anypoint Runtime Manager
Runtime Agent
StandaloneThis operation should run on the Mule server where the project will be started.

Environment/Instance Properties

Property Name

Property Code

Required

Description





Project Properties

Property Name

Property Code

Required for which server Types

Description


FDMULE_APP_NAME

All



FDMULE_HOMEStandalone

FDMULE_USER


FDMULE_PASSWORD


FDMULE_TYPEAll

FDMULE_ORG_NAME


FDMULE_ENV_NAME


FDMULE_TIMEOUT


FDMULE_TARGET_TYPE


FDMULE_TARGET_NAME


FDMULE_STATIC_IPADDRESS

Inputs

Input Name

Input Code

Required

Description

Mule Project PathFDMULE_PROJECT_PATHNoThis is the folder that typically is named for your application and contains your [src] folder. Relative paths are sourced from the FD_TEMP_DIR.
http.portFDMULE_HTTP_PORTNo

HTTP port to use when running JUnit tests. This should be a different number than the one that is usually used to run the application on the server. This only works if
${http.port} is used in your HTTP Connector.

Outputs

Output Name

Required

Description




Artifacts

This operation produces artifacts that will be stored in the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.


  • No labels