Oracle® Communications MetaSolv Solution LSR

Installation Guide

Release 10.2

E76094-02

February 2017

Oracle Communications MetaSolv Solution LSR Installation Guide, Release 10.2

E76094-02

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.

Contents

Preface

- Audience

- Related Documents

- Documentation Accessibility

1 Installation and Deployment

- Pre-Installation Checklist

- Installing LSR 10.2

- Applying LSR Database Changes

- Deploying LSR 10.2 on the Application Server in a Single Server Environment

- Deploying LSR 10.2 on the Application Server in a Clustered Environment

- Using LSR with Web Services

- Deploying LSR Web Service on the Application Server in a Single Server Environment

- Deploying LSR Web Service on the Application Server in a Clustered Environment

Preface

This guide provides instructions for installing Local Service Request (LSR) 10.2 and deploying it on the application server.

For future service packs, refer to the respective LSR release notes document for the minimum required version of MetaSolv Solution. You should always install different LSR versions in sequence, starting with the earlier LSR version.

This guide includes some information on third-party software products used by MetaSolv Solution. However, this is limited to information needed to install and perform initial configuration tasks. If you need additional information on a third-party software application, consult the documentation provided by the product's manufacturer.

Audience

This guide is for individuals who install and configure Local Service Request.

Related Documents

For more information, see the following documents in the Oracle Communications MetaSolv Solution LSR documentation set:

- LSR Developer's Reference: Provides information about the Local Service Request API, which is designed to assist you in exchanging local service requests and related documents with trading partners.

- LSR Release Notes: Provides information about supported software, new enhancements, and fixed issues.

For information on the MetaSolv Solution application, see the Oracle Communications MetaSolv Solution documentation set on the Oracle Help Center:

http://docs.oracle.com

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.

1 Installation and Deployment

This chapter explains how to install LSR 10.2 on Oracle WebLogic Server for all platforms.

Pre-Installation Checklist

Ensure the following:

- You have installed Oracle Communications MetaSolv Solution 6.3 or later.

- The following environment variables are set:

PATH=jdkVersion/bin:$PATH
MW_HOME=/oracle/middleware/oracle_home
JAVA_HOME=jdkVersion

where:

- MW_Home is the directory in which Oracle WebLogic Server is installed.

- jdkVersion is the directory location where you installed the JDK.

Note:
LSR 10.2 is supported only on MSS 6.3 and later.

See MSS Installation Guide for information on software versions and requirements.

Installing LSR 10.2

To install LSR 10.2:

1. From MSLV_Home, enter the following command:

java -jar Lsr.R10_2_0.buildNo_M63.jar

where:

- MSLV_Home is the directory in which the MetaSolv Solution software is installed.

- buildNo is the build number.

For example:

java -jar Lsr.R10_2_0.b47_M63.jar

The Select MetaSolv home directory window appears.

2. From the Look In list, select a directory in which the installation program files can be stored and used during the installation process, and then click Select.
A directory named lsr10.2installer is automatically created in the selected directory. Oracle recommends choosing your MSLV_Home directory for this task.

The installation program launches the installation process by running setup.sh (UNIX/Linux) or setup.cmd (Windows) in the MSLV_Home/lsr10.2installer directory.

The welcome screen for the MetaSolv Solution LSR installation appears.

3. Click Next.
The Details window appears.

4. Enter the path and name of the MetaSolv Home directory, MetaSolv Domain directory, and MetaSolv Server directory or click Open to search for the directories.

5. Click Next.
The Install Type window appears.

6. Select one of the following installation types:

- Install all LSR Files

- Install Only LSR EAR File

When prompted for the Install Type, if the environment is a clustered environment, you can choose an option to extract the EAR file only. Use this option to extract the EAR file on the Admin server for deployment to separate managed servers. For a non-clustered environment, choose the option to install and deploy all files.

7. Click Next.
The Install Summary window appears.

8. Click Finish.

Note:
If you are installing LSR in a clustered environment, and if you select admin server as the MetaSolv server, then you must copy the loggingconfig_LSR10.xml file to the MSLV_Home\m63domain\servers\mslvadmin\appserver\config directory.
where:

- MSLV_Home is the directory on the clustered server where MSS is installed; for example, /opt/m63Cluster/cluster.

- m63domain is the domain home directory.

- mslvadmin is directory where the administration server is installed.

Rename this file to loggingconfig_cluster-LSR10.xml and place it in every managed server's config directory at MSLV_Home\mslv01\appserver\config directory, where mslv01 is the name of the directory where the managed server is installed.

Applying LSR Database Changes

You must apply the contents of the prodfixsql directory.

To apply LSR database changes:

1. Run the lsr_master.sql file located in the MSLV_Home/server/appserver/sql/LSR10/prodfixsql directory, where server is the name of the WebLogic server.

2. Run DBHealth, which recompiles all invalid objects.

