Redwood Documentation

Product Documentation

 

You are currently viewing the legacy RunMyJobs documentation site. This site will be taken down later this month.
All current and future RunMyJobs documentation, including versions 2023.3 and later, can be found here.
Please update your bookmarks. Use the version dropdown menu to select the documentation you need.

›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
← Connecting to Oracle Health Insurance InstancesThe PeopleSoft Connector →

Importing Oracle Health Insurance Workload

You import Oracle Health Insurance ( OHI ) scripts into Redwood Server using the System_OraOHI_Import process definition. For each imported script, Redwood Server creates a process definition that you can schedule like any other Redwood Server workload.

The import process definition imports all scripts that match the conditions in the prerequisites section below. You can specify the following properties of imported scripts:

  • Partition
  • Application

If you already have a process definition with the same name in the same partition, it will not be overwritten by default; to change this behavior, set the Overwrite Existing Process Definitions? to Yes.

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

Procedure

Importing OHI scripts

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of the System_OraOHI_Import process.
  3. Select the OHI system from which you wish to import scripts.
  4. On the Generation Settings tab, specify a partition and application; if you have modified scripts in OHI and wish to re-import, select Yes for the Overwrite Existing Process Definitions? parameter.
  5. Choose Next.
  6. On the Time and Dates page,leave the default value of Once and choose Next.
  7. The default queue of your OHI system is already selected, choose Submit.
← Connecting to Oracle Health Insurance InstancesThe PeopleSoft Connector →
  • 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 |