Pre-Generation Tasks › CA Gen Java Runtime/User Exits

CA Gen Java Runtime/User Exits

CA Gen provides a Java Runtime and User Exits to support the generated Java code. There are two ways of deploying the Java Runtime and User Exits:

• Place the CA Gen Java Runtime and User Exits in each EAR file. This allows each application to have its own copy of the runtime and user exits. However, should the runtime need to be PTFed, or if a change is made to the user exits, then each application must have its EAR file updated and redeployed.

  Note: Some application servers do not support this option.

• Place the CA Gen Java Runtime and User Exits in a common location on the application server, such as the …\lib\ext directory. This simplifies the process of PTFing the runtime or updating a user exit for all applications on an application server. However, this option usually requires a restart of the application server in order for the change to take effect.

In either case, the CA Gen Java Runtime would be PTFed or the User Exits would be updated on a Windows workstation and then moved into the application's EAR file or the application server. Therefore, you should put controls in place to manage the configuration of the CA Gen Java Runtime and User Exits over the life of the application.