21 Configuring and Deploying Design to Release: Agile - JDE E1

This chapter discusses how to configure and deploy the Oracle Design to Release Integration Pack for Agile Product Lifecycle Management and JD Edwards EnterpriseOne (Design to Release: Agile - JDE E1 Pre-Built Integration).

This chapter includes the following sections:

• Section 21.1, "Deployment Configuration Wizard"

• Section 21.2, "Configuring and Deploying the Design to Release: Agile - JDE E1 Pre-Built Integration"

• Section 21.3, "Verifying Deployment"

• Section 21.4, "Undeploying the Design to Release: Agile - JDE E1 Pre-Built Integration"

21.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Design to Release: Agile - JDE E1 Pre-Built Integration. Enter the details of the Design to Release: Agile - JDE E1 Pre-Built Integration screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

21.1.1 Integration Server Details Screen

All artifacts associated with the integration infrastructure components deploy to the integration server. This screen contains the following fields:

Table 21-1 Integration Server Details Screen Fields

Field	Description
Admin Host Name	Species the admin server. This can be a remote server or the same system where the AIA Pre-Built Integrations Installer is launched. Example: server1.company.com. The Admin Host Name is _________________________________
Admin Port	This is the port number on which the Weblogic Admin server is started. To find this value contact the WebLogic administrator. Example: 7001. The Admin Port is _____________________________________
Domain Name	This is WebLogic server domain corresponding to the Admin Server. Example: domain1 The Domain Name is _______________________________
Admin User	This value is the WebLogic admin user name. To find this value contact your WebLogic administrator. The Admin User is __________________________________
Admin Password	This value is the WebLogic admin password. To find this value contact your WebLogic administrator. The password is _____________________________________
Managed Server	After you enter the Admin Host Name, Admin Port and Admin User, this field populates with managed servers for the domain. Select the managed server from the list. If you are deploying the integration to a SOA cluster, you should select the cluster name in this field. The Managed Server is _______________________________
Managed Port	This field is automatically updated after you select the managed server. If you have configured a SOA Cluster, the SOA Cluster port appears in the list.

21.1.2 Agile Details Screen

Use this screen to enter details related to your Agile PLM instance.

The screen contains the following fields:

Table 21-2 Agile Details Screen Fields

Field	Description
Agile PLM Host	Specifies system name. Example: example1.corp.example.com. Agile PLM Host name is _____________________________
Agile PLM Port	This is the http port. This value depends on the web server port and operating system of your Agile PLM instance. To find this value, contact your Agile PLM administrator. Example: 80. Agile PLM Host is _________________________________
Agile PLM Virtual Path	This value is the same virtual path entered during the Agile PLM installation. Example: Agile. Agile PLM Virtual Path is ______________________________
Agile PLM Integration Username	This is the Agile PLM admin access user name. Example: admin. Agile PLM Integration Username is _________________________
Agile PLM Integration User Password	To find this value, contact your Agile PLM administrator. Agile PLM Integration User Password is _____________________
Agile Version	This is a drop down list of Agile PLM Application Versions.

21.1.3 EnterpriseOne Business Services Information Screen

Use this screen to enter details related to your JD Edwards EnterpriseOne business services.

The screen contains the following fields:

Table 21-3 EnterpriseOne Business Services Information Screen Fields

Field	Description
Web Services Platform	This value is the web services platform that is used by EnterpriseOne. Valid platforms include Oracle WebLogic Server (WLS) and WebSphere Application Server (WAS). This value can be WLS or WAS. Example: WLS Web Services Platform is ____________________________
Web Service Server URL	This value is the location of the EnterpriseOne business service URL. Example: http://den60002jems.example.com:7831/DV900/orhttp://dnitsas2.mlab.jdedwards.com:94/DV900_WEB/services/ Web Service Server URL is __________________________
Environment	This is the environment that the integration proxy user accesses during sign on. To find this value, contact your administrator. Example: DV900. Environment is _________________________________

21.2 Configuring and Deploying the Design to Release: Agile - JDE E1 Pre-Built Integration

This section discusses the integration configuration and deployment process. There are two steps:

1. Configure your integration using the deployment DCW.

2. Deploy the integration to the Fusion Middleware server.

21.2.1 Configuring the Design to Release: Agile - JDE E1 Pre-Built Integration

The screens that appear in the DCW prompt you to enter the data that is required for successful configuration of the Design to Release: Agile - JDE E1 Pre-Built Integration. Keep the completed worksheets the Design to Release: Agile - JDE E1 Pre-Built Integration screens ready before you launch the DCW.

Note:

If you are harvesting content to OER, perform the first three steps. Else start from step 4.

To configure the Design to Release: Agile - JDE E1 Pre-Built Integration:

