← Prepare Oracle Application InstanceIntercepting Oracle Applications Jobs →

Connecting to Oracle Applications Instances

To schedule workload in an Oracle Applications instance, you must first set up a connection between Redwood Server and the Oracle Applications instance.

  • A JDBC credential for the Oracle database
  • Database object that uses the credential and points to the Oracle database
  • Oracle Applications object that references the database object
    • Process server and queue are created automatically.

Credentials

The username and password is stored in a credential. Redwood Server retrieves the username and password by using the JDBC credential which has an Endpoint matching the value of the Database object and has default set as the Virtual Username.

Connection String

The connect string must be an Oracle JDBC compliant connect string as follows:

JDBC:oracle:thin:@<host>:<port>:<sid>
or
JDBC:oracle:thin:@//<host>:<port>/<service>
  • <host> - the hostname of the Oracle Applications database host
  • <port> - the port the Oracle database is listening on
  • <sid> - the SID of the Oracle database
  • <service> - the name of the service of the Oracle database

Example

JDBC:oracle:thin:@/oraapps.example.com:1521/orcl
note

Oracle recommends connecting using the service over the sid, as connecting via sid will be deprecated.

Prerequisites

  • Oracle Applications 11.5 or higher
    • Oracle database 8.1.7.4 or higher, an Oracle 8 database requires the 10.2.0.4 Oracle database client (JDBC)
  • on-site-related topic To connect to instances of Oracle Applications, you need a free slot in the ProcessServerService.OraApps.limit license key

Procedure

Create an Oracle Applications System Object

  1. Navigate to "Security > Credentials".
  2. Choose New Credential from the context-menu.
  3. Select the JDBC protocol, fill the username and password, as Endpoint it is recommended to choose the database name.
  4. Navigate to Environment > Databases.
  5. Choose New Database from the context-menu.
  6. Fill in the fields Name (referred to as <ora_name>) and JDBC Connect String.
  7. Select the credential for the database connection.
  8. Choose Save & Close.
  9. Navigate to "Environment > Oracle Applications".
  10. Choose New Oracle Applications System from the context-menu.
  11. Select the Database object you just created and set the Default Time Zone.
  12. Choose how you wish to retrieve output files.
  13. The HTTP(S) method is recommended as needs to configuration.
  14. If you would like to use a platform agent, you will have to install one on the EBS server.
  15. cloud-related topic If you registered the platform agent with the central Redwood Server, select a process server as Spool Host; note that output files will be stored on the central Redwood Server.
  16. Choose Save & Close.
  17. Navigate to "Environment > Process Servers".
  18. If you did register the platform agent with the central Redwood Server:
  19. Choose Start from the context-menu of the process servers named <ora_name>_ProcessServer.
  20. If you did not register the platform agent with the central Redwood Server:
  21. Choose Edit from the context-menu of the process servers named <ora_name>_ProcessServer.
  22. On the Process Server tab, ensure the PlatformAgentService is present and all native interpreters that the platform has are selected.
  23. On the Parameters tab, Fill the RemoteHostName, RemotePort (optional, default 1555), and SharedSecret (optional if the platform agent has none) parameters;.
  24. Choose Save & Close.

Start the process server

  1. Navigate to "Environment > Process Servers".
  2. Choose Start from the context-menu of the process server _<ora_name>ProcessServer.
  3. Refresh the window until the process server is starting, if after two minutes the process server has not started, inspect the Operator Messages Monitor.

Submit a test job

  1. Navigate to "Definitions > Processes" and choose Submit from the context-menu of System_OraApps_ConcurrentProgramImport.
  2. Select the newly created Oracle Applications system, select an Application short name and Concurrent Program name; note that the values are retrieved from the remote Oracle Applications system.
  3. Choose the _<ora_name>Queue queue served by the Oracle Applications process server and monitor the process until it reaches the status Completed, if the process reaches status Error, check "Monitoring > Operator Messages".

Install a Platform Agent on the Oracle Applications Server (Optional)

  1. Download the appropriate installer for your platform from "Configuration > Software".
  2. Navigate to "Environment > Process Servers".
  3. Choose New Process server from the context-menu, fill the Port field, select the appropriate platform; choose Next.
  4. Fill a name into the Name field, select or create a partition for the process server, and select the OS Family; choose Next.
  5. Select a Native installer, choose Next.
  6. Transfer the platform agent binary to the Oracle Applications Application server and run it with administrative privileges.
  7. If you register the agent with the central Redwood Server, you specify the name of the process server in the Spool Host field of the Oracle Applications object (see Create an Oracle Applications System Object section below).
  8. If you choose not to register the platform agent with the central Redwood Server, you add RemoteHostName, RemotePort, and SharedSecret to the process server created by the Oracle Applications object. (see Create an Oracle Applications System Object section below).
note

You can use the default settings, on UNIX, you should ensure the user the jobs run under is a valid user. See the Creating Platform Process Servers topic for more information on installing platform agents.

See Also

← Prepare Oracle Application InstanceIntercepting Oracle Applications Jobs →