Enterprise Resource Planning (ERP) Connection Profiles

The following topics describe the connection profile parameters for enterprise resource planning (ERP) platforms and services:

Oracle E-Business Suite Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a centralized connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for Oracle E-Business Suite.

Oracle Connection Details Parameters

The following table describes the Oracle Connection Detail parameters that enable you to create an OEBS connection profile.

Parameter

Description

Service Name

(Mandatory) Defines the Oracle client connection identifier registered in the tnsnames.ora file.

For more information, contact your Oracle Database Administrator.

User Name

Defines the username for the Oracle E-Business Suite (OEBS) server.

Password

Defines the password for the OEBS server.

Language

Determines whether to use the default Oracle client language or a different language.

Character Set

Enables you to set National Language Support (NLS) characters.

Default Job Options Parameters

The following table describes the Default Job Options parameters that enable you to create an OEBS connection profile.

Parameter

Description

Append request log to job output

Determines whether to copy the OEBS request log to the job outputClosed A tab in the job properties pane of the Monitoring domain where the job output appears that indicates whether a job ended OK, and is used, for example, with jobs that check file location..

Append request output to job output

Determines whether to copy the OEBS request output to the job output.

Allow job to complete even if a warning occurs

Determines whether to allow the OEBS job to complete even if a warning appears.

Monitor all child requests (Wait Child)

Determines whether to track OEBS child jobs.

Job completion depends on a child request status

Determines whether to set the OEBS job ending status according to the lowest completion status of all the child requests.

PeopleSoft Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a centralized connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for PeopleSoft.

The following table describes the connection detail parameters to add a connection profile.

Parameter

Description

PeopleTools Version

Defines the PeopleTools version, as follows:

<Major_Version.Minor_Version>

  • 8.48

  • 8.52

The PeopleSoft administrator must provide the exact version.

User Name

Defines a valid PeopleSoft user, as defined on PSOPRDEFN, which has the roles to submit and execute processes.

User Password

Defines the password for the PeopleSoft server.

Domain Password

(PeopleTools 8.51 or higher) Defines the PeopleSoft domain password.

Application Server Name

Defines the PeopleSoft application server name.

Jolt Port

Defines the PeopleSoft application server Jolt listener port number.

SAP Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a centralized connection profile, see Creating a Centralized Connection Profile.

Control-M for SAP can connect with an SAP system after a connection profile is created.

For more information about this plug-in, see Control-M for SAP.

The following table describes the SAP connection profile parameters:

Parameter

Logon Type

Description

General

 

Click to open the General parameters.

Connection Profile Name

 

Defines the connection profile for the job.

Rules:

  • Characters: 1−30

  • Case Sensitive: Yes

  • Invalid Characters: Spaces

Description

 

Defines a free-text description of the connection profile.

Logon Type

 

Determines one of the following types of logons:

  • Specific Application Server

  • Group

Application Server Host Name

Specific Application Server

 

Defines the host name of the host running the SAP application server.

System Number

Specific Application Server

Determines a two-digit number of the SAP instance.

Rule: 2 characters

System ID

Group

Defines the the SAP System ID.

Rule: 3 alphanumeric characters

Message Server Host Name

Group

Defines the host name of the SAP system message server.

Group

Group

Defines the SAP login group name.

The Group name is defined in the SAP SMLG transaction.

Connection Details

  • Specific Application Server

  • Group

Click to open the Connection Details parameters.

SAP Client

  • Specific Application Server

  • Group

Determines the number of the SAP client.

Rule: 3 characters

Login Username

  • Specific Application Server

  • Group

Defines the SAP login username.

For details about required authorizations, see Control-M for SAP Post-installation.

Rules: 1–127 characters

Login Password

  • Specific Application Server

  • Group

Defines the password for the SAP login user.

Language

  • Specific Application Server

  • Group

Determines the SAP language.

Default: English

SAP Application Version

  • Specific Application Server

  • Group

Determines one of the following SAP application versions:

  • R/3

  • BW 2.<X>

  • BW 3.<X> or higher

Default: R/3

XBP Version

  • Specific Application Server

  • Group

Determines one of the following SAP XBP interface versions that is installed on the SAP server:

  • XBP 1.0

  • XBP 2.0

  • XBP 3.0

Default: XBP 3.0

SAProuter String

  • Specific Application Server

  • Group

(Optional) Defines the proxy in a network connection between SAP systems and external networks.

Secured Network Communication

  • Specific Application Server

  • Group

Click to open the Secured Network Communication parameters.

SNC Partner Name

  • Specific Application Server

  • Group

Defines the SNC (Secured Network Communication) name of the application server.

p:CN=LE1, OU=BPM, O=BMC, C=US

SNC Lib

  • Specific Application Server

  • Group

Defines the SAP crypto lib pathname.

/home1/agsapfp/SNC/libsapcrypto.sl

Quality of Protection

  • Specific Application Server

  • Group

Determines the quality of the secured network protection.

Valid Values: 1, 2, 3, 8, and 9.

Default: 8

SNC My Mame

  • Specific Application Server

  • Group

Defines the SNC name of the user sending the RFC.

Default: The name provided by the security product for the user who is logged on.

Advanced Options

  • Specific Application Server

  • Group

Click to open the Advanced Options parameters.

Specify the Maximum Time To Wait for an SAP Response

  • Specific Application Server

  • Group

Determines the number of seconds the program waits for an RFC request to be handled by the SAP system before returning a timeout error.

Default: 180

Use SAP Plug-in Function Modules

  • Specific Application Server

  • Group

Determines whether the extended functionality of Control-M for SAP is used.

This is a Solution Manager Connection Profile

  • Specific Application Server

  • Group

Determines whether the specified connection profile is a solution manager connection profile.

If this not selected, enter the solution manager connection profile in the next parameter, below.

Define the Required Solution Manager Connection Profile

  • Specific Application Server

  • Group

Defines the required solution manager connection profile.

SAP BTP Scheduler Connection Profile Parameters

Before you can define a job, you must create a connection profile in the Configuration domain. A connection profile contains authorization credentials—such as the username, password, and other plug-in-specific parameters—and enables you to connect to the application server with only the connection profile name. To create a connection profile, see Creating a Centralized Connection Profile.

For more information about this plug-in, see Control-M for SAP BTP Scheduler.

The following table describes the connection detail attributes to add a connection profile.

Attribute

Description

Client ID

Defines the unique identifier of the SAP client.

To obtain the Client ID in SAP, see KA000438774.

Client Secret

Defines the password associated with the SAP client.

To obtain the Client Password in SAP, see KA000438774.

Use External Vault

Determines whether to retrieve secret parameter values from an external vault, as described in CyberArk Secret Parameters in Connection Profiles.Determines whether to retrieve secret parameter values from an external vault as described in CyberArk Secret Parameters or HashiCorp Secret Parameters.

SAP Authentication URL

Defines the SAP authentication endpoint, in the following format:

https://<Domain Name>.authentication.<Region>.hana.ondemand.com/oauth/token

where:

  • Domain Name: The SAP Identity Authentication Service (IAS) tenant subdomain, such as mycompany.

  • Region: The SAP BTP region code where the tenant is hosted, such as eu10 and us10.

To obtain the Domain Name and Region in SAP, see KA000438774.

Trigger URL

Defines the URL to communicate with the SAP Job Scheduler in the following format:

https://jobscheduler-rest.cfapps.<Region>.hana.ondemand.com

where the Region parameter is the SAP BTP region code where the tenant is hosted, such as eu10 and us10.

HTTP Codes

Defines the HTTP codes that trigger a rerun of a job step if detected in the response.

Multiple HTTP codes must be separated with a space.

You cannot rerun a step with HTTP codes when you perform manual execution, such as rerun from point of failure.

Default: 503

Attempt Reruns

Determines the number of attempts to rerun a job step.

Default: 3

Rerun Interval

Determines the number of seconds to wait before Control-M reruns the job step.

Default: 10

Connection Timeout

Determines the number of seconds to wait after Control-M initiates a connection request before a timeout occurs.

Default: 60