CA ESP Workload Automation System Agent r6.1 - Oracle Application Server 10g Certification
Article ID: 55052
Updated On:
Products
Issue/Introduction
Contents
Installing & starting up the Oracle Application Server
How to Set Up Oracle for dSeries
CA dSeries Workload Automation (Server):
Version: 5.0.3.0
Build: 212
Installed Operating System: Windows 2003
CA ESP Workload Automation System Agent:
Version: 6.1
Build: 2005062411
Installed Operating System: Windows 2003
CA dSeries Workload Automation Desktop Client:
Version: 2.0.2.0
Build: 323
Installed Operating System: Windows XP
Oracle Application Server:
Version: 10g (10.1.3)
Installed Operating System: Windows 2003
Install the Agent with "J2EE Plug-in"
Note: For more information refer the " ESP_System_Agent_R6.1_Administrators_Guide_01.pdf " available with the Agent documentation.
Installing & starting up the Oracle Application Server
Oracle Application Server is a software program that deploys J2EE-based applications using Oracle Containers (OC4J). If required, you can download the OC4J file from the Oracle website.
Note: Refer the vendor's documentation for installing the application server.
Note: Refer the readme.txt to startup the "oc4j", after successful installation of the server.
Setting Up Oracle Application Server for dSeries
To set up Oracle Application Server for dSeries, do the following:
- Collect the Oracle and Client Jars
Note: The jars listed are based on Oracle Application Server 10g. Other versions of Oracle may contain different jar files. Collect all of the jar files for your particular version.
To configure the agent to access your Java applications deployed on your Oracle Application Server, you must collect the following jar files:- ejb.jar, javax77.jar, jms.jar, jta.jar located in the j2ee/home/lib directory
- oc4jclient.jar located in the j2ee/home directory
- client jars that contain the interfaces and stubs for the application Enterprise JavaBeans (EJBs) you intend to access via the agent Java applications
Contact the Java EE developer to locate the client jar for the Java applications you intend to use with the agent. - ejb.jar, javax77.jar, jms.jar, jta.jar located in the j2ee/home/lib directory
- Configure the Agent for Oracle
You must add the required Oracle jar files to your agent installation directory and configure the agent's classpath to specify the location of those files.
Note: The following instructions are based on Oracle Application Server 10g.
To configure the agent for Oracle- Create a subdirectory within your agent installation directory to store the Oracle jar files, for example, agentdir /jars/oc4j.
- Copy the Oracle jar files into the new subdirectory.
- Create a second subdirectory to store the client jar for the Java applications you intend to use, for example agentdir /jars/ext/stubs.
Note:
We recommend you create the subdirectory in the existing agentdir/jars/ext directory. - Copy the client jar into the new subdirectory.
- Stop the agent.
- Open the agentparm.txt file and configure the oscomponent.classpath parameter to specify the Oracle and client classpaths.
- For example, on UNIX, specify jars/oc4j/*.jar:jars/ext/stubs/*.jar.
- Save and close the agentparm.txt file.
- Start the agent.
The agent is configured for the Oracle Application Server. - Create a subdirectory within your agent installation directory to store the Oracle jar files, for example, agentdir /jars/oc4j.
- Test the Oracle Setup
After you have set up Oracle for the agent, you can use Desktop Client to create and run a test Application containing one of the following jobs:- Entity Bean or Session Bean
- JMS Publish or JMS Subscribe
To define these jobs, you require the following Oracle-specific information:
- Initial context factory
- Provider URL
- User and password (depending on the Oracle Application Server setup)
Note: For detailed instructions, see the Define perspective help in Desktop Client.
Use the application "default" that is deployed and readily available on the Oracle Application Server.
An EJB module "jmsrouter_ejb" will be available in the "default" application and the same would be used in our testing.
Create a JMS publish job using desktop client with the following information- Name - JMS_PUB
- Agent name - APPAGENT
- Initial context factory-com.evermind.server.rmi.RMIInitialContextFactory
- Provider URL- ormi://localhost/default
Note : Please replace "localhost" with the machine name where oc4j is installed. - Connection factory - jms/XAQueueConnectionFactory
- JNDI destination - jms/events
- Message class - String
- Destination type - QUEUE
- Message Parameters - My First message
- User - oc4jadmin
Upload the job and run it. The job should go to COMPLETED if success. Refer the Error Messages page for possible error messages.
Example: JMS Subscribe job to consume a message through an Oracle Application Server
Use the application "default" that is deployed and readily available on the Oracle Application Server.
An EJB module "jmsrouter_ejb" will be available in the "default" application and the same would be used in our testing.
We will try to retrieve the message published by the previous job here.Add a JMS subscribe job using desktop client with the following information on the previously created application
- Name - JMS_SUB
- Agent name - APPAGENT
- Initial context factory-com.evermind.server.rmi.RMIInitialContextFactory
- Provider URL- ormi://localhost/default
Note : Please replace "localhost" with the machine name where oc4j is installed. - Connection factory - jms/XAQueueConnectionFactory
- JNDI destination - jms/events
- Destination type - QUEUE
- User - oc4jadmin
Upload the job and run it. The message sent by the JMS_PUB should be received by the JMS_SUB ("My First message"). Refer the JOB details in the Monitor perspective.
Example: Invoke a Stateless Session Bean on an Oracle Application Server
Download an sample EJB JAR available at http://www.oracle.com/technology/sample_code/tech/java/oc4j/htdocs/oc4jsamplecode/oc4j-demo-ejb.html#StatelessSessionBean
to test the stateless session bean.
Deploy the same in the oracle application server and modify provide the application administration authorization for the same.
Add a EJB job using desktop client with the following information on the previously created application
- Name - EJB
- Agent name - APPAGENT
- Initial context factory-com.evermind.server.rmi.RMIInitialContextFactory
- Provider URL- ormi://localhost/employee
Note : Please replace "localhost" with the machine name where oc4j is installed. - Bean name - employee/EmployeeBean
- Method name - addEmployee
- User - oc4jadmin
- Method Parameters
Integer - 001
String - Emp1
Float - 100.25
Upload the job and run it. - Entity Bean or Session Bean
Possible error messages while running J2EE jobs:
- Specified domain/application in the "*Provider URL" unavailable:
Status("Lookup error: javax.naming.AuthenticationException: No such domain/application: ""defaul""; nested exception is: ..javax.naming.AuthenticationException: No such domain/application:""defaul""") - Specified Connection factory in the "*Connection factory" unavailable:
Status("jms/XAQueueConnectionFactory1 not found") - Specified JNDI destination in the "*JNDI destination" unavailable:
Status("jms/eventss not found") - Specified Destination type in the "*Destination type" is wrong:
Status("java.lang.ClassCastException") - Specified Initial Context Factory in the "*Initial Context Factory" is wrong:
Status("Cannot instantiate class: com.evermind.server.rmi.RMIInitialContextFactor") - Specified User ID in the job doesn't have access to the deployed event:
Status("Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is: ..javax.naming.AuthenticationException: Not authorized")
Environment
Component: SYSAGT
Feedback
