Software Change Management for Computer Associates
CA Plex
CA Plex is a multi-platform, model-based, architected rapid application development tool. Develop applications in a Windows environment and then compile and test them in the target environment, which might be Windows/.NET, Java/J2EE or IBM i. CA Plex supports the development of many different types of applications, including client/server, web-based, service-oriented, character-based, batch, and wireless device-based, all from a single set of skills and development techniques.
TD/OMS CA PLEX INTERFACE
The CA Plex development process on the IBM i platform is fully supported by TD/OMS, Remains Software's change-management solution. The TD/OMS CA Plex interface enables you to manage your application development life cycle. By managing important information items such as incidents, change requests and tasks, you are able to control the various aspects of application development. CA Plex-TD/OMS works for all your CA Plex software components: native i OS and PC components.
CA 2E
The solution allows work in the CA workbench and, when needed, access to desired functionality in TD/OMS. The 2E object registration and management is supported on the local side of a TD/OMS installation, i.e. the development platform where all the TD/OMS administration is done. The 2E objects are never an active part of the distribution to a remote machine or partition of an IBM i. Once a TD/OMS application is configured to work with the 2E interface, TD/OMS functions will work with the 2E definitions as if they are standard IBM i objects.
TD/OMS CA 2E INTERFACE
Using the solution, the CA 2E definitions and specifications are registered in TD/OMS as objects and they can be copied from one 2E model repository to another. While changing the CA application, TD/OMS informs other developers that the component is already locked in the maintenance cycle and prevents overwriting the changes. When the TD/OMS task is started, the associated IBM i components will be selected automatically, which makes it easier for developers to manage the change.
Regardless of whether users work with new or existing components, both types are automatically checked to development (start) stage in TD/OMS. This significantly reduces time needed for the work which previously required manual effort.