Oracle® Communications ASAP

Release Notes

Release 7.3

E61085-02

March 2021

This document provides release notes for Oracle Communications ASAP release 7.3.

About This Document

This document includes the following sections:

New Features

The new features in this release of ASAP are:

Note:

If you are installing ASAP 7.3.0.3 or a later patch, refer to the corresponding patch readme for updated information on software requirements. Software requirements can change depending on the patch you're installing. The patch readme is packaged with the patch software on My Oracle Support.

Oracle Database 12c Support

ASAP introduces support for Oracle Database 12c.

This support includes:

  • Oracle Database Server 12c (12.1.0.2)

  • Oracle Database Client 11g (11.2.0.4) and 12c (12.1.0.2)

Oracle WebLogic 12c Support

ASAP introduces support for Oracle WebLogic 12c.

This support includes:

  • Oracle WebLogic Server 12c (12.1.2 and 12.1.3)

Oracle Communications Design Studio 7.3

ASAP 7.3 supports Design Studio release 7.3.

Fixes in This Release

This release of ASAP contains enhancements and bug fixes. Refer to the patch readme files available on the My Oracle Support web site:

https://support.oracle.com/

The following table lists the bugs fixed in ASAP 7.3.

Bug No. Related SR Description
21118965 3-10755327581 ASAP now creates OrderFailEvent with the sub-elements in the correct order.
20991387 3-10373695771 There is no longer a memory leak in CTRL Server when it processes a SYS_INFO event that is not mapped to an alarm, or the alarm is not enabled. Hence the CTRL server memory usage no longer increases when it receives a large number of SYS_INFO events continuously.
20824037 3-10480175751 If an additional NEP is configured in ASAP, and it follows a naming convention of NEPXENV_ID (where X represents any character and ENV_ID is the ASAP environment ID), the additional NEP is no longer deleted during an ASAP upgrade.
20682611 3-10418771791 When a web service order contains only one CSDL, the CSDL history and ASDL history of the order can now be viewed in the OCA Client.
19630689 3-9574681571 JNEP now initializes correctly when there is a \u character in an environment variable.
19335652 3-9390049701 If the wls_host in the ASAP.properties file is a hostname starting with t, the cartridges can now be installed and uninstalled using the command line utilities installCartridge and uninstallCartridge.
19288123 3-9186376411 The namespace prefix in an ASAP order no longer causes an XMLParseException error when the JSRP ErrorResponseBean generates createOrderByValueException.
19031852 3-9200714451 SARM no longer terminates when processing work orders with a large number of CSDL parameters.
18679274 3-8925244463 The messages that are generated in the CreateDatabase log during ASAP installation no longer contain the word "rollback," which could be misleading. The messages now use the word "revert."
17973805 3-8212788681 The ASAP export_tool.sh script no longer incorrectly classifies the ASAP Daemon entry as an SRP component.
17740443 3-8005923931 ASAP installation no longer fails on Oracle Enterprise Linux 5.10.
17331739 3-7646560069 SARM no longer crashes because of a non-breaking space (0xA0) in the work order ID.
17301035 3-7583149031 The NEP can now process very large numbers of return CSDL parameters efficiently and is now faster when sending the return parameters to SARM.
17191886 3-7553322656 The getSecureData() method now returns the expected value when the security level is set to SECU_ON.
16998488 3-7389481111 The entire ASDL mapping table is no longer logged each time a JNEP connection request is processed. The ASDL mapping table is now logged only in error scenarios.
16972467 3-7390398971 ASAP can now handle situations where a port conflict is detected on JSRP event listener ports.
16838682 3-7241972891 SARM no longer exits during partial rollback for cases where no ASDLs executed prior to the point-of-no-return ASDL.
16494528 3-6585836671 To eliminate problems, some of the default settings in the ASAP.cfg file are now increased.
16494125 3-6793918921 The waitfor() method now works using SSH protocol.

The following table lists the enhancements included in this release of ASAP.

Known Problems

This section lists the known issues in this release of ASAP.

Bug No. Description
21140323 The OCA thick client uninstaller does not start on Windows using Java 8. The following error is displayed: The wizard cannot continue because of the following error: could not load wizard specified in /wizard.inf (104)

Oracle recommends using Java 7 to uninstall the OCA thick client. For example:

C:\Program Files (x86)\Oracle Communications\ASAP\_uninst>"c:\Program Files\Java\jre7\bin\java.exe" -jar uninstall.jar
20666743 Under maximum throughput scenarios, there may be performance degradation if you are using Oracle Database Client 12c. Oracle recommends using Oracle Database Client 11g (11.2.0.4).
13839793 The ASAP installer fails to upgrade ASAP when you enable SSL in the wizard.

To work around this problem, do not enable SSL in the wizard during the upgrade. Instead, enable SSL after the upgrade is complete:

  1. Using the WebLogic Server Administration Console for the ASAP server domain, enable any disabled SSL listen ports for all administration and managed servers.

  2. Make note of the SSL port values you assigned in the WebLogic Server console.

  3. Open the ASAP.properties file for editing and add or modify the following parameters:

    • wls_ssl_enable: set to true.

    • wls_keystore_file: set to the full path to the keystore file.

    • wls_sslport: set to the SSL listen port for the managed WebLogic server.

    • wls_admin_port: set to the SSL listen port for the administration WebLogic server.

  4. Open the ASAP.cfg file for editing and add or modify the following parameters:

    • BEA_WLS_PORT: set to the SSL listen port for the administration WebLogic server.

See ASAP System Administrator's Guide for information about editing configuration or properties files or using the WebLogic Server Administration Console.

11783843 The OCA installer does not interact with Windows User Accounts Control correctly. This causes the OCA desktop shortcuts to not execute the OCA client.

Open the desktop shortcut properties and manually change the values in the Target and Start in fields. The Target field needs to contain the path to the javaw.exe and the OCAClient lib. The Start in field needs to contain the path to the OCAClient lib.

For example, if the javaw.exe exists in C:\Windows\SysWOW64 and the OCAClient is installed in the default location (C:\Program Files (x86)\Oracle Communications\ASAP), you would modify the fields as below:

  • Modify the Target field to read:

    C:\Windows\SysWOW64\javaw.exe -ms64m -mx64m -classpath "C:\Program Files (x86)\Oracle Communications\ASAP\OCAClient\lib\ocac.jar" architel.OCA.OCAClient.app.OCAMain
    
  • Modify the Start in field to read:

    C:\Program Files (x86)\Oracle Communications\ASAP\OCAClient\lib
    

Deprecated Features

The following feature has been deprecated in the ASAP 7.3 release.

Importing SAR Files Using the GUI

In ASAP 7.3, the ability to import SAR files into Design Studio using the GUI is deprecated and is supported only for backwards compatibility.


Oracle Communications ASAP Release Notes, Release 7.3

E61085-02

Copyright © 2012, 2021, 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.