Cycle Installation
Agent
The steps for setting up Cycle Agent are very similar to the steps for setting up OIPA. Follow the OTN documents "WebLogic Deployment Installation Instructions" for WebLogic and the "WebSphere Deployment Installation Instructions" for WebSphere. Only the differences in the setup are given below.
- Modify any necessary configuration files as outlined in the Configuration section.
- cycle.properties – Refer to the Agent Cycle.properties section above for the properties related to the Cycle Agent.
- cycle-coherence-config.xml – This file controls the coherence cluster. Do not alter this file unless you have an in-depth understanding of coherence. The information in this file is based on how the installation was performed. The well-known-address is how you specify what machines are allowed to join the Cycle cluster. If you try to access a machine/IP address which is not in the cluster, you will get an error.
- cycle-coherence-cache-config.xml – This is a default file that defines how coherence caches are configured in terms of best practices.
- Copy these property files into the conf directory.
- Instead of creating an OIPA Server, create a Cycle Server.
- Use the Cycle Agent war instead of the PAS Java war. For WebLogic use CycleWeb-weblogic.war instead of PASJava-weblogic.war and CycleWeb-websphere.war instead of PASJava-websphere.war.
- The coherence file names in the JVM arguments for cycle agent are different from that in OIPA. The arguments must contain the path to the config files. The following is an example of the arguments:
-Dtangosol.coherence.override=./conf/cycle-coherence-config.xml -Dtangosol.coherence.cacheconfig=./conf/cycle-coherence-cache-config.xml
- The application Portable Object config file must be specified as a JVM argument. The Portable Object config file is packaged with the application, and describes the portable object setup. The argument should not include a path to the Portable Object config file, as it is packaged in an application library and available on the class path. The following is an example of the Portable Object config argument for a Cycle Agent:
-Dtangosol.pof.config=com-adminserver-cycle-agent-pof-config.xml
- The complete JVM startup arguments for the container might look like:
-javaagent:/opt/Environments/spring-instrument-4.3.10.RELEASE.jar -
Dtangosol.coherence.override=/opt/Environments/cycle-coherence-config.xml -Dtangosol.coherence.cacheconfig=/opt/Environments/cycle-coherence-cache-config.xml -Dtangosol.pof.config=com-adminserver-cycle-agent-pof-config.xml -Dtangosol.coherence.override=/opt/Environments/cycle-coherence-config.xml
Client
- Ensure that the JAVA_HOME environmental variable is set to a valid JDK 1.8.x installation. Alternatively, you can modify the startup scripts to use a specific JVM.
- Extract the Cycle.client archive file into the desired location on your file system. The following directories are included:
- bin – Contains the executables for the Cycle Client to run.
- conf – Contains the configuration files for the Cycle Client.
- lib – Contains the Java libraries required for the Cycle Client.
- Open aspectj-1.8.10.jar with an unzipping software and retrieve aspectjrt.jar and aspectjweaver.jar from the lib folder and copy into the lib directory.
- In the lib folder mentioned above, you will need to add a coherence 12.2.1.2 jar, which can be downloaded from the below url: http://www.oracle.com/technetwork/middleware/coherence/downloads/index.html
- For this, you will have to log on to oracle website and download the coherence 12.2.1.2 jar version and place it in the lib folder.
- Modify the necessary configuration files as outlined in the configuration section. In most cases, the following files will need to be configured:
- Cycle.properties – Refer to the Client Cycle.properties section above for the properties related to the Cycle Client.
- cycle-coherence-config.xml – This file controls the coherence cluster. Do not alter this file unless you have an in-depth understanding of coherence. The information in this file is based on how the installation was performed. The well-known-address is how you specify what machines are allowed to join the Cycle cluster. You will receive an error if you try to access a machine which is not in the cluster.
- cycle-coherence-cache-config.xml – This is a default file that defines how coherence caches are configured in terms of best practices.
- If you are using a database other than Oracle, the correct database drivers must be copied to the lib directory, as outlined in the data source section of this document.