Installation in a First-level Production Environment

The first-level production, or pilot, phase is the second step in rolling out a successful Synapta Services Builder implementation. In this phase, the scope is broadened — design-time tasks have been completed and development is no longer bound to a Windows environment.

A first-level production environment is distributed across separate servers. The run-time, MCS, and design-time components have been separated. However, it is likely that only one instance of Synapta Services Builder is running.

Workflow

  1. After receiving the necessary files from the developer, the system administrator deploys tasks to a single production Runtime Service and, optionally, to MCS.

  2. The system administrator verifies the accuracy of the configuration files.

  3. The system administrator and developer work together to verify that the newly published system is working.

  4. The system administrator monitors and logs information via a production version of MCS, accessing the MCS user interface through a supported browser in a Windows environment.

Configuring the Pilot Environment

During the pilot phase, you can have multiple remote Runtime Services, all pointing to a single MCS server. This server can act as a repository for the tasks recorded during design-time.

In the following diagram, the pilot phase is using two servers, both with the same configuration as was used in design-time. The implementation is confined to two regional offices to verify that the tasks and management configurations are in place and working correctly.

This diagram could illustrate a pilot phase for a production environment in which the number of offices served could be increased to many regional offices and several thousand individual clients. Of course, the pilot phase you use depends on your particular business needs.

First-level production or pilot environment

Related Topics
Bullet Installation
Bullet Installing in Windows
Bullet Installing in UNIX
  Attachmate