Integrate Cloud Inventory® Platform with JD Edwards EnterpriseOne 64-bit

About integrating Cloud Inventory® Platform with JD Edwards EnterpriseOne 64-bit

Note:

This process assumes the user has a comprehensive familiarity with Oracle and database troubleshooting.

JDE EnterpriseOne Configurable Network Computing (CNC) concepts
JDE EnterpriseOne Applications Interface Services (AIS) server
JDE EnterpriseOne User security
Cloud Inventory® Platform

With the release of their JDE EnterpriseOne 9.2 Update 5 (UN5) and above, and running JDE Tools 9.2.4.x and above, JD Edwards now strongly recommends customers convert from using XML Interop to AIS Interop (REST API) processing. The Cloud Inventory® Platform supports integration with the JD Edwards EnterpriseOne ERP system using AIS Interop. The latest release of Cloud Inventory® Platform supports integration with EnterpriseOne using both XML and REST methods.

Note:XML interop only works with 32-bit versions of JDE EnterpriseOne. Further differences with theses integration methods and their configuration in the platform are outlined below. Refer to the Connector Settings for the shared setup aspects that have not changed.

64-bit Connector Settings

To account for the storage of function registration metadata in the JDE system database and JDE's strong recommendations to use AIS (web service) Interop for integration within the latest EnterpriseOne Tools releases, new REST API based functionality was added within the Cloud Inventory® EnterpriseOne Connector, which uses an AIS Server(REST API) connection for function registrations and function call processing. To activate this functionality, your JDE system must have Tools 9.2.4.3 or higher applied. It must also have an AIS server configured for the JDE environments path you are connecting to. Using this functionality requires you to be running the appropriate version of the platform and to reconfigure your connector settings.

Note:Comparing XML and AIS Interop methods, only the interop method has changed, not the functionality within the interface functions themselves.

Enable AIS Interop

Before reconfiguring the EnterpriseOne Connector, update the user permissions for the user defined in the User ID field in the EnterpriseOne connector configuration screen. For this integration to work the user must be granted the ability to submit and run APIs via the AIS server. The AIS Server Security Settings also need to have the "Allow Basic Authentication Login" checkbox selected.

To enable AIS Interop within the connector, do the following:

In JDE Work With User/Role Security, select Form > Set Up Security > Data Browser.

Example
Add the User with Allowed access to launch Data Browser and Search/Select Tables or Business View queries. This should be added for the JDE User that is being used in the Platform EnterpriseOne Connector.

Example
In JDE Work With User/Role Security, select Form > User Defined Object > View.

Example
In the toolbar, select the + to Add User Defined Object View Security.

Example
Add Security for JDE User in question as shown in the example below. This should be added for the JDE User that is being used in the Platform EnterpriseOne Connector.

Example
From the JDE EnterpriseOne Server Manager, select your EnterpriseOne Application Interface Services instance (AIS Server). In the Configuration selections, select "Security Information". In the "Application Interface Services Security Settings" section, confirm that the allow login checkboxes are selected.

Example
To ensure that the Platform EnterpriseOne Connector can use Basic Authentication on the backend:
1. Take a backup of the config.xml file found in the 'WebLogic_home\user_projects\domains\AISDomainLocation\config' directory.
2. Add an '<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>" entry to the config.xml just before the closing </security-configuration> tag of the Weblogic Server domain:
  Step Information
  
  <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
3. Restart the AIS server.

For more information regarding the setup/configuration of the JDE EnterpriseOne AIS Server, please refer to Oracle's Application Interface Services Server Reference Guide.

Once the user is configured in JDE you can set up the connector.

Enable the JDE Connector in Cloud Inventory®

The AIS (Application Interface Services) server enables communication between Cloud Inventory® and JD Edwards EnterpriseOne.

From the Cloud Inventory® menu, open Platform > Admin > Configuration > Connector Settings > EnterpriseOne XML Connector. At the bottom of the list of settings, we have added additional configuration options for REST API:

Enable for function registration
Enable for function calls
Host name/address
Host port Use SSL

Migrate Existing Registered Functions

In the past it was required that you point to a shared file location on the deployment server where the objects would be located after completing a build of the objects. Oracle no longer requires that these header and source files be deployed to the deployment server for any reason. The new method to register functions uses the AIS server to execute a web service call that can retrieve details about the objects directly from the EnterpriseOne database.

When using the AIS Interop connector functionality for the first time, previously registered Functions require a one-time migration process to add Control ID information required by the REST API call. To perform this migration:

Open Platform > Develop > Connectors > EnterpriseOne XML Connector.
Select Migrate to 64-bit Compatible. This may take a few moments to finish.

Once the process is finished, a summary will display the number of:

Migrated files
Up-to-date files
A list of functions that failed to migrate

If any functions failed to migrate, re-register them individually.

Note:Do not delete functions prior to reregistering. Reregistering will simply overwrite the existing function so as to not affect any apps that use it.

Applying ASUs for JD Edwards EnterpriseOne Interface code

Cloud Inventory® ASUs can contain 32-bit objects, 64-bit objects, or both. Going forward, the goal is that only 64-bit objects will be used and provided. According to discussions, JD Edwards plans for upgrades to require a 64-bit only EnterpriseOne environment. For this reason, it is both best practice and highly recommended that our clients migrate their JDE EnterpriseOne 9.2 systems to 64-bit only starting in Apps Update 6 (UN6). Moving forward, JDE and Cloud Inventory® both recommend keeping your EnterpriseOne 9.2 environment apps and tools release on the same level starting in Release 22 (UN6 & Tools 9.2.6.x).

Note:For EnterpriseOne 9.2 Apps Update 5 (UN5), the baseline ASUs provided for Cloud Inventory® interface objects will be 32-bit only or 64-bit only.

For EnterpriseOne 9.2 Apps Update 6 (UN6) and beyond, the baseline ASUs provided for Cloud Inventory® interface objects will be 64-bit only.

With EnterpriseOne configurations using Dual foundation (32-bit and 64-bit), separate ASUs will need to be applied for 32-bit baseline and 64-bit baseline. Some post-baseline bug fixes will require paper fixes to be manually applied and promoted.

There was a problem loading this topic

Mobile Enterprise Platform