1. Navigate to /slot/emsxxxx/oracle/Middleware/user_projects/domains/soa_domain/bin/ and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.

2. In the setDomainEnv.sh (or .bat) file, perform a search for USER_MEM_ARGS. Go to the second instance found and replace the following lines:

   USER_MEM_ARGS="-Xms2048m -Xmx2048m -XX:PermSize=256 -XX:MaxPermSize=256 -XX:NewSize=1228 -XX:MaxNewSize=1228"

   WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false"

   with the following changes

   USER_MEM_ARGS="-Xms2048m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:NewSize=1228m -XX:MaxNewSize=1228m"

   WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

3. Restart the server.

4. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

5. Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh for Linux based systems and aiaconfig.bat for Microsoft Windows.

   This launches the AIA DCW.

6. Click Next.

7. Select the Design to Release: Agile - JDE E1 PIP

8. Click Next.

21.2.1.1 Specify Integration Server Details

To specify integration server details:

1. Enter information related to your integration server in the Integration Server Details screen.

2. Click Next.

21.2.1.2 Specify EnterpriseOne Business Services Details

To specify EnterpriseOne Business Services details:

1. Enter information about your EnterpriseOne Business Services details in the EnterpriseOne Business Services Information screen.

   Note:

   The Web Services platform (WLS / WAS) must be selected before entering the Business Service related details.

2. Click Next.

21.2.1.3 Specify Agile PLM Application Details

To specify Agile PLM details:

1. Enter information about your Agile PLM installation in the Agile Details screen.

2. Click Next.

21.2.1.4 Complete Configuration

To complete configuration:

1. Review the configuration information on the Configuration Summary screen.

   Note:

   If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.

   You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the integration. You can configure using the steps described in Section 21.2.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.

2. Click Configure to accept the configuration.

   The system displays progress of the configuration in the Configuration Progress screen.

   The system displays any warnings or errors as necessary. You can review the configuration log for additional details. The configuration log location is displayed in Configuration Progress screen.

3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

4. Click Finish to close the DCW.

21.2.2 Configuring using the Response File

To configure using the response file:

1. Open the response file.

   When you create a response file through OUI, passwords get stored as <SECURE>.

2. Replace the password fields with actual passwords in the response file.

3. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

4. Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh <Response File Location and Name> for Linux based systems and aiaconfig.bat <Response File Location and Name> for Microsoft Windows.

21.2.3 Deploying the Design to Release: Agile - JDE E1 Pre-Built Integration

To deploy the integration to Fusion Middleware server:

1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

2. Run the command for your platform.

   Note:

   When you copy and paste the command in the command line, ensure that there is space between .xml and -. Ensure that there is space between these two when you run undeployment command too.

   Table 21-4 Deployment Command for the Design to Release: Agile - JDE E1 Pre-Built Integration

   Platform	Deployment Command
   Linux Solaris SPARC HP-UX IBM AIX Based Systems	ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<instancename>/config/AIAInstallProperties.xml -DDeploymentPolicyFile=<AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1ConditionalPolicy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1SupplementaryDP.xml -l <AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1DP.log
   Microsoft Windows	ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1DP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia instance>\config\AIAInstallProperties.xml -DDeploymentPolicyFile=<AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1ConditionalPolicy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1SupplementaryDP.xml -l <AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1DP.log

   
   

   Note:

   In Windows 2008, 2008 R2 and Vista, run the command prompt as an administrator (elevated mode). If the command prompt is invoked in normal mode, the integrations are not displayed.

3. Review the log file in the location specified in the command to verify successful deployment.

Oracle AIA ships artifacts in AIA Lifecycle Workbench which can be used in your integrations. These artifacts are created using FMW technologies such as BPEL and Mediator and are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, AIA Deployment Driver (ADD). These are called native artifacts and they include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These artifacts can be modified or new natively supported artifacts can be added using the AIA Lifecyle Workbench and a BOM.xml file can be generated.

AIA integration development teams, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, integration may require artifacts such as, Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

21.3 Verifying Deployment

To verify the Design to Release: Agile - JDE E1 Pre-Built Integration deployment:

1. Open the log files from the following location and look for warnings and error messages:

   • For Linux, Solaris SPARC, HP-UX and IBM AIX Based Systems: Review the install log located at <AIA_HOME>/aia_instances/<instance name>/logs or <AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1DP.log to verify that the integration is successfully installed.

   • For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs or <AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1DP.log to verify that the integration is successfully installed.

2. Confirm that Design to Release: Agile PLM - JDE E1 Pre-Built Integration queues were installed.

   1. Navigate to the PLM integration Queue Management console: http://<server name>:<port number>/queue.

   2. Log in with the server admin user name. To find this information, contact the system administrator.