Deploying LSR 10.2 on the Application Server in a Single Server Environment

Deploying LSR 10.2 on the application server in a single-server environment involves the following:

- Undeploying the existing LSR 10.2 application from the application server

- Deploying LSR 10.2 on the application server

To undeploy LSR 10.2 from the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Control tab, select LSR10.

6. From the Stop list, select Force Stop Now.
Ensure that the state of the LSR 10.2 application has changed from Active to Prepared.

7. Select LSR10 from the Configuration tab and click Delete.
The Delete Application Assistant window appears.

8. Click Yes.

9. Under the Change Center, click Activate Changes.
The LSR 10.2 application is undeployed.

Before you deploy LSR 10.2, ensure the following servers are running:

- Administration server
If it is not running, start it using the following startup script:

For UNIX:

domain_directory/startServerName.sh

For Windows:

domain_directory/startServerName.cmd

where:

- domain_directory is the WebLogic server domain directory.

- ServerName is the name of the administration server.

To deploy LSR 10.2 on the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Configuration tab, click Install.
The Install Application Assistant window appears.

6. Under Current Location, navigate to the directory from which you want to deploy LSR 10.2 (for example, opt/metasolv/mslv01/appserver/deploy), select LSR10.ear, and then click Next.
The Choose targeting style window appears.

7. Select Install this deployment as an application and click Next.

8. Under Source accessibility, select I will make the deployment accessible from the following location.

9. Click Finish.

10. Under the Change Center, click Activate Changes.

11. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

12. On the Control tab, select LSR10.

13. From the Start list, select Servicing all requests.
The Start Application Assistant window appears.

14. Click Yes.
Ensure that the state of the LSR 10.2 application has changed from Prepared to Active.

15. If you receive the following error in the appserver.mss.log file during LSR deployment,

