Configuring GOP

This chapter covers the following topics:

Configuring the GOP Web Service Data Source

The GOP web service is deployed in the web logic server (WLS) which is part of AIA Fusion Middleware (FMW).

The WLS should have a valid data source named ApplicationDB. The data source's Java Sourcing and Directory Interface (JNDI) name should be JDBC/ApplicationDBDS and it should have valid database connection details.

To verify that a valid data source exists

  1. In the WLS Administration Console, navigate to Services, Data Sources, ApplicationDB.

  2. Click the Configuration tab.

  3. Click the Connection Pool tab.

  4. Click the Targets tab.

    This page allows you to view the servers or clusters on which the data source is deployed.

  5. Click the Monitoring tab.

  6. Click the Testing tab.

  7. Select a data source and click Test Data Source.

To create a new data source

If ApplicationDB does not exist in the web logic service, you must create a new data source.

  1. In the WLS Administration Console, navigate to Services, Data Sources.

  2. Click the New button and select Generic Data Source.

  3. In the Name field, enter ApplicationDB.

  4. In the JNDI Name field, enter jdbc/ApplicationDBDS.

  5. Click Next.

  6. Select an entry in the Database Driver drop-down list and click Next.

  7. Select the following options:

    • Supports Global Transactions

    • One-Phase Commit

  8. Click Next.

  9. Provide the database connection details and click Next.

  10. Verify the driver class name and other database parameters.

  11. Click Next.

  12. Select one or more targets on which to deploy the new JDBC data source.

  13. Click Finish.

Deploying the GOP Web Service

The GOP web service is deployed in the WLS, which is part of AIA Fusion Middleware (FMW).

To deploy the GOP web service

  1. Copy the msc_ws_atp_ws.ear file to a local directory in the host where WLS is running.

  2. In the WLS Administration Console, navigate to Deployments.

  3. Click Install.

  4. Click the 'upload your file(s)' link.

  5. Click Browse.

  6. Locate the msc_ws_atp_ws.ear file and click Next.

  7. Click Next.

  8. Leave the 'Install this deployment as an application' option checked, and click Next.

  9. Select one or more targets on which to deploy the application and click Next.

    Note: Targets for the data source and the deployed application should be the same.

  1. Select optional settings and click Next.

  2. Click Finish.

  3. Click Save.

Profile Values

After deploying the GOP web service, set the following profiles:

Profile Description
MSC: Memory build during deployment for GOP WS (MSC_GOP_WS_MEMORY_BUILD_DEPLOY) Indicates whether or not to load data at deployment time or not. Values are:
  • Yes – load

  • No – do not load


The recommended initial value is Yes.
MSC: Memory refresh mode for GOP WS (MSC_GOP_WS_MEMORY_REF_MODE) Indicates whether or not to perform a complete refresh or a net change when an element is not found in the value map. Values are:
  • Complete Refresh

  • Net Change Refresh


The recommended initial value is Complete Refresh. If system performance issues are encountered, set to Net Change Refresh.
MSC_ATP_DEBUG (MSC: ATP Debug Mode) Indicates whether not to log debug messages to a file. Values are:
  • Debug Only

  • Debug and Database Trace

  • Database Trace Only

  • None


The recommended initial value is Debug and Database Trace. If system performance issues are encountered, set to None.
MSC: Memory cleanup window (Days) for GOP WS (MSC_GOP_WS_CLEANUP_WINDOW) Indicates a number of days. Once this number of days is reached, elements which have not been accessed are removed. It should be a numeric value. This profile option is used for LRU approach.
The recommended initial value is 30.
MSC: Organization Translation WSDL URL (MSC_GOP_WS_ORG_TRANS_URL) Gives the WSDL URL for the Organization Translation Web service.
The format is as follows: http://{hostName}:{port}/ODIWebservice-ODIInvoke-context- root/MSC_E1APS_DVMDATAService?wsdl
This profile option is mandatory. There is no default value.

Setting Up GOP in EnterpriseOne

To set up GOP in EnterpriseOne

  1. In JDE E1, navigate to Fast Path P99410.

  2. On the EnterpriseOne System Control – Revisions page, turn the GOP system constants on by clicking the Yes option.

  3. Navigate to Fast Path P34A10.

  4. On the Integration Constants page, complete the following fields:

    • Inclusion Version

    • GOP Arrival or Ship Flag

  5. Navigate to Fast Path P95400.

  6. On the Update Web Service Soft Coding Record page, the Soft Coding Key field should be set to JC34A010.

  7. In the Soft Coding Value field, enter a URL to point to the GOP web service's end point, for example:

    <endpoint>http://sdc60027sems.us.oracle.com:7014/OrderPromising- OrderPromisingProject-context-root/OrderPromisingServicePort?WSDL</endpoint>

  8. Navigate to Fast Path P4210.

  9. On the Processing Options page, set up a version of GOP with Global Order Promising Mode by entering 2 in the following field:

    Order Promising Blank = No Order Promising 1 = Auto Promising Mode 2 = Global Order Promising Mode