Deployment Overview

Delivering the package to the runtime environment

An integration package contains the business process metadata that the engine uses at runtime. Each package contains one or more business processes associated with a project. After the design of the business processes is complete and the package is created, it is delivered to one or more runtime instances on the runtime server.

Configuring the package for the runtime instance

Binding each service endpoint used in the business processes to a physical resource (database, transport, or Web service port) is required. Ports types are associated with a service during design time. Ports are defined during design or after the package is delivered to the runtime instance. The Server Explorer is used to bind the endpoints to the physical resources used at runtime. The endpoint specified in the package and the port identifying a physical resource MUST be the same. Otherwise, the runtime engine will be unable to communicate with the external systems.

Runtime instance configuration includes updating configuration properties that are specific to the runtime instance, such as logging levels, error transports, and tunable performance parameters and defining input transports. If any database services are included in the package, modification to connection pooling defaults is available. For each service receiving inbound data, default performance parameters are available for modification.

Deployment Overview

Deployment is the process of transferring application metadata from a design-time environment to a runtime environment. Deployment steps are performed from the Orchestration Administration perspective of Unwired Orchestrator.

After deployment prerequisites are complete, the package is ready for deployment to the runtime instance. During the deployment of the configured package on the runtime instance, the agent converts the metadata that makes up the business process into the proper runtime format and stores the configuration data.