GuardIEn automates the updating and implementation of changed objects into a target environment, including the updating of the executable system.
The steps required to implement a system will vary between organisations. Typical steps include:
GuardIEn executes the steps using a series of linked background tasks. It executes each step, checks the results and if the step was successful, automatically moves on to the next step. This allows the update to be performed overnight without any intervention. Contrast this with a manual process whereby each step has to be performed individually, probably split over several days to allow for example the completion of one step before defining and executing the next step.
The figure below provides an example of how the GuardIEn system updating process can automate some typical steps in a production update. It can first update the test libraries. Once the testing is complete, the objects are migrated to a controlled acceptance model. The acceptance model can be secured so that only GuardIEn has access to it, signified in the figure below by the brick wall. The code is then regenerated and installed into acceptance to guarantee that the model is synchronised with the source and object code. Once acceptance testing is complete, the changes can be implemented into production, either by GuardIEn or by existing production updating routines invoked by GuardIEn. This is followed by a migrate to the production model to synchronise the production model with the production code
GuardIEn supports installing the generated code on the encyclopaedia server or a remote server. For remote installation, the code is generated on a CSE and installed on a separate machine. Many different configurations are supported, for example from a Windows or UNIX CSE, code can be installed on MVS, UNIX, or Windows machines.
Interfaces to Other CCM Tools
Many organisations have a desire to implement a single change and configuration management (CCM) solution to control applications, irrespective of the development tool, language, operating system and hardware.
There are a number of issues to be considered when attempting to control CA Gen projects with a source code based CCM tool:
Many attempts to interface source based configuration management tools to CA Gen have therefore faltered due to the inherent difficulties of interfacing a tool designed to work with 'traditional' source, object and control code with the model-based architecture of CA Gen.
GuardIEn contains interfaces to the most popular CCM tools, like Endevor, Harvest, ChangeMan and ISPW. The interface shields the CA Gen developers from these CCM tools and issues surrounding synchronisation whilst ensuring that the CA Gen projects adhere to site standards for implementing applications.
Further details on the specific CCM interfaces can be obtained from the Brochures page.