Connection properties for the external service wizard, WebSphere Adapter for JD Edwards EnterpriseOne

IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JD Edwards EnterpriseOne > Reference > Outbound configuration properties
Setting connection properties for the external service wizard

External service discovery connection properties establish a connection between the external service wizard of IBM Integration Designer, a tool used to create business objects, and the JD Edwards EnterpriseOne server. The properties you configure in the external service wizard specify such things as connection configuration, bidi properties, and logging and tracing options.

Once a connection between the external service wizard and the JD Edwards EnterpriseOne server is established, the external service wizard is able to access the metadata it needs from the JD Edwards EnterpriseOne server to create business objects.
Some of the properties that you set in the external service wizard are used as the initial value for the resource adapter and managed connection factory properties that you can specify at a later time in the wizard.
The external service connection properties and their purposes are described in the following table. A complete description of each property is provided in the sections that follow the table. For information on how to read the property detail tables in the sections that follow, see Guide to information about properties.
If you set any of these connection properties using bidirectional script, you must set values that identify the format of the bidirectional script entered for that property.

External service connection properties for Adapter for JD Edwards EnterpriseOne
Property name Description
Environment Specifies the JD Edwards EnterpriseOne environment name
Log file output location Specifies the location of the log file for external service
Logging level Specifies the type error for which logging will occur during external service
Password Password of the adapter user account on the JD Edwards EnterpriseOne environment
Role Name of the role that is associated with the user name used to access the JD Edwards EnterpriseOne environment.
User name Name of the adapter user account on the JD Edwards EnterpriseOne environment

Environment

This property specifies the JD Edwards EnterpriseOne environment name.

Environment details
Required Yes
Default No default value
Property type String
Usage A JD Edwards EnterpriseOne environment is a user-defined pointer that indicates the location of data and objects on a JD Edwards EnterpriseOne server. Users can be authorized to use multiple JD Edwards EnterpriseOne environments on a single JD Edwards EnterpriseOne server.
Globalized Yes
Bidi supported Yes

Log file output location

This property specifies the location of the log file for external service.

Log file output location details
Required Yes
Default The .metadata directory of the workspace
Property type String
Usage Use this directory to hold the log file that will list the errors that occur during the discovery process. The type of discovery errors for which logging occurs is controlled by the Logging level property.
Example C:\IBM\wid6.1.0\workspace\.metadata\JDEMetadataDiscovery.log
Globalized Yes
Bidi supported No

Logging level

This property specifies the type error for which logging will occur during external service.

Logging level details
Required No
Possible values
ALL
OFF
FINE
FINER
FINEST
CONFIG
INFO
SEVERE
WARNING
Default SEVERE
Property type String
Usage Use this property to tailor tracing capabilities. By specifying an error type, you are indicating that trace operations will occur only for errors of the type specified.
Example
Accepting the default value of SEVERE will provide trace information on errors that fall into the SEVERE category. Severe errors mean that an operation cannot continue, though the adapter can still function. Severe errors also include error conditions that indicate an impending fatal error, that is, reporting on situations that strongly suggest that resources are on the verge of being depleted.
Other error descriptions are as follows:

Fatal – Adapter cannot continue. Adapter cannot function
Warning – Potential error or impending error. This also includes conditions that indicate a progressive failure, for example, the potential leaking of resources.
Audit – Significant event affecting adapter state or resources
Info – General information outlining overall operation progress
Config – Configuration change or status
Detail – General information detailing operation progress

Globalized Yes
Bidi supported No

Password

This property specifies the password of the adapter user account on the JD Edwards EnterpriseOne environment.

Password details
Required Yes
Default No default value
Property type String
Usage Passwords are created and named by the JD Edwards EnterpriseOne administrator. There are no restrictions on the type of characters used, the number of characters used, or the case of the characters used in passwords.
Globalized No
Bidi supported Yes

Role

This property specifies the name of the role that is associated with the user name used to access the JD Edwards EnterpriseOne environment.

Role details
Required Yes
Default No default value
Property type String
Usage Roles define what authority users have. Users can have multiple roles. A user's access to applications, forms, table columns, data sources, and so on, is based on one or more roles to which the user is assigned. Roles are created and named by the JD Edwards EnterpriseOne administrator.
Examples

System administrator
Human resources
Accounting

Globalized No
Bidi supported Yes

User name

This property specifies the name of the adapter user account on the JD Edwards EnterpriseOne environment.

User name details
Required Yes
Default No default value
Property type String
Usage User names are created by the JD Edwards EnterpriseOne administrator. There are no restrictions on the type of characters used, the number of characters used, or the case of the characters used in user names.
Globalized Yes
Bidi supported Yes

Outbound configuration properties

Related reference:

Guide to information about properties
Resource adapter properties
Managed connection factory properties
Interaction specification properties

Property name	Description
Environment	Specifies the JD Edwards EnterpriseOne environment name
Log file output location	Specifies the location of the log file for external service
Logging level	Specifies the type error for which logging will occur during external service
Password	Password of the adapter user account on the JD Edwards EnterpriseOne environment
Role	Name of the role that is associated with the user name used to access the JD Edwards EnterpriseOne environment.
User name	Name of the adapter user account on the JD Edwards EnterpriseOne environment

Required	Yes
Default	No default value
Property type	String
Usage	A JD Edwards EnterpriseOne environment is a user-defined pointer that indicates the location of data and objects on a JD Edwards EnterpriseOne server. Users can be authorized to use multiple JD Edwards EnterpriseOne environments on a single JD Edwards EnterpriseOne server.
Globalized	Yes
Bidi supported	Yes

Required	Yes
Default	The .metadata directory of the workspace
Property type	String
Usage	Use this directory to hold the log file that will list the errors that occur during the discovery process. The type of discovery errors for which logging occurs is controlled by the Logging level property.
Example	C:\IBM\wid6.1.0\workspace\.metadata\JDEMetadataDiscovery.log
Globalized	Yes
Bidi supported	No

Required	No
Possible values	ALL OFF FINE FINER FINEST CONFIG INFO SEVERE WARNING
Default	SEVERE
Property type	String
Usage	Use this property to tailor tracing capabilities. By specifying an error type, you are indicating that trace operations will occur only for errors of the type specified.
Example	Accepting the default value of SEVERE will provide trace information on errors that fall into the SEVERE category. Severe errors mean that an operation cannot continue, though the adapter can still function. Severe errors also include error conditions that indicate an impending fatal error, that is, reporting on situations that strongly suggest that resources are on the verge of being depleted. Other error descriptions are as follows: Fatal – Adapter cannot continue. Adapter cannot function Warning – Potential error or impending error. This also includes conditions that indicate a progressive failure, for example, the potential leaking of resources. Audit – Significant event affecting adapter state or resources Info – General information outlining overall operation progress Config – Configuration change or status Detail – General information detailing operation progress
Globalized	Yes
Bidi supported	No