After installation, the Orchestrator Resources folder displays only the JDBC JAR files that were added during installation. After you use the Manage User Resources palette to update the Orchestrator Resources folder, the Orchestrator Resources folder also displays the uploaded JAR files.
You can upload a JAR file to the Orchestrator Resources folder on the Domain Orchestrator. When you restart the Domain Orchestrator, CA Process Automation deploys the file to the Domain Orchestrator. The Domain Orchestrator mirrors (copies) the file at the configured mirroring interval, after which you restart the other Orchestrators. When the Orchestrators restart, the mirrored file is available for their use.
Note: Mirroring applies to all Orchestrators in the domain. For clustered Orchestrators, mirroring applies to all nodes in each cluster.
Follow these steps:
The Add New Resource: "Untitled" pane opens.
The following example is a reasonable way to specify the resource name if you are uploading a JDBC driver:
database_name Driver
Defines the name of the RDBMS. For example, Oracle Driver, MySQL Driver, or Sybase Driver.
A line with your entry displays.
CA Process Automation copies the uploaded resource to the following paths:
install_dir/server/c2o/ext-lib
install_dir/server/c2o/.c2orepository/.c2oserverresources/lib
Defines the directory on the server where the Domain Orchestrator was installed.
When the Domain Orchestrator restarts, the system deploys all jars that you uploaded to the Domain Orchestrator Resources. That is, CA Process Automation puts the jars in the classpath of the Domain Orchestrator.
The system deploys all uploaded jars to all Orchestrators. That is, the system puts the jars in the classpaths of the Orchestrators.
Note: For clustered Orchestrators, restart each node.
Copyright © 2014 CA.
All rights reserved.
|
|