Help
Deployment
Help menu
- Help content
- AS2
- Examples and Tutorials
- IO Queues and Forms
- Maps
- Schemas
- Send and Receive Ports
- Send and Receive Ports / Transports
- Servers
- Static Configuration
- Tracking
- Workflows
- Workflows / Workflow Activities
- Call Web Service Direct Activity
- Compensatable Sequence Activity
- Compensatable Transaction Scope Activity
- Compensate Activity
- Conditioned Activity Group
- Database Activity
- Delay Activity
- Event Handling Scope Activity
- Event Driven Activity
- Expression Activity
- Fault Handler Activity
- If Else Activity
- Increment Activity
- Invoke Web Service Activity
- Invoke Blue Integrator Workflow Activity
- Invoke Workflow Activity
- Listen Activity
- Map Activity
- Parallel Activity
- Policy Activity
- Send Receive Port Response Activity
- Replicator Activity
- Send Receive Port Response Activity
- Send Port Message Activity
- Sequence Activity
- Suspend Activity
- Synchronization Scope Activity
- Transaction Scope Activity
- While Activity
Blue Integrator has a number of features facilitating safe and easy deployment :
- The centralized configuration model means that changes made become live across all Servers as required without machine-by-machine action being required.
- Assemblies referenced by the solution can be stored in the configuration store (via the Blue Integrator Explorer, Static Configuration | Assemblies tree node), and will be loaded automatically from this store by all Servers as required. For example if your VSTA code or custom Functoid references a third-party assembly, you can register it here to avoid having to install it physically on all machines.
- Individual Blue Integrator Servers can also be flagged to ‘Use Deployed Versions rather than Latest’. Schemas, Maps and Workflows can all be Deployed via the Blue Integrator Explorer, that is a particular version can be specified as the deployed version. Where a Server has this flag set, it will only use the deployed versions (where they exist). Hence a release Server can be configured to carry on running a known version whilst developers and testers work on a modified version.
- A selective and intelligent import/export feature allows for moving data between physical deployments where it is desired not to have a common configuration store.