Promoting Resources to Servers (deployment)

Promotion describes the act of moving different resources (mainly objects and Projects) into a server environment that can be used for testing or production-ready integration with external servers. The Studio provides two methods to promote resources – either locally or remotely.

Method Description

(Scenario Deployment)

Describes object promotion to the Local Test Server environment within the Studio. While the server may be started using a default install license, it does require a Studio license to actually test scenarios.

The purpose is to test individual processes as part of your solution design. Business Processes and related top-level objects are the primary units of promotion in this case. Top-level objects are:

  • Configuration objects that invoke a Business Process – namely: Monitors (File, Database, Email Receive), Web Service Providers, Message Filters, Events, Inbound EDI Routes, and Outbound EDI Routes
  • Business Processes that are not invoked by a top-level object as defined above

Dependencies for all explicitly deployed top-level objects are calculated, and those dependent Clarify objects are deployed along with the top-level objects when the Local Test server is started. So, explicitly deploying a Business Process implicitly deploys objects such as a Ruleset, input and output Adapters, Code Tables, etc.

Note: Global Variables, Control Number Generators, and Next Numbers are promoted automatically and not subject to the local method.

(Remote Server Deployment)

Describes Project promotion to a remote Server at the Project level. Projects are bundled and then deployed in their entirety, and all dependencies between other Projects must be satisfactorily resolved.

Remote promotion may require special licensing, depending on the type and number of remote servers being used.

All methods of promotion take place in the Admin Console/Projects View.