Unifier Upgrade Guide for On-Premises
Version 18
August 2018
Contents
Overview ........................................................................................................................................... 5
Upgrading Unifier 9.9.4 to Unifier [Link] ...................................................................................... 7
Upgrading Unifier [Link] to Unifier [Link] .............................................................................. 11
Upgrading Unifier [Link] (and Later Versions) to Unifier [Link] ............................................. 15
Upgrading Unifier [Link] (and Later Versions) to Unifier [Link] ............................................. 19
Appendix A: Additional Information................................................................................................. 23
Legal Notices .................................................................................................................................. 25
3
Overview
Depending on which version of Unifier you are using, the following major updates must take
place in order to upgrade Unifier to the most recent version:
If you have 9.9.x:
a. Upgrade to 9.9.4
For details about upgrading Unifier versions earlier than 9.9.4 to Unifier 9.9.4, refer to the
associated Media Pack Readme files. The Media Pack Readme file provides information
about backup, uninstall, install, and data migration. For assistance, contact Oracle
Support.
b. Upgrade 9.9.4 to [Link]
c. Upgrade to the most recent version
If you have [Link] or [Link] (and later versions):
a. Upgrade to [Link]
b. Upgrade to the most recent version
If you have [Link] (and later versions), then upgrade to the most recent version.
The Unifier Upgrade Guide provides instructions for:
Upgrading Unifier 9.9.4 to Unifier [Link] (on page 7)
Upgrading Unifier [Link] to Unifier [Link] (on page 11)
Upgrading Unifier [Link] (and Later Versions) to Unifier [Link] (on page 15)
Upgrading Unifier [Link] (and Later Versions) to the latest Unifier version.
Audience
The Unifier network administrator
The Unifier database administrator
The Unifier Administrator
5
Upgrading Unifier 9.9.4 to Unifier [Link]
Workflow
1) Backup a copy of the file repository and database
2) Uninstall Unifier 9.9.4
3) Install and deploy Unifier [Link] on each application server
4) Migrate data to Unifier [Link]
The following sections provide details.
Backup a copy of the file repository and database
1) Follow your organization procedures and create backup files of the following:
Unifier file repository
Unifier database
2) Backup the configurator settings as follows:
a. In the Unifier Home folder, find the configuration settings for Unifier in the
weblogic/configurator directory.
b. Copy the [Link] file to a safe location. The file locations are set while
configuring Unifier and can be found in the Unifier Configurator.
Uninstall Unifier 9.9.4
1) Stop the Unifier service on all machines within the environment (including a cluster
environment if it exists).
2) Ensure all open windows related to Unifier are closed, including any administrative tools
such as Windows Services.
3) From the Windows Start menu, click Programs, Unifier [version no.], Uninstall Unifier.
4) Click the Uninstall button. This will uninstall Unifier, remove the services, and remove the
directory.
5) When prompted, click Yes to remove all the files in the Unifier directory.
6) Ensure that the WebLogic Admin server is running.
7) Navigate to the Unifier server and verify that the files and the Unifier directory were
successfully removed.
8) Before rebooting the server, restart the World Wide Web Publishing Service from the
Services window.
9) If you receive a message that all of the files could not be removed, reboot the server before
continuing.
10) After restarting the server, open Windows Explorer, right-click the Unifier folder and select
Delete.
Install and deploy Unifier [Link] on each application server
1) Install the new version of Unifier by following instructions in the Unifier Installation Guide
(WebLogic).
7
Unifier Upgrade Guide for On-Premises
2) After a successful installation, proceed to migrate data to Unifier [Link]. See the following
section.
Note: During migration all staging environments are automatically
renamed and converted as Development environments. Once the
migration is complete, you must have only one Development
environment. Ensure that other Development environments, if any, are
converted/configured to Test environment.
Migrating from Unifier 9.9.4 to Unifier [Link]
Note: During the preparation of Development and Production
environments, do not conduct any design updates on the Production
environment. If you want to bring in designs from the 9.9.x Development
environment, you can do so only by using the XML Design Export and
Import mechanism, which will be available on 9.9.x and 9.11 uDesigner.
Migrating 9.9.4 data to [Link] Development Environment
1) Prepare a new database for [Link] with a database import from the 9.9.4 Production
database.
2) Prepare the [Link] Unifier environment with the “Production” configuration, and connect it
to the new database created in the previous step.
3) Perform data migration on the [Link] Unifier environment. This includes running the
End-Of-Migration target on the [Link] Unifier environment.
4) On the Application Server, open a browser and type this URL in the Address bar:
[Link]
The Unifier Migration log window opens. If there are any data migration targets listed in the
log window, then you must run all the listed data migrations before finally executing the
End-Of-M Migration step.
5) Run the migration script, select End of Migration, click Run, and click Yes to confirm. A
window opens notifying you that the migration has been completed successfully.
6) Close the browser. The run date on the migration log will update after a successful migration.
7) Log in to the [Link] Unifier environment as company administrator (ootbadmin) and
navigate to Administration Mode > uDesigner.
8) Verify that all the designs were successfully migrated. If a design was not successfully
migrated, the Version field for that design has a value -1 (minus on) and the id field has a
value included in the [ ] (brackets). If you see any instances that did not migrate successfully,
proceed as follows:
a. Save the current Unifier log file which will be used to identify the issues.
b. Contact Oracle Support. Oracle Support will identify the problems and may recommend
updating the current production environment to have those designs brought to a stage
where they are suitable for [Link].
c. Repeat the previous steps in this procedure if you need to apply any updates to the
current production environment.
8
Upgrading Unifier 9.9.4 to Unifier [Link]
9) If there are no errors, reconfigure the application server to Development. This is your new
[Link] Development environment.
10) As a company administrator, you might want to disable most of the production users in the
new Development environment.
11) Proceed to migrating [Link] to [Link] Production environment.
Migration of 9.9.4 data to [Link] Production Environment
Perform this procedure after you finish creating a new [Link] Development environment from
the 9.9.4 Production database.
Note: When you complete the following procedure, both the Unifier
[Link] Development environment and the Unifier [Link] Production
environment are built and ready to use.
1) Prepare the Unifier [Link] environment with the 9.9.4 production configuration and connect
it to the production database.
2) Perform data migration on the [Link] Unifier Production environment. This includes
running the End-Of-Migration target on the [Link] Unifier environment.
3) On the Application Server, open a browser and type this URL in the Address bar:
[Link]
The Unifier Migration log window opens. If there are any data migration targets listed in the
log window, then you must run all the listed data migrations before finally executing the
End-Of-M Migration step.
4) Run the migration script, select End of Migration, click Run, and click Yes to confirm. A
window opens notifying you that the migration has been completed successfully.
5) Close the browser. The run date on the migration log will update after a successful migration.
6) Log in to the [Link] Unifier environment as company administrator (ootbadmin) and
navigate to Administration Mode > uDesigner)
7) Verify that all the designs were successfully migrated. No errors occur at this stage because
errors have been identified and resolved when building the [Link] Unifier Development
environment.
The Unifier [Link] Development environment and the Unifier [Link] Production environment
are built and ready to use.
9
Upgrading Unifier [Link] to Unifier [Link]
Workflow
1) Backup a copy of the file repository and database
2) Uninstall Unifier [Link]
3) Install and deploy Unifier [Link] on each application server
4) Migrate data to Unifier [Link]
The following sections provide details.
Backup a copy of the file repository and database
1) Follow your organization procedures and create backup files of the following:
Unifier file repository
Unifier database
2) Backup the configurator settings as follows:
a. In the Unifier Home folder, find the configuration settings for Unifier in the
weblogic/configurator directory.
b. Copy the [Link] file to a safe location. The file locations are set while
configuring Unifier and can be found in the Unifier Configurator.
Uninstall Unifier [Link]
1) Stop the Unifier service on all machines within the environment (including a cluster
environment if it exists).
2) Ensure all open windows related to Unifier are closed, including any administrative tools
such as Windows Services.
3) From the Windows Start menu, click Programs, Unifier [version no.], Uninstall Unifier.
4) Click the Uninstall button. This will uninstall Unifier, remove the services, and remove the
directory.
5) When prompted, click Yes to remove all the files in the Unifier directory.
6) Ensure that the WebLogic Admin server is running.
7) Navigate to the Unifier server and verify that the files and the Unifier directory were
successfully removed.
8) Before rebooting the server, restart the World Wide Web Publishing Service from the
Services window.
9) If you receive a message that all of the files could not be removed, reboot the server before
continuing.
10) After restarting the server, open Windows Explorer, right-click the Unifier folder and select
Delete.
Install and deploy Unifier [Link] on each application server
1) Install the new version of Unifier by following instructions in the Unifier Installation Guide
(WebLogic).
11
Unifier Upgrade Guide for On-Premises
2) After a successful installation, proceed to migrate data to Unifier [Link]. See the following
section.
Note: During migration all staging environments are automatically
renamed and converted as Development environments. Once the
migration is complete, you must have only one Development
environment. Ensure that other Development environments, if any, are
converted/configured to Test environment.
Migrating from Unifier [Link] to Unifier [Link]
Note: During the preparation of Development and Production
environments, do not conduct any design updates on the Production
environment. If you want to bring in designs from the 9.9.x Development
environment, you can do so only by using the XML Design Export and
Import mechanism, which will be available on 9.9.x and 9.11 uDesigner.
Migrating [Link] data to [Link] Development Environment
1) Prepare a new database for [Link] with a database import from the [Link] Production
database.
2) Prepare the [Link] Unifier environment with the “Production” configuration, and connect it
to the new database created in the previous step.
3) Perform data migration on the [Link] Unifier environment. This includes running the
End-Of-Migration target on the [Link] Unifier environment.
4) On the Application Server, open a browser and type this URL in the Address bar:
[Link]
The Unifier Migration log window opens. If there are any data migration targets listed in the
log window, then you must run all the listed data migrations before finally executing the
End-Of-M Migration step.
5) Run the migration script, select End of Migration, click Run, and click Yes to confirm. A
window opens notifying you that the migration has been completed successfully.
6) Close the browser. The run date on the migration log will update after a successful migration.
7) Log in to the [Link] Unifier environment as company administrator (ootbadmin) and
navigate to Administration Mode > uDesigner.
8) Verify that all the designs were successfully migrated. If a design was not successfully
migrated, the Version field for that design has a value -1 (minus on) and the id field has a
value included in the [ ] (brackets). If you see any instances that did not migrate successfully,
proceed as follows:
a. Save the current Unifier log file which will be used to identify the issues.
b. Contact Oracle Support. Oracle Support will identify the problems and may recommend
updating the current production environment to have those designs brought to a stage
where they are suitable for [Link].
c. Repeat the previous steps in this procedure if you need to apply any updates to the
current production environment.
12
Upgrading Unifier [Link] to Unifier [Link]
9) If there are no errors, reconfigure the application server to Development . This is your new
[Link] Development environment.
10) As a company administrator, you might want to disable most of the production users in the
new Development environment.
11) Proceed to migrating [Link] to [Link] Production environment.
Migration of [Link] data to [Link] Production Environment
Perform this procedure after you finish migrating [Link] to [Link] Development environment.
Note: When you complete the following procedure, both the Unifier
[Link] Development environment and the Unifier [Link] Production
environment are built and ready to use.
1) Upgrade the current Unifier production environment from [Link] to [Link].
2) Perform data migration on the [Link] Unifier Production environment. This includes
running the End-Of-Migration target on the [Link] Unifier environment.
3) On the Application Server, open a browser and type this URL in the Address bar:
[Link]
The Unifier Migration log window opens. If there are any data migration targets listed in the
log window, then you must run all the listed data migrations before finally executing the
End-Of-M Migration step.
4) Run the migration script, select End of Migration, click Run, and click Yes to confirm. A
window opens notifying you that the migration has been completed successfully.
5) Close the browser. The run date on the migration log will update after a successful migration.
6) Log in to the [Link] Unifier environment as company administrator (ootbadmin) and
navigate to Administration Mode > uDesigner)
7) Verify that all the designs were successfully migrated. No errors occur at this stage because
errors have been identified and resolved when building the [Link] Unifier Development
environment.
The Unifier [Link] Development environment and the Unifier [Link] Production environment
are built and ready to use.
13
Upgrading Unifier [Link] (and Later Versions) to
Unifier [Link]
Workflow
1) Backup a copy of the file repository and database
2) Uninstall Unifier [Link] (and later versions)
3) Install and deploy Unifier [Link] on each application server
4) Migrate data to Unifier [Link]
The following sections provide details.
Backup a copy of the file repository and database
1) Follow your organization procedures and create backup files of the following:
Unifier file repository
Unifier database
2) Backup the configurator settings as follows:
a. In the Unifier Home folder, locate the configuration settings for Unifier in the
/configurator directory.
b. Copy the [Link] file to a safe location.
Note: The file locations are set while configuring Unifier and can be
found in the Unifier Configurator.
Uninstall the current version of Unifier
Uninstalling Unifier from WebLogic
If WebLogic was deployed using ".sh" or ".bat," then:
1) Ensure WebLogic is running.
2) Open the WebLogic directory within the Unifier Home folder.
For Windows installations, run [Link].
For Linux installations, run [Link].
If prompted, enter the WebLogic user name and password.
If WebLogic was deployed using "[Link]," then:
1) Go to WebLogic console > Deployments
2) Select Unifier Deployment name, stop, and Delete.
Install and deploy Unifier [Link] on each application server
1) Install the new version of Unifier by following instructions in the Unifier Installation Guide.
2) After a successful installation, proceed to migrate data to the latest version of Unifier.
15
Unifier Upgrade Guide for On-Premises
Note: During migration all staging environments are automatically
renamed and converted as Development environments. Once the
migration is complete, you must have only one Development
environment. Ensure that other Development environments, if any, are
converted/configured to Test environment.
Migrating data from Unifier [Link] (and later versions) to Unifier [Link]
Note: During the preparation of Development and Production
environments, do not conduct any design updates on the Production
environment. If you want to bring in designs from the 9.9.x Development
environment, you can do so only by using the XML Design Export and
Import mechanism, which will be available on 9.9.x and 9.11 uDesigner.
Migrating [Link] (and later versions) data to [Link] Development Environment
1) Prepare the Unifier [Link] environment with the Development configuration, and connect it
to the Development database.
2) Migrate data to the Unifier [Link] environment as follows:
a. On the Application Server, open a browser and enter the following URL:
[Link]
The Unifier Migration log window opens.
b. If there are any data migration targets listed in the log window, then you must run all the
listed data migrations.
c. After running all listed data migrations, select the End of Migration script and click Run.
d. Click Yes to confirm. A message displays indicating the migration was completed
successfully.
e. Close the browser. The run date on the migration log will update after a successful
migration.
This completes data migration process in the Development environment ([Link] (and later
versions) to [Link]).
Migrating [Link] (and later versions) data to [Link] Production Environment
Note: Perform this procedure after you have completed migrating the
Development Environment from [Link] (and later versions) to [Link]
.
1) Prepare the Unifier [Link] environment with the production configuration and connect it to
the production database.
2) Migrate data to the Unifier [Link] production environment as follows:
a. On the Application Server, open a browser and enter the following URL:
[Link]
The Unifier Migration Log window opens.
b. If there are any data migration targets listed in the Unifier Migration log window, you must
run all the listed data migrations.
16
Upgrading Unifier [Link] (and Later Versions) to Unifier [Link]
c. After running all listed data migrations, select the End of Migration script and click Run.
d. Click Yes to confirm. A window opens notifying you that the migration was completed
successfully.
e. Close the browser. The run date on the migration log will update after a successful
migration.
This completes data migration process in the Production environment ([Link] (and later
versions) to [Link]).
17
Upgrading Unifier [Link] (and Later Versions) to
Unifier [Link]
Note: Pre-17.6 configuration package zip files will not be available in the
log. If you want to view your pre-17.6 log content, Oracle recommends
that you print your pre-17.6 log content prior to the upgrade.
The following procedure applies to upgrading Unifier [Link] and later version to Unifier
[Link].
Workflow
1) Backup a copy of the file repository and database
2) Uninstall the current version of Unifier
3) Install and deploy Unifier [Link] on each application server
4) If you are migrating from a version before 17.0 and you have changed your server, copy the
[Link] file from your base server to the new server in the /configurator
directory.
5) Migrate data to Unifier [Link]
The following sections provide details.
Backup a copy of the file repository and database
1) Follow your organization procedures and create backup files of the following:
Unifier file repository
Unifier database
2) Backup the configurator settings as follows:
a. In the Unifier Home folder, locate the configuration settings for Unifier in the
/configurator directory.
b. Copy the [Link] file to a safe location.
Note: The file locations are set while configuring Unifier and can be
found in the Unifier Configurator.
Migrating Reports and Dashboard files
Note: This section is applicable only if you are migrating from a version
before 17.0.
Ensure that the path specified for the reports and dashboard files in the [Link] file
is accessible and contains the report and dashboard files. If your files are stored in a different
server from the previous release, ensure that the locations are accessible to the new server and
you have maintained the existing report and dashboard folder hierarchy.
19
Unifier Upgrade Guide for On-Premises
Uninstall the current version of Unifier
Uninstalling Unifier from WebLogic
If WebLogic was deployed using ".sh" or ".bat," then:
1) Ensure WebLogic is running.
2) Open the WebLogic directory within the Unifier Home folder.
For Windows installations, run [Link].
For Linux installations, run [Link].
If prompted, enter the WebLogic user name and password.
If WebLogic was deployed using "[Link]," then:
1) Go to WebLogic console > Deployments.
2) Select Unifier Deployment name, Stop, and Delete.
Install and deploy Unifier [Link] on each application server
1) Install the new version of Unifier by following instructions in the Unifier Installation Guide.
2) After a successful installation, proceed to migrate data to the latest version of Unifier.
Note: During migration all staging environments are automatically
renamed and converted as Development environments. Once the
migration is complete, you must have only one Development
environment. Ensure that other Development environments, if any, are
converted/configured to Test environment.
Migrating data from Unifier [Link] (and later versions) to Unifier [Link]
Note: During the preparation of the Development and Production
environments, do not conduct any design updates on the Production
environment. If you want to bring in designs from the 9.9.x Development
environment, you can do so only by using the XML Design Export and
Import mechanism, which will be available on 9.9.x and 9.11 uDesigner.
Migrating data from Unifier [Link] (and later versions) to Unifier [Link] Development
Environment
To determine if you need to migrate data, check the following:
Open a browser and navigate to Unifier. If you see the message, "Login disabled until end of
migration.," then you need to continue the steps below; otherwise, you do not need to proceed
with migrating data.
1) Prepare the Unifier [Link] environment with the test configuration, and connect it to the
Development database.
2) Migrate data to the Unifier [Link] environment as follows:
a. Open a browser and enter the URL you use to access Primavera Unifier, followed by
/bluedoor/admin.
b. Login as Administrator and navigate to Migration Log.
20
Upgrading Unifier [Link] (and Later Versions) to Unifier [Link]
c. If there are any data migration targets listed in the log window, then you must run all the
listed data migrations.
d. After running all listed data migrations, select the End of Migration script and click Run.
e. Click Yes to confirm. A message displays indicating that the migration was completed
successfully.
f. The run date on the migration log will update after a successful migration.
g. Logout.
h. Log in as Company user. This is will automatically trigger migration scripts responsible for
migrating the reports and dashboard files to the central file repository.
This completes data migration process in the Development environment (Unifier [Link] (and
later versions) to [Link]).
Migrating data from Unifier [Link] (and later versions) to Unifier [Link] Production
Environment
To determine if you need to migrate data, check the following:
Open a browser and navigate to Unifier. If you see the message, "Login disabled until end of
migration.," then you need to continue the steps below; otherwise, you do not need to proceed
with migrating data.
Note: Perform this procedure after you have completed migrating the
Development Environment from Unifier [Link] (and later versions) to
[Link].
1) Prepare the Unifier [Link] environment with the production configuration and connect it to
the production database.
2) Migrate data to the Unifier [Link] production environment as follows:
a. Open a browser and enter the URL you use to access Primavera Unifier, followed by
/bluedoor/admin.
b. Login as Administrator and navigate to Migration Log.
c. If there are any data migration targets listed in the log window, then you must run all the
listed data migrations.
d. After running all listed data migrations, select the End of Migration script and click Run.
e. Click Yes to confirm. A message displays indicating that the migration was completed
successfully.
f. The run date on the migration log will update after a successful migration.
g. Logout.
3) Log in as Company user. This is will automatically trigger migration scripts responsible for
migrating the reports and dashboard files to the central file repository.
This completes data migration process in the Production environment (Unifier [Link] (and later
versions) to [Link]).
21
Appendix A: Additional Information
This appendix provides additional information about upgrading products that are used in Unifier.
SharePoint
If you are using SharePoint, migrate your Unifier documents to SharePoint. Refer to the
following for more instructions:
Microsoft site for instructions on how to perform the SharePoint upgrade.
The Unifier Content Repository Configuration Guide ("Configuring Microsoft SharePoint"
section) on how to enable CMIS site features.
Note: For the full list of system requirements, applications, and
application version levels refer to the Primavera Unifier Tested
Configurations in the Primavera Unifier Documentation Library.
The following steps explain how to migrate Unifier documents to support SharePoint CMIS:
1) Download the current version of the Primavera Unifier Tools file from the Oracle Software
Delivery Cloud ([Link]
2) Copy the [Link] file and save it locally.
3) Unzip the [Link] file on a server where you can connect to both the Unifier
database and the SharePoint server.
Note: JDK 7 or higher should be installed on the machine where you
want to execute this program.
4) Ensure that JAVA_HOME environment variable is set correctly on the SharePoint server.
Windows server
In Windows server, execute echo %JAVA_HOME% to check if JAVA_HOME is set. If
JAVA_HOME is not set use "set JAVA_HOME=<Java install dir>" from the terminal,
where you are planning to execute the script.
Linux server
In Linux server you can check the setting by executing "echo $JAVA_HOME" command. If
JAVA_HOME is not set, then execute "export JAVA_HOME=<Java install dir>" from the
terminal, where you are planning to execute the script.
5) Edit "[Link]" file under "conf" folder to specify SharePoint server and
Unifier database details. The following are the properties present in the [Link] file:
SharePoint
[Link] = enter the user name for your content repository.
[Link] = enter the password for the user name you entered above.
[Link] = enter the machine name or IP address of the SharePoint server.
(Example: [Link]
[Link] = enter the domain where the SharePoint server resides.
23
Unifier Upgrade Guide for On-Premises
[Link] = enter the site name used to store the Unifier documents.
[Link] = enter the name of the document library where Unifier documents are
stored.
Unifier
[Link] = enter oracle if Unifier is connected to Oracle database, or mssql if Unifier is
connected to Microsoft SQL server.
[Link] = enter the host name of the computer where you installed the database.
[Link] = enter Oracle SID or MS SQL server instance ID. If you did not specify
an instance name when configuring the SQL Server, leave the Instance ID field blank.
Otherwise, enter the Instance ID.
[Link] = enter the Port number to be used by Unifier to communicate with the
database.
[Link] = enter the database login user account name to be used by Unifier.
[Link] = enter the database login user account password to be used by Unifier.
Linux
If running from a Linux server, assign executable permission to the Shell script, [Link] and
the [Link] file under the bin folder.
Windows
Go to the bin folder and execute "./[Link]" on Linux or "[Link]" (refer to the log file
"bin/log/[Link]" for the details of script execution).
Once the script is completed successfully, follow the steps in the Unifier Content Repository
Configuration Guide to complete the configuration of SharePoint with Unifier. You will be able to
access the documents uploaded in previous release.
24
Legal Notices
Oracle Primavera Unifier Upgrade Guide for On-Premises
Copyright © 1998, 2018, Oracle and/or its affiliates. All rights reserved.
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 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, 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
failsafe, 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.
This software or hardware and documentation may provide access to or information on 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. 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.
25