Redwood Documentation

Product Documentation

 

›Oracle Health Insurance

RunMyJobsERP Systems

Modules

  • ERP Modules

Oracle EBS

  • The Oracle Applications Connector
  • Prepare Oracle Application Instance
  • Connecting to Oracle Applications Instances
  • Intercepting Oracle Applications Jobs
  • Oracle Applications Job Interception Configuration
  • Technical Requirements and Sizing Recommendations
  • Using the Oracle Apps Definition Type
  • Importing Oracle Applications Concurrent Programs
  • Importing Oracle Applications Request Sets
  • Importing Oracle Applications Functions and Procedures
  • Calling Oracle Applications Functions and Procedures

Oracle Health Insurance

  • The Oracle Health Insurance Connector
  • Connecting to Oracle Health Insurance Instances
  • Importing Oracle Health Insurance Workload

PeopleSoft

  • The PeopleSoft Connector
  • Connecting to PeopleSoft Instances
  • Importing PeopleSoft Workload
  • Intercepting PeopleSoft Jobs
  • PeopleSoft Job Interception and Monitoring Configuration
  • Peoplesoft Plug-In
← The Oracle Health Insurance ConnectorImporting Oracle Health Insurance Workload →

Connecting to Oracle Health Insurance Instances

To schedule workload in an Oracle Health Insurance ( OHI ) instance, you must first set up a connection between Redwood Server and the OHI instance.

Connecting to an OHI instance requires:

  • An Oracle Health Insurance object that points to the underlying Oracle database
    • As soon as you create it, it will create a process server and queue

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 Health Insurance 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.

Credentials

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

Prerequisites

  • Scripts in OHI must have a 24/7 open batchframe
    • Existing script requests must be removed before using Redwood Server; if you leave them as is, they will not be monitored.
  • The following properties of imported OHI JobDefinitions must not be changed :
    • Name
    • Parameter (name/type/constraints)
    • Description
    • Authorizations and business rules in OHI are leading
  • on-site-related topic To connect to instances of Oracle Applications, you need a free slot in the ProcessServerService.OraApps.limit license key
  • on-site-related topic Connectivity from the central Redwood server to the Oracle database on its port
  • cloud-related topic Connectivity from the secure gateway to the Oracle database on its port

Procedure

Create an Oracle Health Insurance System Object

  1. Navigate to "Environment > Oracle Applications".
  2. Choose New Oracle Health Insurance System from the context-menu.
  3. Fill in the fields Name (referred to as <ora_name>), JDBC Connect String, and Default Time Zone.
  4. Choose Save & Close.
  5. Navigate to "Environment > Process Servers".
  6. Choose Save & Close.

Create the credential for Oracle Health Insurance

  1. Navigate to "Security > Credentials".
  2. Choose New Credential from the context-menu, select OHI as a protocol, fill the name of the OHI system object into the Endpoint property and default into the Virtual Username field. Fill the username and password into the respective fields.

Start the process server and submit a test job

  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.
  4. Navigate to "Definitions > Processes" and choose Submit from the context-menu of System_OraOHI_Import.
  5. Choose the _<ora_name>Queue queue served by the Oracle Health Insurance process server and monitor the job until it reaches the status Completed, if it reaches status Error, check "Monitoring > Operator Messages".
← The Oracle Health Insurance ConnectorImporting Oracle Health Insurance Workload →
  • Connection String
  • Credentials
  • Prerequisites
  • Procedure
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |