New Features › CA Process Automation Release 04.2.00 › Java-Related Improvements

Java-Related Improvements

Summary

• Document JavaScript functions that return Java types
  • Formerly, we did not document JavaScript functions that return Java types.
  • Now, the Content Designer Reference contains the topic, "Return Types." For each system function return type, a table describes the effect on a Javascript variable being assigned the return value, and the CA Process Automation dataset variable type created.
• Invoke Java operator changes and enhancements.
  • Formerly, you could execute the Invoke Java operator on an Orchestrator or on an agent. The Invoke Java operator uses custom Java code. Administrators want to prevent the execution of any custom code that could corrupt the Orchestrator or that conflicts with its execution.
  • Now, the Invoke Java operator can only be executed on an agent. A new Required Main Method dialog provides a coding example that you can copy into the area that the operator uses. The example provides directions for usage.

Details

Previously, the Invoke Java operator could be run on Orchestrators. For security reasons, this operator can now be run only on agents. This change prevents the running of custom code that could inadvertently corrupt CA Process Automation components. See Where Operators Can Run in the Content Designer Reference.

For existing processes that include an Invoke Java operator that targets an Orchestrator, change the target so that the operator runs on an agent. If you require the operator to run on the host where the Orchestrator runs, we recommend that you install an agent for this purpose on that same host.

We recommend that you install a dedicated agent on another host and run any Invoke Java operator that is used in new processes on this dedicated agent.

A new example panel has been added inside the Required Main Method text area of the Invoke Java operator. You can display or hide the example with a click of the Hide Examples button. The MyAccount.jar file is required to run the provided java example. The installation or upgrade process adds the MyAccount.jar file to User Resources (located in the invoke_java_op_example_jars folder) in the Domain Orchestrator. CA Process Automation then mirrors the MyAccount.jar file throughout the other nodes in your system. See "Resource for Running Invoke Java Operator Example" in the Content Administrator Guide.

The Use Strict Java Mode? input field is no longer in the Invoke Java operator, but was moved to the Utilities Module properties. The new Invoke Java operators use the value that is configured at the module level. Any Invoke Java operators that you created with CA Process Automation releases before Release 04.2.00 retain this input field. The value of this field dictates whether the operator uses Strict Java Mode.

Other UI changes include:

• The Invoke Java operator has new labels and detailed tooltips that explain the use of each field.
• The tab on the module properties for the Utilities module was changed to Default Invoke Java Operator Properties.