Go to primary content
Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release Release Notes
Release 3.5
E72354-02
  Go To Table Of Contents
Contents

Previous
Previous
 
 

Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release

Release Notes

Release 3.5

E72354-02

March 2016

This document is intended for administrators and describes any known issues in this release of the Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release 3.5.

1 Supported Software Versions

The Design to Release: Agile - EBS Pre-Built Integration requires:

  • Agile Product Lifecycle Management Release 9.3.5, 9.3.4, 9.3.3

  • Oracle E-Business Suite:

    • EBS Release (R) 12-12.2.5 + 22892400:R12.ITM.D

    • EBS Release (R) 12-12.2.4

    • EBS Release (R) 12-12.2.3 + 17237771:R12.INV.C + 19048871:R12:INV.c

    • EBS Release (R) 12 - 12.2.2 + 14769523:R12.INV.C + 17237771:R12.INV.C + 17189026:R12.ITM.D

    • In EBS R12.1.0 or later versions - To deploy GenerateItemNumberService successfully in Agile-Ebiz PIP, you must install Oracle E-Business Suite Integrated SOA Gateway. For more information, see metalink note 556540.1 on My Oracle Support.

    • EBS R12 - 12.1.3 +17014975:R12.INV.B,13370136:R12.INV.B, 10397048:R12.INV.B, 10172716:R12.INV.B, 9945332:R12.INV.B ,13893810:R12.INV.B and 14769523:R12.INV.B + 10632813:R12.OWF.B,10399014:R12.ITM.C, 11654417:R12.ITM.C, 14395360:R12.ITM.C, 13905125:R12.ITM.C

      • For 12.1.3 with VM, apply these additional patches 10009922:R12.CZ.B + 10009066:R12.FND.B.


        Note:

        After applying the patches, restart the EBS server.

      • Database: 11.2.0.1.0 + Patch 9140891 and 9488247

2 Known Issues

This list of Known Issues consists of those found at the time of the initial release. The product may have additional issues found after the initial release and therefore this list is subject to change and is not always comprehensive. Oracle support will continue to track known issues of this product release found on My Oracle Support. Please check for updates at https://support.oracle.com.

Note: Change Orders with Affected Files and no Affected Items are not supported in PIP 3.5. If you attempt to create a workflow for DFCO, you will receive an error message. There is no workaround.

22912341

SYNC ITEM FAILS FOR A PART JUST CREATED WITH NPR NUMBER

Steps to Reproduce:

  1. On the Agile Web Client, create New > Item > Part.

  2. In the Create New dialog, select NPR Number to receive an autonumber from EBS.

  3. Click Save to close the Create New dialog.

  4. Add a description for the part, then click Save.

  5. Click Action Menu > Sync Item.

    Actual Result: SyncItem fails with an error message.

Workarounds:

If the part number does not matter: Click Action Menu > NPR Number to get a new number, then click Action Item > Sync Item again.

or

If you want to keep the same part number: Create an ECO for the part and release the ECO to EBS.

22928801

VALIDATEECO FAIL AFTER SYNCITEM FAIL FROM CREATE NEW > NPR

Steps to Reproduce:

  1. Create New > Item > Part and get an autonumber by NPR.

  2. Add a description to the part, then Save.

  3. From the Action Menu, choose SyncItem. An error is received (Known Issue 22912341).

  4. Create an ECO against this part and set Rev >='B'.

  5. Submit the ECO.

    Actual Result: ValidateECO flow may fail.

Workaround: Ignore the ValidateECO failure and continue to Release. The ValidateECO failure does not affect functionality.

22600634

PERFORMANCE ISSUE WHILE PIP 3.5 INTEGRATED EBIZ 12.2.5

Issue: Some process may encounter intermittent failures as described in the error messages. This may be due to the performance of your E-Business server.

Workaround: Increase the JTA/Transaction/BPEL. Refer to ID 8, ID 9 and ID 10 in Appendix G, "Error Handling" of the Agile PLM Integration Pack for Oracle E-Business Suite: Design to Release Implementation Guide, Release 3.5.

20348963

AIA AGILETOEBIZ DEPLOY FAILED ON LINUX CLUSTER ENV

Steps to Reproduce:

  1. Install PIP 3.5 on a Linux cluster.

  2. Run the command to deploy the AgileToEbiz PIP.

    Actual Result: Deployment fails.

Workaround: Edit the createJMSCluster.py file, located in the $FMW_HOME/soa/aiafp/Install/AID/lib/py directory with the following information:

Add "break;"  to createJMSCluster.py:
       jmsServerMbean = createJMSServer(servermb, str(dSTargetServers[0]), dataStore)
       subDepMbean.addTarget(jmsServerMbean)
       break;
else:
        print 'WARNING!!! Data Store already exists!!'

20322592

Issue: TWO COMPOSITES FAIL TO START ON WINDOWS ALTHOUGH DEPLOYED SUCCESSFULLY

Steps to Reproduce:

  1. Install Java, Oracle Database, WebLogic, and SOA on Windows.

  2. Run Repository Creation Utility and configure the Agile PLM system.

  3. Start the Node Manager, the Admin Server, and the SOA server.

  4. Install PIP 3.5 and deploy it.

  5. Restart SOA Server.

  6. Log in to Enterprise Manager and check composites.

    Actual Result: Two composites, ACSAXMLJMSConsumer and SyncBillOfMaterialsConfigurationEbizJMSConsumer, failed to start.

    Expected Result: All composites start successfully.

