JAMS natively supports automation using many leading business applications, including the Oracle E-Business Suite. Integrations (add-ons) for this and other preferred applications are selected during the JAMS installation process. Once the Oracle E-Business Suite integration is enabled, users can create, manage, deploy and monitor every kind of Oracle EBS batch process job, regardless of where it resides.
To work with Oracle EBS in JAMS, users must install the Oracle E-Business Suite Add-on on the JAMS Scheduler Server and deploy an Agent to the Oracle Server. For more information on deploying Agents, see Agent D and Agent X sections.
![]() |
NOTE: Un Checking components in the Feature Selection step will uninstall those components. |
The Oracle EBS Connection String allows users to connect to Oracle from within JAMS. This connection string must be properly configured to run Oracle Jobs in JAMS. The Oracle EBS connection should be configured on each Oracle EBS Execution Method in JAMS.
Users may override the connection string configured on an Execution Method by configuring a Connection String Parameter at the Folder level or Job level.
![]() |
NOTE: If the User on an Oracle EBS Job has OS Authentication permissions to Oracle, then JAMS will pass the credentials from the User into the defined connection string during execution, and an Oracle user is not needed in the Job's source. If the User on the Job does not have OS Authentication, an Oracle user must be defined in the dropdown list that has permissions to the oracle Database. |
User Id = {0}; Password = {1}; Data Source = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = Orchid64)(PORT = 1521))(CONNECT_DATA = (SERVICE_NAME = MVP)));
A Connection String should ONLY be defined at the Folder level if users wish to override the Execution Method level Connection Strings. Note that the Folder level Connection String will apply to all Oracle EBS Jobs within that folder.
User Id = {0}; Password = {1}; Data Source = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = Orchid64)(PORT = 1521))(CONNECT_DATA = (SERVICE_NAME = MVP)));
A Connection String Parameter should ONLY be defined at the Job level if users wish to override Execution Method or Folder level Connection Strings.
User Id = {0}; Password = {1}; Data Source = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = Orchid64)(PORT = 1521))(CONNECT_DATA = (SERVICE_NAME = MVP)));
JAMS offers OracleEBSConcurrent, OracleEBSJobSsh, and OracleEBSRequestSet Execution Methods to run Oracle EBS Jobs.
The OracleEBSConcurrent Execution Method gives users a series of automatically populated drop-down fields to run Concurrent Jobs, including the ability to view and set each parameter on the Concurrent Job from within JAMS.
The OracleEBSJobSsh Execution Method gives users a fill in the blank style form to run Concurrent Jobs from within JAMS. The advantage of the fill in the blank form over the OracleEBSConcurrent Execution Method is that field values in the Job Source may be defined as JAMS Parameters. By using Parameters in the Job Source, users can create a self-service Oracle Job from within JAMS.
The OracleEBSRequestSet Execution Method gives users a series of automatically populated drop-down fields to run Request Sets, including the ability to see each Concurrent Job (and modify the Concurrent Job's Parameters) within the Request Set.
OracleEBSJobSsh Jobs in JAMS provide a fill-in-the-blank style form for users to configure their Concurrent Oracle Jobs in JAMS. The benefit of the fill-in-the-blank form over the automatically populated drop-down list of the OracleEBSConcurrent Execution Method is the parametrization of field values. By using Parameters in the Job Source, users can create a self-service Oracle Job from within JAMS.
JAMS | Oracle |
---|---|
Job Name | Program Shortname |
Application Short Name | Program Application Shortname |
Responsibility Short name | Responsibility App Shortname |
Responsibility Name | Responsibility Name |
Username | Username |
Parameters | Parameters |