Enabling SSIS in Visual Studio 2022

If you're using Visual Studio 2022, you will need to install the SQL Server Integration Services Projects extension to use SSIS.

1. Navigate to Extensions > Manage Extensions.
2. In the Manage Extensions window's search box, search for "SQL Server Integration Services Projects 2022" and select the extension in the list.
3. Click Download.
4. Close Visual Studio and run the downloaded Microsoft.DataTools.IntegrationServices.exe installer. Proceed through the installer with default settings.
5. Open Visual Studio. There should now be an "Integration Services Project" project template available.

Adding the JD Edwards Connection Manager

Create a new connection manager as follows:

1. Create a Visual Studio project with the "Integration Services Project" template.
2. In the project, right-click within the Connection Managers window and select New Connection from the menu.
3. In the Description column, select CData JD Edwards Connection Manager and click Add...
4. Configure the component as described in the next section.

Alternatively, if you have an existing project and CData JD Edwards Source or CData JD Edwards Destination:

1. Right-click your CData JD Edwards source or destination component in your data flow
2. Select Edit... to open an editor window.
3. Click the New... button next to the Connection manager: dropdown selector to create a connection manager.
4. Configure the component as described in the next section.

Connecting to JD Edwards

The component connects to JD Edwards through your JD Edwards Application Interface Services (AIS) Server.

Set the following connection properties to connect:

• URL: The base HTTPS URL of your AIS Server. For example: https://jde-ais.example.com:8300
• User: Your JD Edwards username.
• Password: Your JD Edwards password.
• Environment (optional): The JD Edwards environment to use (for example, PD920 for production or DV920 for development). The environment determines which database and configuration settings the provider uses during the session. If not specified, the AIS Server's default environment is used.
• Role (optional): The JD Edwards role for the session. Roles in JD Edwards determine the permissions and data access for the session. If not specified, the AIS Server's default role is used.
• DeviceName (optional): An identifier for the connecting device or application, used for auditing and logging on the AIS Server. If not specified, the IP address of the device the component is running on is used as the identifier.
• Jasserver (optional): The specific JAS (Java Application Server) instance to route requests through. This connection property is useful for associating requests with a particular node in a clustered environment. If not specified, the component uses the default HTML Server configured for the AIS Server.

To control what exact JD Edwards data is exposed, set these properties:

• DataModel: A module (or a comma-separated list of modules) whose system codes you want to expose as schemas in the component. Supported values include All, FinancialManagement, HumanCapitalManagement, Logistics, Manufacturing, OrderManagement, RealEstateManagement, and others. Defaults to FinancialManagement.
• SystemCodes: A comma-separated list of additional JD Edwards system codes to expose as schemas alongside those of the selected DataModel(s). For example, SystemCodes=42,43.

Token Caching

The component uses your credentials to obtain a session token, which is necessary to request your JD Edwards data from the API, from the AIS Server and caches it for subsequent requests.

On the first connection, the component sends your credentials to the AIS Server to obtain a session token. You can use the CredentialsLocation property to change the token storage location.

When the session token approaches expiry — after approximately 90% of the AIS Server's configured session timeout — the component automatically requests a new token using the stored credentials.