Workaround: After deploying the PIP, go to the $FMW_HOME/soa/soa/connectors directory and open the JmsAdapter_plan.xml file. Change all "\" to "/". Save and close the xml file. Restart AIA.

20724550

Issue: VARMGMT FLOW FAILED DUE TO AGILE CONFIGTOOL ERROR

Steps to Reproduce:

  1. Enable Web Service Security (WSS) and deploy PIP with supporting Agile WSS.

  2. In Agile PLM, create a Model and create a Part in the Model's BOM.

  3. Create an ECO against the Model and the Part.

  4. Set the correct revision and release it to EBS.

  5. In EBS, implement the ECO.

  6. In Agile PLM, go to the Instance tab of the Model.

  7. Add and create a new Part.

  8. Select the part and click Launch Configurator.

  9. Log in to the EBS Configurator and click Finish.

  10. Check the instance status, the flow status, and the AIA log.

  11. Check the result.

    Actual Result: The instance Part is still in draft status. The flow status in Enterprise Manager and the AIA log contain error messages.

    Expected Result: No error messages should appear.

Workaround: This issue only occurs with Agile PLM 9.3.4. On the Agile PLM system. open the application.ear > VMService.war file. In the WEB-INF folder, replace the contents of web.xml and weblogic.xml with the following:

Example 1 web.xml

- 
<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 
2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd"> 
 
<web-app id="AgileVMServiceWebApp"> 
 <display-name>Agile VM Web Services</display-name> 
 <description>Agile VM Web Service Web-App</description> 
 
  <servlet> 
    <servlet-name>ConfiguratorTerminationServicehttp</servlet-name> 
     
<servlet-class>com.agile.pc.cmserver.varmgt.aia.cfg.ConfiguratorTerminationSer 
vice</servlet-class> 
    <load-on-startup>0</load-on-startup> 
  </servlet> 
  <servlet-mapping> 
    <servlet-name>ConfiguratorTerminationServicehttp</servlet-name> 
    <url-pattern>/services/ConfiguratorTerminationService</url-pattern> 
  </servlet-mapping> 
 
  <session-config> 
    <session-timeout>25</session-timeout> 
  </session-config> 
 
  <mime-mapping> 
    <extension>wsdl</extension> 
     <mime-type>text/xml</mime-type> 
  </mime-mapping> 
 
  <mime-mapping> 
    <extension>xsd</extension> 
    <mime-type>text/xml</mime-type> 
  </mime-mapping> 
 
 
</web-app> 

Example 2 weblogic.xml

<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 
8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd" > 
 
<weblogic-web-app> 
@      <security-role-assignment> 
        <role-name>AgileUser</role-name> 
        <principal-name>Administrators</principal-name> 
        <principal-name>everyone</principal-name> 
@      </security-role-assignment> 
     <reference-descriptor> 
        <resource-description> 
  <res-ref-name>jdbc/AgileContentPool</res-ref-name> 
  <jndi-name>ContentDataSource</jndi-name> 
        </resource-description> 
     </reference-descriptor>   
     <session-descriptor>   
        <session-param>     
           <param-name>URLRewritingEnabled</param-name>     
           <param-value>false</param-value> 
        </session-param> 
        <session-param> 
           <param-name>PersistentStoreType</param-name> 
           <param-value>replicated_if_clustered</param-value> 
        </session-param> 
     </session-descriptor> 
     
</weblogic-web-app> 

20667175

Issue: ACSAXMLJMSCONSUMER CREATE QUEUE FAILED AFTER SWITCHING TO 933

Steps to Reproduce:

  1. Set up a PIP 3.5 environment with Agile PLM 9.3.4 or 9.3.5 and prepare another Agile PLM 9.3.3.

  2. Use SwitchAgileDP.xml to switch the PIP to the Agile PLM 9.3.3 system.

  3. Log in to the Agile PLM 9.3.3 system.

  4. Create a part and submit it to trigger a Validate ECO.

  5. Check the results in the AIA queue and Enterprise Manager.

    Actual Result: Nothing is created in the queue. On Enterprise Manager, ACSAXMLJMSConsumer failed to create queue, resulting in an error message.

    Expected Result: Create queue successfully and ValidateECO works as designed.

Workaround: PIP 3.5 drops support of SwitchAgileDP.xml. To switch between difference versions of Agile, you must undeploy PIP 3.5, update Agile information in the AIAInstallProperties.xml file, and then re-deploy the PIP.

20259313

Issue: AIA AGILE2EBIZ PIP UNDEPLOY FAILED

Steps to Reproduce:

  1. Connect to AIA server.

  2. Undeploy PIP 3.5.

  3. Check the file, AgileToEbizUndeployDP.log.

  4. Check the result.

    Actual Result: Undeploy fails with the following exception message:

    java.lang.Exception:Error connecting to server, please check to see if the server exists.

Workaround: Manually update the AIDConfigurationLibraryTasks.xml file, located in the $SOA_HOME/aiafp/Install/AID/lib directory, by removing the delete keyFile and propFile action in line 875:

<!--delete file="${application.tmpdir}/keyFile"/>
<delete file="${application.tmpdir}/propFile"/-->

3 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


Release Notes, Release 3.5

E72354-02

Copyright © 2007, 2016 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.