3. Verify that you can see the following Design to Release: Agile - JDE E1 services were installed.

   1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

   2. Log in with the server admin user name. For access details, contact the system administrator.

   3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

   • ACSAXMLJMSConsumer

   • BillOfMaterialsInitialLoadExtractJDEE1Consumer

   • ChangeStatusDBAdapter

   • CreateEngineeringChangeOrderListJDEE1ProvABCSImpl

   • CreateQueueControlService

   • CreateQueueService

   • EngineeringChangeOrderEBS

   • EngineeringChangeOrderListExtractJDEE1Consumer

   • EngineeringChangeOrderResponseEBS

   • InitialLoadBillOfMaterialsListJDEE1toAgileImpl

   • InitialLoadItemListJDEE1toAgileImpl

   • ItemBalanceEBS

   • ItemBalanceListExtractJDEE1Consumer

   • ItemBalanceResponseEBS

   • ItemEBSV2

   • ItemInitialLoadExtractJDEE1Consumer

   • ItemListExtractJDEE1Consumer

   • ItemResponseEBSV2

   • ProcessEngineeringChangeOrderAgileReqABCSImpl

   • QueueProcessorService

   • QueueProcessorServiceImpl

   • UpdateEngineeringChangeOrderListAgileProvABCSImpl

   • UpdateEngineeringChangeOrderListJDEE1ReqABCSImpl

   • UpdateItemBalanceListAgileProvABCSImpl

   • UpdateItemBalanceListJDEE1ReqABCSImpl

   • UpdateItemListAgileProvABCSImpl

   • UpdateItemListJDEE1ReqABCSImpl

     If you have selected Websphere Application Server (WAS) for your JD Edwards EnterpriseOne web services platform, also verify that these items appear.

   • EngineeringChangeOrderManagerJDEE1WASConnector

   • IntegrationTimeStampManagerJDEE1WASConnector

4. Confirm that the AIA Foundation Manager components were successfully installed.

   1. Navigate to the AIA Console URL: http://<server name>:<port number>/AIA.

   2. Log in with server admin user name.

   3. Navigate to Setup, System to access the Application Registry page.

   4. Check the rows for the following sets of values:

      Table 21-5 Application Registry Page Values for Agile

      Field	Value
      Internal ID	AGILE_01
      System Code	AGILE_01
      System Description	Agile PLM Instance 01
      IP Address	IP address of the Agile PLM system
      URL	URL of the Agile PLM system
      System Type	Agile
      Application Type	PLM
      Version	9.2.2.x(where x can be either 6 or 7) or 9.3.1

      
      

Table 21-6 Application Registry Page Values for JD Edwards

Field	Value
Internal ID	JDE Environment Name
System Code	JDEE1_01
System Description	JDEdwards EnterpriseOne Instance 01
IP Address	<IP of the JDE E1 instance>
URL	<JDE Web Service Server URL>
System Type	JDE
Application Type	ERP
Version	9.0

21.3.1 Validating Security Policies

All SOA composites are protected by Global Policies provided by Foundation Pack as defined in the Security section of the Developer Guide. Additionally individual services for this integration have locally attached security policies.

To validate locally attached security policies:

1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

3. Verify Service Policy attachment.

   1. Find the service policy in the list of policies.

   2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

   3. Change the Subject Type list box to SOA Service.

   4. Validate that all the composites are listed with local attachment to this service policy.

4. Verify Client Policy attachment

   1. Navigate back to Policies screen and find the client policy

   2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

   3. Change the Subject Type list box to SOA Reference.

   4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 21-7 Service Policy Attachments for Design to Release: Agile - JDE E1 Pre-Built Integration

      Composite	Service Policy
      CreateQueueServiceControl	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      CreateQueueService	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      QueueProcessorService	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      QueueProcessorServiceImpl	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      EngineeringChangeOrderManagerJDEE1WASConnector(WAS Install Only)	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      IntegrationTimeStampManagerJDEE1WASConnector(WAS Install Only)	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      InitialLoadItemListJDEE1toAgileImpl	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON
      InitialLoadBillOfMaterialsListJDEE1toAgileImpl	oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      
      

      Table 21-8 No Authentication Client Policy Attachments for Design to Release: Agile - JDE E1 Pre-Built Integration

      Composite	Reference	Client Policy
      InitialLoadItemListJDEE1toAgileImpl	InitialLoadItemListJDEE1toAgileImplV1Extension	oracle/no_authentication_client_policy
      InitialLoadBillOfMaterialsListJDEE1toAgileImpl	InitialLoadBillOfMaterialsListJDEE1toAgileImplExtension	oracle/no_authentication_client_policy

      
      

      Table 21-9 Saml Opt On Client Policy Attachments for Design to Release: Agile - JDE E1 Pre-Built Integration

      Composite	Reference	Client Policy
      QueueProcessorService	BPELSystem.default.QueueProcessorServiceImpl.QueueProcessorServiceImpl_1_0	oracle/aia_wss10_saml_token_client_policy_OPT_ON
      QueueProcessorServiceImpl	ProcessEngineeringChangeOrderAgileReqABCSImpl	oracle/aia_wss10_saml_token_client_policy_OPT_ON
      InitialLoadBillOfMaterialsListJDEE1toAgileImpl	AIAAsyncErrorHandlingBPELProcess	oracle/aia_wss10_saml_token_client_policy_OPT_ON
      InitialLoadItemListJDEE1toAgileImpl	AIAAsyncErrorHandlingBPELProcess	oracle/aia_wss10_saml_token_client_policy_OPT_ON

      
      

      Table 21-10 Wss User Name Token Client Policy Attachments for Design to Release: Agile - JDE E1 Pre-Built Integration

      Composite	Reference	Client Policy
      CreateEngineeringChangeOrderListJDEE1ProvABCSImpl	EngineeringChangeOrderManager	oracle/wss_username_token_client_policy
      UpdateEngineeringChangeOrderListJDEE1ReqABCSImpl	TimeStampManager	oracle/wss_username_token_client_policy
      UpdateItemBalanceListJDEE1ReqABCSImpl	TimeStampManager	oracle/wss_username_token_client_policy
      UpdateItemListJDEE1ReqABCSImpl	TimeStampManager	oracle/wss_username_token_client_policy
      EngineeringChangeOrderManagerJDEE1WASConnector(WAS Install Only)	EngineeringChangeOrderManager	oracle/wss_username_token_client_policy
      IntegrationTimeStampManagerJDEE1WASConnector(WAS Install Only)	TimeStampManagerWAS	oracle/wss_username_token_client_policy
      UpdateItemBalanceListAgileProvABCSImpl	ItemBalanceErrorEBS	oracle/wss_username_token_client_policy
      UpdateItemListAgileProvABCSImpl	ItemErrorResponseEBSV2	oracle/wss_username_token_client_policy
      CreateEngineeringChangeOrderListJDEE1ProvABCSImpl	EngineeringChangeOrderEBSErrorResponse	oracle/wss_username_token_client_policy
      UpdateEngineeringChangeOrderListAgileProvABCSImpl	EngineeringChangeOrderErrorResponseEBS	oracle/wss_username_token_client_policy

      
      

      Table 21-11 Wss Http Token Client Policy Attachments for Design to Release: Agile - JDE E1 Pre-Built Integration

      Composite	Reference	Client Policy
      UpdateEngineeringChangeOrderListAgileProvABCSImpl	ChangeABSService MergeABSService ChangeStatusService	oracle/wss_http_token_client_policy (AgileWebServiceKey)
      ProcessEngineeringChangeOrderAgileReqABCSImpl	ChangeABSService	oracle/wss_http_token_client_policy (AgileWebServiceKey)
      UpdateItemListAgileProvABCSImpl	ItemABSService	oracle/wss_http_token_client_policy (AgileWebServiceKey)
      UpdateItemBalanceListAgileABCSImpl	ItemABSService	oracle/wss_http_token_client_policy (AgileWebServiceKey)

      
      

For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."

For integration implementation, see Oracle Application Integration Architecture Design to Release Agile - JDE E1 Implementation guide.

21.4 Undeploying the Design to Release: Agile - JDE E1 Pre-Built Integration

To undeploy the integration from Fusion Middleware Server:

1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

2. Run the command for your platform.

   Table 21-12 Undeployment Command for the Design to Release: Agile - JDE E1 Pre-Built Integration

   Platform	Undeployment Command
   Linux Solaris SPARC HP-UX IBM AIX Based Systems	ant Uninstall -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<AIA_Instance_name>/config/AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1UndeployDP.xml -DDeploymentPolicyFile=<AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1ConditionalPolicyUndeploy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1SupplementaryUndeployDP.xml -l <AIA_HOME>/pips/AgileToJDEE1/DeploymentPlans/AgileToJDEE1UndeployDP.log
   Microsoft Windows	ant Uninstall -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<AIA_Instance_name>\config\AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1UndeployDP.xml -DDeploymentPolicyFile=<AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1ConditionalPolicyUndeploy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1SupplementaryUndeployDP.xml -l <AIA_HOME>\pips\AgileToJDEE1\DeploymentPlans\AgileToJDEE1UndeployDP.log

   
   

3. Restart the SOA server.

4. Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".