JDEdwards Connection policy (JDEdwardsConnection)

Use a JDEdwards Connection policy to control, at run time, connections to JDEdwards applications.

You use JDEdwardsInput and JDEdwardsRequest nodes to accept input from, and send requests to, JDEdwards applications. JDEdwards nodes can get connection details from either the adapter component or a policy. By using a policy, you can change the connection details for an adapter at run time without the need to redeploy the adapter.

To enable connection details for the JDEdwardsInput or JDEdwardsRequest node to be retrieved from a policy, you must deploy a policy with the same name as the JDEwardsAdapter, of type JDEdwardsConnection, in the default policy project for the integration server. This policy must be deployed before the message flow containing the JDEdwards node is started. For example, if a JDEdwardsInput node is configured to use the adapter file JDEdwardsCustomerInbound.inadapter, ensure that the name of your JDEdwardsConnection policy is JDEdwardsCustomerInbound. When the JDEdwards node starts, it uses connection details in the policy to connect to JDEdwards.

If you redeploy a JDEdwards Connection policy, all message flows that are using the policy will be stopped and restarted.

The properties of this policy are described in the following table:

Table 1. Properties of the JDEdwards Connection policy
Property	Property name in .policyxml file	Description of properties
Assured once-only delivery	assuredOnceDelivery	Specifies whether to provide assured once-only delivery for inbound events. This property applies only to .inadapter files. The default value is an empty string, which indicates that behavior is controlled by the .inadapter file.
Environment	environment	The JD Edwards EnterpriseOne environment to which to connect. 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.
Role	role	The role that is applicable to the JD Edwards connection. 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.