Release Notes
Release 6.3
E69845-03
February 2017
This document provides information about Oracle Communications MetaSolv Solution Release (MSS) 6.3.
This document consists of the following sections:
MetaSolv Solution 6.3 supports the following software versions:
Oracle Enterprise Linux Server 6.6 (or later) and 7.0 (or later)
Red Hat Enterprise Linux Server 6.6 (or later) and 7.0 (or later)
AIX 7.1 Update 1
HP Itanium 11.31 Update 7
Oracle Solaris 11
Windows Server 2012 R2
Windows 8.1 (client side)
Oracle WebLogic Server 12.2.1.2
Oracle Database 12c R1
JacORB 3.8
Java Development Kit 8
LSR 10.2
Internet Explorer 11
Refer to MSS Planning Guide and MSS Installation Guide for more information on software versions and compatibility.
This section describes the new features introduced in this release.
MSS now supports updated operating systems and underlying software systems. These platform changes align MSS with other Oracle products. See "Software Compatibility" for more information.
With enhanced platform support, MSS now provides MSS Web Services. The MSS Web Services replace the existing MSS XML API functionality. There is a one-to-one mapping from each XML API operation to a web service operation.
MSS can now integrate with other Oracle products or with external applications using web services. The MSS Web Services include a group of web services that address customer, event, inventory, order, activation, and service order activation functionality. This functionality is automatically deployed with MSS. See MetaSolv Solution Web Services Developer's Guide for more information.
MSS can now optionally be enabled to have single sign-on functionality utilizing Oracle Enterprise Single Sign-On Suite Plus (ESSO Suite) software. Single sign-on functionality provides a unified sign-on and authentication across all enterprise resources. It provides identity management functionality eliminating the need for multiple user names and passwords.
MSS now supports the Oracle Database 12c Optimizer which determines the most efficient execution plan for each SQL statement, and provides statistics related to the database.
MSS now supports the EJB3 specification. The home and remote interfaces no longer exist. Integration code that fetches the EJB stub is simplified.
MSS installations now default to an SSL installation. The ”Connect to WebLogic using SSL” check box is enabled by default. Optionally, in a cluster installation, you can enable the SSL port, if it was not previously enabled.
The MSS Application installer now supports IPv6 addresses anywhere IPv4 addresses are referenced.
In previous MSS releases a property was available to bypass authentication for CORBA APIs. To comply with Oracle's security policy, this setting is now removed. MSS access through a CORBA API call always requires authentication. The "validateUserAndPassword" property is now removed from the gateway.ini file and an MSS logon authentication is mandatory.
The CORBA integration now provides SSL support. To set up SSL, refer to MSS CORBA API Developer's Reference.
The MetaSolv Solution 6.3 documentation set includes a new guide entitled MSS Security Guide. This guide provides guidelines and recommendations for setting up MSS in a secure configuration.
The MetaSolv Solution 6.3 documentation set includes a new guide entitled MSS Web Services Developer's Guide. This guide describes the Oracle Communications MetaSolv Solution Web Services. The guide includes information about the MetaSolv Solution Web Service framework that supports web services, the various web services that are available, and how to migrate existing XML API interfaces to web service operations.
New installation parameters need to be set to specific values for optimal results. These settings assure avoiding an existing Optimizer issue. These also provide better database performance and are set with the following values:
optimizer_features_enable=12.1.0.2.1 optimizer_adaptive_features= FALSE
If you are upgrading from an older version of MSS, ensure these parameters are also set as follows:
_b_tree_bitmap_plans = false O7_DICTIONARY_ACCESSIBILITY=TRUE _grant_secure_role = true (since 11.2.0.4)
Because of the enhanced platform support added in MSS 6.3, some features are obsolete. This section describes the items that are obsolete in this release.
MSS now supports Oracle WebLogic Server 12.2.1.2, however this version of WebLogic does not support Oracle WebLogic Integration (WLI). Therefore, MSS no longer supports the Full Installation on WebLogic Integration Domain (WLI) installation type, and no longer support the XML APIs. MSS now provides the MSS Web Services which replace the existing MSS XML API functionality.
Oracle will no longer provide or maintain the Business Objects universes and sample reports previously delivered with MSS Operational Reports. However, you can continue to use your existing MSS Operational Reports solution.
Because of security issues and low utilization, this MSS release removes the Zero Admin Client functionality.
Because of security issues with this functionality, this MSS release removes the Equipment Visualization functionality.
Table 1 lists the known problems in this release.
| Bug Number | Description |
|---|---|
|
25487497 |
Problem If you run MSS Web Services with the client and server computers in different time zones, you receive the following error:
<env:Envelope xmlns:env=
"http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:wsse=
"http://docs.oasis-open.org/wss/2004/01/
oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>wsse:InvalidSecurityToken</faultcode>
<faultstring>Security token failed to validate.
weblogic.xml.crypto.wss.SecurityTokenValidateResult@313c75d4
[status:false][msg UNT Error:Message older than allowed
MessageAge]</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
Workaround Set both the client and server computers to the same time zone. |
|
25419190 |
Problem When running a high volume of MSS Web Service operations, you can encounter the following error:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns0:Fault xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.w3.org/2003/05/soap-envelope">
<faultcode>ns0:Server</faultcode>
<faultstring>Error thrown during Assign Prov Plan API
execution : SQL Exception Thrown Generating and Saving Tasks
for orderKey : 123456. Message: Connection closed</faultstring>
<detail>
<ns0:WSException xmlns:ns0="http://www.openuri.org/">
<message>Error thrown during Assign Prov Plan API execution :
SQL Exception Thrown Generating and Saving Tasks for
orderKey : 123456. Message: Connection closed
</message>
</ns0:WSException>
</detail>
</ns0:Fault>
</S:Body>
</S:Envelope>
Workaround No workaround available. |
|
21614047 |
Problem In running the prodfix database SQL, you may encounter the following error ”ora-01031 insufficient privileges while compiling proc ASAP.SP_DELETE_JOB_QUEUE”. Workaround Apply the SQL patch 23743198. |
|
24524848 |
Problem If you install MSS on a clustered server in an IPv6 environment that has SSL enabled, the MSS application displays a blank page and you are unable to navigate to any module within the application. The MSS server log reflects the following: <Error> <Cluster> <BEA-000198> <All replication calls for cluster ipv6mslvcluster must be made over channel DefaultSecure[https]> Workaround No workaround available. |
|
24480724 |
Problem If you install MSS using IPv6 address in a non-SSL domain, the application fails to connect to the server. This issue occurs because the IPv6 address is not specified within [] (brackets) in the npasplit.ini configuration file located at MSLV_Home\mslv01\appserver\config directory, where MSLV_Home is the directory in which the MSS software is installed and mslv01 is the server home directory. Workaround You can avoid this issue by manually specifying the IPv6 address within square brackets [] in the INI configuration file. |
|
24603024 |
Problem If you install MSS in an IPv6 domain, you may receive the following error in the appserverlog.xml: <log4j:event logger="cmm.INTEGRATION_MANAGER" timestamp="1472128633441" level="ERROR" thread="Thread-37" dateTime="[current date]" debugCode="0" moduleName="cmm.INTEGRATION_MANAGER" messageID="100117" appServerName="DEF_APPSERVER" className="DEF_CLASS" userName="app_api" machineName="XXXXX" productName="nur"> <log4j:message> <![CDATA[Could not create pooled connection. Creating unpooled connection. https://[IPv6 server address]:port: Destination IPv6 server address, port unreachable; nested exception is: java.net.ConnectException: Could not connect to / IPv6 server address; No available router to destination]]> </log4j:message> </log4j:event> Workaround You can ignore this error. |
|
23666384 |
Problem After you log in to MSS in SSL mode, the Runtime Information page displays the non-SSL port (instead of the SSL port) in the EAR version section and in the ASR and LSR applications. Workaround No workaround available. |
|
23233038 |
Problem When running the GetAvailPhysicalPortsOneExist Web Service, the API may return the following error:
”For input string: "{com.metasolv.value.resource.entity.equipment.Equipment: {}{equipmentId//<nnnn>} }"”
Workaround No workaround available. |
|
21945596 |
Problem When running any Web Service, the API may return the following error: ”Failed to copy a message” Workaround The error could occur if the closing tags are not specified properly. To avoid this error, ensure that the closing tags are specified properly. For example: <ser:servicePrimaryKey>123</ser:servicePrimaryKey> |
|
23735794 |
Problem When running the CreateAttachment Web Service, the API may return the following error:
”cvc-complex-type.2.4.b: The content of element 'open:createAttachment' is not complete. One of '{WC[##any]}' is expected.”
Workaround No workaround available. |
|
23717963 |
Problem When running the getDLR operation of the getServiceLocationRequest Web Service, the API may return an empty output. Workaround Run the getDLR operation from the getDlrByKeyRequest Web Service API. |
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.
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.
Oracle Communications MetaSolv Solution Release Notes, Release 6.3
E69845-03
Copyright © 2017, 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.