”log4j: ERROR Attempted to append to closed appender named [XMLFileApp”

do the following:

1. Open the loggingconfig_LSR10.xml file located in the MSLV_Home/server/appserver/config directory, where server is the name of the WebLogic server.

2. Remove the following entries:

category name="cmm.LSR"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger"additivity="false"><level value ="error"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileApp"/>
</category>
<category name="LSR"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value="error"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileApp"/>
</category>
<category name="cmm.LSR"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="error"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileApp"/>
</category>

3. Save and close the file.

4. Restart the server.

Deploying LSR 10.2 on the Application Server in a Clustered Environment

If the administration server for the domain is on a machine where no managed server process is running, you can run the LSR installer and select the option to only extract the EAR file. The EAR file must reside on the machine where the admin server is running to deploy to the managed servers in the domain.

Deploying LSR 10.2 on the application server in a clustered-server environment involves the following:

- Undeploying the existing LSR 10.2 application from the application server

- Deploying LSR 10.2 on the application server

To undeploy LSR 10.2 from the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Control tab, select cluster-LSR10.

6. From the Stop list, select Force Stop Now.
Ensure that the state of the LSR 10.2 application has changed from Active to Prepared.

7. On the Configuration tab, select cluster-LSR10 and click Delete.
The Delete Application Assistant window appears.

8. Click Yes.

9. Under the Change Center, click Activate Changes.
The LSR 10.2 application is undeployed.

Before you deploy LSR 10.2 deployment, ensure the following servers are running:

- Administration server
If it is not running, start it using the following startup script:

For UNIX:

domain_directory/startAdminServer.sh

For Windows:

domain_directory/startAdminServer.cmd

where:

domain_directory is the WebLogic server domain directory.

- Managed server or servers
Start any managed servers that are not running using the following startup script:

For UNIX:

domain_directory/startServerName.sh

For Windows:

domain_directory/startServerName.cmd

where:

domain_directory is the WebLogic server domain directory.

ServerName is the name of the administration server.

To deploy LSR 10.2 on the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Configuration tab, click Install.
The Install Application Assistant window appears.

6. Under Current Location, navigate to the directory from which you want to deploy LSR 10.2 (for example, opt/metasolv/mslv01/appserver/deploy).

7. Select cluster-LSR10.ear, and click Next.
The Choose targeting style window appears.

8. Select Install this deployment as an application and click Next.
The Select deployment targets window appears.

9. Under Clusters, select All servers in the cluster.

10. Under Source accessibility, select I will make the deployment accessible from the following location.

11. Click Finish.

12. Under the Change Center area, click Activate Changes.

13. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

14. On the Control tab, select cluster-LSR10.

15. From the Start list, select Servicing all requests.
The Start Application Assistant window appears.

16. Click Yes.
Ensure that the state of the LSR 10.2 application has changed from Prepared to Active.

17. If you receive the following error in the appserver.mss.log file during LSR deployment,

”log4j: ERROR Attempted to append to closed appender named [XMLFileApp”

do the following:

1. Open the loggingconfig_LSR10.xml file located in the MSLV_Home/managedserver/appserver/config directory, where managedserver is the WebLogic managed server.

2. Remove the following entries:

category name="cmm.LSR"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger"additivity="false"><level value ="error"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileApp"/>
</category>
<category name="LSR"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value="error"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileApp"/>
</category>
<category name="cmm.LSR"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false">
<level value ="error"
class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/>
<appender-ref ref="XMLFileApp"/>
</category>

3. Save and close the file.

4. Restart the server.

Using LSR with Web Services

The process for using LSR with Web services involves the following steps:

- Deploying LSR Web Service on the Application Server in a Single Server Environment

- Deploying LSR Web Service on the Application Server in a Clustered Environment

Deploying LSR Web Service on the Application Server in a Single Server Environment

Deploying LSR Web service on the application server in a single-server environment involves the following:

- Undeploying the existing LSR Web service 10.2 application from the application server

- Deploying LSR Web service 10.2 on the application server

To undeploy LSR Web service 10.2 from the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Control tab, select LSR_WebService.

6. From the Stop list, select Force Stop Now.
Ensure that the state of the LSR Web service 10.2 application has changed from Active to Prepared.

7. On the Configuration tab, select LSR_WebService and click Delete.
The Delete Application Assistant window appears.

8. Click Yes.

9. Under the Change Center, click Activate Changes.
The LSR Web service 10.2 application is undeployed.

Before you deploy LSR Web service 10.2, ensure the following servers are running:

- Administration server
If it is not running, start it using the following startup script:

For UNIX:

domain_directory/startServerName.sh

For Windows:

domain_directory/startServerName.cmd

where:

- domain_directory is the WebLogic server domain directory.

- ServerName is the name of the administration server.

To deploy LSR Web service 10.2 on the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Configuration tab, click Install.
The Install Application Assistant window appears.

6. Under Current Location, navigate to the directory from which you want to deploy LSR Web service 10.2 (for example, opt/metasolv/mslv01/appserver/deploy), select LSR_WebService.ear, and then click Next.
The Choose targeting style window appears.

7. Select Install this deployment as an application and click Next.

8. Under Source accessibility, select I will make the deployment accessible from the following location.

9. Click Finish.

10. Under the Change Center, click Activate Changes.

11. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

12. On the Control tab, select LSR_WebService.ear.

13. From the Start list, select Servicing all requests.
The Start Application Assistant window appears.

14. Click Yes.
Ensure that the state of the LSR Web service 10.2 application has changed from Prepared to Active.

Deploying LSR Web Service on the Application Server in a Clustered Environment

Deploying LSR Web service on the application server in a clustered-server environment involves the following:

- Undeploying the existing LSR Web service 10.2 application from the application server

- Deploying LSR Web service 10.2 on the application server

To undeploy LSR Web service 10.2 from the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Control tab, select LSR_WebService.

6. From the Stop list, select Force Stop Now.
Ensure that the state of the LSR Web service 10.2 application has changed from Active to Prepared.

7. On the Configuration tab, select LSR_WebService and click Delete.
The Delete Application Assistant window appears.

8. Click Yes.

9. Under the Change Center, click Activate Changes.
The LSR Web service 10.2 application is undeployed.

Before you deploy LSR Web service 10.2, ensure the following servers are running:

- Administration server
If it is not running, start it using the following startup script:

For UNIX:

domain_directory/startAdminServer.sh

For Windows:

domain_directory/startAdminServer.cmd

where:

domain_directory is the WebLogic server domain directory.

- Managed server or servers
Start any managed servers that are not running using the following startup script:

For UNIX:

domain_directory/startServerName.sh

For Windows:

domain_directory/startServerName.cmd

where:

domain_directory is the WebLogic server domain directory.

ServerName is the name of the administration server.

To deploy LSR Web service 10.2 on the application server:

1. Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console

where:

- ServerName is the name of the administration server.

- Port is the administration server port number.

For example:

http://myserver:7001/console

2. Enter the administration user name and password when prompted and press Enter.

3. Under the Change Center, click Lock & Edit.

4. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

5. On the Configuration tab, click Install.
The Install Application Assistant window appears.

6. Under Current Location, navigate to the directory from which you want to deploy LSR Web service 10.2 (for example, opt/metasolv/mslv01/appserver/deploy), select LSR_WebService.ear, and then click Next.
The Choose targeting style window appears.

7. Select Install this deployment as an application and click Next.

8. Under Source accessibility, select I will make the deployment accessible from the following location.

9. Click Finish.

10. Under the Change Center, click Activate Changes.

11. Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.

12. On the Control tab, select LSR_WebService.ear.

13. From the Start list, select Servicing all requests.
The Start Application Assistant window appears.

14. Click Yes.
Ensure that the state of the LSR Web service 10.2 application has changed from Prepared to Active.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2017, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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.

Hazardous Applications Notice

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.

Trademark Notice

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.

Third-Party Content, Products, and Services Disclaimer

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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

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.