Guidelines for All Clarify 3 Servers

1. Business Processes with parameters cannot be launched, as there is no mechanism for manually entering a value for parameters. In order to launch a Business Process with a parameter, you must encapsulate parameters in another Business Process that assigns them value.
2. File Monitors, Database Monitors, and Web Services are started/stopped in the Resource Monitors view.
3. The results of an executed process are viewed in the Auditor view.
4. Active Projects in your Workspace are available for deployment when a server is started.
5. The Projects view displays a list of all EBI objects deployed on the server. It also displays deployment errors, which can be very useful when troubleshooting issues on the Local Test server. It’s a good indicator that something in your Workspace may need to be cleaned.
6. Avoid hard-stopping servers. However, if you shut down the server in an untraditional manner (such as from the Task Manager in Windows or the ps command in Linux), the server notifies you of the occurrence and suggest you re-build your Workspace. You can also delete and rebuild the runtime workspace on the Projects view.

**Source: Cleo documentation: EBI v2 to v3.1 Conversion Guide.pdf

Guidelines Clarify Test (QA) Server

1. Disable the communication paths to your trading partners. Instead, use the file system to test your solution’s output.
2. Save the environment’s Workspace in SVN as the test environment. The test and production Workspaces should not be the same Workspace.

**Source: Cleo documentation: EBI v2 to v3.1 Conversion Guide.pdf

Guidelines Clarify Production Server

1. Ensure that communications to your trading partners are enabled.
2. Save the environment’s Workspace in SVN as the gold version of the implementation.
3. When deploying Projects from the Workspace to the production environment EBI Server, use the Projects view’s Repositories section. Create a Local Repository and deploy from there. This creates an additional back-up of your environment on the local machine.

**Source: Cleo documentation: EBI v2 to v3.1 Conversion Guide.pdf

Guidelines Clarify Local Server

1. Don’t start the Local Test server immediately after starting CLarify Studio. Instead, only start it when ready to test. Then, all EBI objects are implicitly deployed. This ensures that all are deployed simultaneously, instead of piece-by-piece as each is created.
2. Ensure that the Local Test server isn’t started while converting objects from EBI v2 and when checking out objects from a SVN repository.
3. Global Variables are automatically updated in the Local Test server when modified in Clarify Studio.
4. Before starting the Local Test server, close Projects that contain invalid objects or objects that aren’t ready for development testing. Valid Clarify objects automatically deploy, but are unusable if referenced objects are not valid. For example, a Business Process that references a Ruleset with a reference to an invalid Schema.
5. Run the Local Test server in debug mode to assist with troubleshooting integration projects.
6. If you experience deployment problems or are missing expected objects, use the Project | Clean option from the main menu to rebuild the Project’s objects.
7. Once you are satisfied with the results of the local testing, save your Workspace to SVN and then deploy it to a remote test server.

**Source: Cleo documentation: EBI v2 to v3.1 Conversion Guide.pdf