About Content Repository Authentication Modes

Transcription

1 P6 EPPM Content Repository Configuration Guide for On-Premises Version 18 February 2019

2

3 Contents About This Guide... 5 About Content Repository Authentication Modes... 5 Configuring the Content Repository for P Configuring Oracle Webcenter Content Core Capabilities to Work with P Configuring an Intradoc Server Port in WCCC... 7 Modifying the Server Configuration through Enterprise Manager... 8 Modifying the Server Configuration using the Configuration File... 8 Enabling Framework Folders in WCCC... 8 Creating a P6 Security Group in WCCC... 9 Creating a Local P6 Security Group in WCCC Creating an External P6 Security Group in WCCC Creating Document Types for P6 Documents in WCCC Creating a P6 Documents Home Folder on the WCCC Server Creating Metadata Text Fields in WCCC Configuring WCCC settings for the Primavera P6 Administrator Configuring CMIS-Compliant Content Repository for P Configuring CMIS-Compliant Content Repository in the Database Instance Settings Configuring AutoVue without VueLink Configuring Outside In Configuring the Oracle Database Content Repository Upgrading the Content Repository Migrating the Content Repository if Upgrading Upgrading from Previous Universal Content Management Version to WCCC Troubleshooting Legal Notices

4

5 About This Guide Scope Integrate a content repository with P6 to make it easier to catalog, access, search, and reuse documentation. This guide describes how to: Configure Oracle Webcenter Content Core Capabilities (WCCC), Oracle Database, Microsoft SharePoint or any CMIS-compliant content repository for integration with P6. Refer to Tested Configurations for a complete list of the content repositories P6 EPPM supports. Set your content repository settings in the Primavera P6 Administrator to connect your content repository to P6. Audience Notes: The SharePoint connector has been removed. New SharePoint users should configure SharePoint with a CMIS-compliant content repository, and then configure P6 EPPM to the CMIS-compliant content repository. Do not reconfigure SharePoint with a CMIS-compliant content repository if you previously configured your SharePoint connection using the Primavera P6 Administrator and SharePoint connector. Reconfiguring SharePoint with a CMIS repository will prevent previously stored documents from being visible. For more information, refer to documentation from Version 16. System administrators should use this guide. Using This Guide This guide assumes you have installed P6 and its supporting applications. For more information, see the P6 EPPM Installation and Configuration Guide. About Content Repository Authentication Modes P6 EPPM offers two content repository authentication modes. You can configure authentication for either single user authentication or multiple user authentication. In single user authentication mode, all P6 EPPM users access the repository using a single administrator user login that is set during repository configuration. In multiple user authentication mode, each P6 EPPM user is authenticated based on their individual login. 5

6 P6 EPPM Content Repository Configuration Guide for On-Premises Single User authentication mode is useful when you want users to have full access to the content repository through P6 EPPM without having to maintain an equivalent list of users for both P6 EPPM and the repository. This allows a repository administrator to maintain one set of credentials for the repository without having to share those credentials with all users. Single user authentication is also useful for quickly setting up test repositories that testers can access with ease. Multiple User authentication mode is the default mode. Multiple user authentication mode provides increased security by restricting content repository access on an individual user basis. Because it uses native auditing fields it also allows a clear audit of who has created and modified files. Note: When using multiple user authentication mode, you should disable for the Oracle content repository Guest Access. If you leave Guest Access enabled and the guest user is not part of the P6 EPPM security group, that user will not be able to access P6 repository functionality. If you are using the Oracle Database as your content repository, you can only use multiple user. See the P6 EPPM Application Administration Guide for more information about Single User and Multiple User settings. Configuring the Content Repository for P6 If you are installing P6 and the content repository for the first time, follow the steps in this section. If you are upgrading from a previous version of P6 and need to update your content repository to the latest supported version, you need to follow the steps in Upgrading the Content Repository (on page 16). Before you configure your content repository, you need to decide which authentication mode to use. Refer to the documentation included with the content repository application for detailed instructions on how to complete the guidelines in this section. Note: When P6 is configured with a content repository, it develops a dependency on that content repository. After you configure your content repository, if dependency is broken (for example, starting P6 when the content repository is not running), the content repository features will fail until the P6 Server is restarted. 6

7 Configuring the Content Repository for P6 Configuring Oracle Webcenter Content Core Capabilities to Work with P6 Depending on your organization, you can choose to use existing configurations or your own naming conventions when configuring Oracle Webcenter Content Core Capabilities (WCCC). Refer to the documentation included with WCCC for detailed instructions on how to complete the guidelines in this section. See the P6 EPPM Tested Configurations document for information on supported versions. These instructions contain information only on configuring Oracle Webcenter Content Core Capabilities to work with P6. They do not include information on installing WCCC. For WCCC installation instructions, see the documentation included with Oracle WCCC. For more information on configuring Oracle Webcenter Core Capablities, consult the following Knowledge Base article on integrating WCCC with P6: Configuring an Intradoc Server Port in WCCC The Intradoc Server Port is used by P6 to communicate with WCCC. When this is enabled, a security filter list which includes the IP address of the P6 application server is required to communicate to the Content Server through the Intradoc Server Port. The security filter list must be defined because it is a trusted connection. If you are accessing WebContent Center for the first time, you must configure the Incoming Socket Connection Address Security Filter and Server Socket Port. To configure the Incoming Socket Connection Address Security Filter and Server Socket Port: 1) Log in to WebCenter Content ( as an administrator. The default is weblogic. 2) Enter or edit the following configuration values: a. In Incoming Socket Connection Address Security Filter, enter the server IP address of the P6 application server. Note: Separate multiple IP addresses using a pipe symbol or. For example, b. In Server Socket Port, enter an unused port number for the Content Server. For example, ) Apply the changes. 4) Restart the WCCC managed server for changes to take effect. Note: If this is not the first time you have installed WCCC, you must confirm or modify the server configuration Incoming Socket Connection Address Security Filter and Server Socket Port values. You can modify the values through Enterprise Manager or with the configuration file (config.cfg) using the following procedures: Modifying the Server Configuration through Enterprise Manager (on page 8) Modifying the Server Configuration using the Configuration File 7

8 P6 EPPM Content Repository Configuration Guide for On-Premises (on page 8) Modifying the Server Configuration through Enterprise Manager To modify the server configuration through Enterprise Manager: 1) Connect to Enterprise Manager Fusion Middleware Control ( 2) Log in as a domain administrative user. For example, weblogic. 3) In the navigation tree, expand WebCenter, Content, Content Server. 4) Select the Content Server instance name (for example, Oracle Content Server (WCCC_server1)). 5) Use the WCCC menu to select Configuration Pages, Internet Configuration. 6) In the Server Configuration section, in the IP Address Filter field, enter a list of IP addresses that can be used to access the server. Note: Separate multiple IP addresses or machine name entries using a pipe symbol or. For example, ) In the Intradoc Server Port field, enter a server port number. 8) Apply the changes. 9) Restart the WCCC managed server for changes to take effect. Modifying the Server Configuration using the Configuration File To edit the files in the server: 1) Go to <WCCC_Home>\ucm\cs\config. WCCC_Home is the location where you installed WCCC. The WCCC_Home path is \Oracle\Middleware\user_projects\domains\$domain_name by default. 2) Edit the config.cfg file. 3) Find the SocketHostAddressSecurityFilter line and add the list of IP addresses that can be used to access the server to the end of the line. Note: Separate multiple IP addresses or machine name entries using a pipe symbol or. For example, ) Find the IntradocServerPort line and enter a server port number. For example, ) Save the changes. 6) Restart the WCCC managed server for changes to take effect. Enabling Framework Folders in WCCC The Framework folder interface is not enabled by default. See the WCCC documentation for more information. To enable the Framework Folders component: 8

9 Configuring the Content Repository for P6 1) Log in to WebCenter Content ( as an administrator. 2) On the Main Menu, choose Administration, Admin Server, Component Manager. 3) On the Component Manager page, select the FrameworkFolders option. 4) Click Update. 5) Restart the WCCC managed server for changes to take effect. Creating a P6 Security Group in WCCC To maintain your WCCC repository, create a P6 Security Group in WCCC and grant the appropriate rights to P6 EPPM users. Consider the following: P6 user names must match the WCCC user names, unless you are using Single User for the Authentication Mode. Note: Single User Authentication Mode will log all P6 users into WCCC using the administrator user or as specified in the Database/Instance/Content Repository setting in P6 Admin Settings. All P6 EPPM-related WCCC user names must have corresponding assignments to WCCC Roles and Users. For a quick setup, you can create one P6 EPPM-specific Role to map to users with full privileges (read, write, delete, admin). All P6 EPPM-related WCCC user names must have access to the P6 Security Group, either directly or through a role. When you are creating users in WCCC for integrating with P6, consider the following: If you are using Multiple User Authentication Mode when configuring P6: You must create a WCCC user for every P6 EPPM user, and the user name created must match the P6 EPPM user. You must assign the user to a role mapped to the security group associated with the P6 Framework folder and must have the right to read, write, and delete. You must create an administrative user in WCCC. The user name does not have to match a P6 user. You must assign the administrative user to a role mapped to the Security Group associated with the P6 folder. The administrator must have read, write, delete, and admin rights within the Security Group. If you are using Single User Authentication Mode when configuring P6: You must create an administrative user in WCCC. The user name does not have to match that of a P6 EPPM user. You must assign the administrative user to a role mapped to the Security Group associated with the P6 folder. The administrator must have read, write, delete, and admin rights within the Security Group. (Optional) If you enabled Security Accounts, create a P6 Security Account. Depending on your organization, you might need to set up a Security Account for performance and storage reasons. Security considerations include the following: 9

10 P6 EPPM Content Repository Configuration Guide for On-Premises P6 EPPM user names must match the WCCC user names, unless using Single User for the Authentication Mode. All P6-related WCCC user names must have corresponding WCCC Roles and Users. All P6-related WCCC user names must have access to the P6 Security Account. Creating a Local P6 Security Group in WCCC To create a local P6 Security Group and administrative user: 1) Log in to WebCenter Content ( as an administrator. 2) Expand Administration, and select Admin Applets. 3) Select User Admin. 4) In the User Admin dialog box, select Security, Permission by Group. 5) Click Add Group. 6) Enter a Group Name and description. 7) Click OK. 8) Close the Permission by Group dialog box. 9) Select Security, Permission by Role. 10) Click Add New Role. 11) Enter a Role Name and Display Name. 12) Click OK. 13) Select newly created role and click Edit applet Rights. 14) Grant all rights to the administrative user. 15) Click OK. 16) In the Groups/Rights section, select the newly created group. 17) Click Edit Permissions. 18) Grant all permissions to the group. 19) Click OK. 20) Close the Permission by Role dialog box. 21) In the User Admin dialog, click Add. 22) Set Authorization type to Local. 23) Click OK. 24) Provide user details. 25) Navigate to the Roles tab. 26) Click Add Role. 27) Add the newly created role. 28) Click OK. 29) Close the User Admin dialog box. 10

11 Configuring the Content Repository for P6 Creating an External P6 Security Group in WCCC You may want to create external security accounts for WCCC. For instructions on creating external security groups, see the document "How To Configure Local Or External Users, Roles And Security Accounts In Webcenter Content Core Capabilities (WCCC), Universal/Enterprise Content Server When Integrating With P6 EPPM" (Doc ID on My Oracle Support at Creating Document Types for P6 Documents in WCCC (Optional) You can create document types for P6 documents in WCCC. 1) Log in to WebCenter Content ( as an administrator. 2) Expand Administration and select Admin Applets. 3) Select Configuration Manager. 4) In the Configuration Manager, select Options, Content Types. 5) Create a new content type for P6 Documents. 6) Apply the changes. 7) Restart the WCCC managed server for changes to take effect. Note: Document Type as Document is the default document type in a WCCC repository. Creating a P6 Documents Home Folder on the WCCC Server Create a P6 documents home folder on the WCCC server by adding a unique path to the root folder. 1) Log in to WebCenter Content ( as an administrator. 2) Expand Browse Content. 3) Select Folders. 4) Select Add. 5) Enter a folder name. For example, P6EPPM 6) Select Show Advanced Options. 7) Select the security group created for P6. 8) Apply the changes. Creating Metadata Text Fields in WCCC From the Configuration Manager applet, create the following metadata text fields in WCCC for P6: 1) Log in to WebCenter Content ( as an administrator. 2) Expand Administration and select Admin Applets. 3) Select Configuration Manager. 11

12 P6 EPPM Content Repository Configuration Guide for On-Premises 4) In the Configuration Manager, select the Information Fields tab. 5) Create the following information fields as specified (including case): PrmUserId PrmProjectId PrmWorkgroupId PrmWorkflowId PrmWorkflowStatus PrmWorkflowAction PrmSecurityPolicy PrmTemplate PrmCheckedOutUserId PrmCheckedOutDate PrmLocalFilePath (set Type to Long Text) PrmAuthorId Note: Using "Prm" as a prefix is optional. You can use any prefix. If you do not use a prefix, ensure that none of the P6 metadata fields conflict with existing metadata fields. 6) Select Update Database Design to commit the changes. 7) Restart the WCCC managed server for changes to take effect. Configuring WCCC settings for the Primavera P6 Administrator To configure WCCC settings for the Primavera P6 Administrator: 1) Open the Primavera P6 Administrator. 2) In the Configurations tab, expand your configuration. 3) Expand Database, Instance[n], Content Repository. 4) In the Type field, choose Oracle. 5) Expand Database, Instance[n], Content Repository, Oracle WebCenter Content Core Capabilities. 6) In the Host field, enter the machine name or IP address of the content repository server. 7) In the Port field, enter the Intradoc Server Port number of the content repository server. The default port number is ) In the Oracle Home field, enter the location of the folders you created. The default for Framework Folders is /P6EPPM. 9) In the Oracle Security Group field, enter the name of the Security Group for P6 documents that you specified when you configured the content repository. 10) In the Oracle Security Account field, enter the name of the Security Account for P6 documents that you specified when you configured the content repository. If you did not enable security accounts, leave this field blank. 12

13 Configuring the Content Repository for P6 11) In the Oracle Document Type field, enter the document type for P6 documents, which can be either an existing document type or a new one that you specified when you configured the content repository. If you enabled Document Types, you must configure this setting. For example, document. 12) In the Metadata Prefix field, enter the prefix added to P6 metadata fields, as specified when you configured the content repository. For example, Prm. 13) In the Admin User field, enter the user name with administrative privileges that you specified when you configured the content repository. 14) In the Authentication Mode field, enter the authentication mode that you use access the content repository server. For example, Single User or Multiple User. P6 EPPM users cannot access content repository functions if you do not configure this setting. Note: If you choose Multiple User, all P6 EPPM content repository-related user names must match the equivalent content repository user name. For example, a P6 EPPM user named "Joe" must have an equivalent user named "Joe" in the content repository. 15) Restart the P6 server. Configuring CMIS-Compliant Content Repository for P6 Content Management Interoperability Services (CMIS) is a standard that content repositories have agreed to adhere to so that a single document connector can be used to connect to any CMIS-compliant repository. You can connect any CMIS-compliant content repository, including SharePoint, to P6. The repository must be 100% CMIS-compliant to utilize all the features of P6 document functionality. Configuring CMIS-Compliant Content Repository in the Database Instance Settings You can use Microsoft SharePoint with P6 by integrating SharePoint with your CMIS-compliant content repository and then configuring your CMIS-compliant content repository with P6. To configure your CMIS-compliant content repository: 1) Open the Primavera P6 Administrator. 2) In the Configurations drop-down list, select your configuration. 3) In the sidebar select Database. 4) Select your Instance from the drop-down list. 5) Expand Content Repository. 6) In the Type field, select CMIS. Note: Changes to these settings require you to restart the P6 server. 7) In the Maximum document size field, enter the maximum size in KB for documents that can be uploaded to P6. The default is KB. Enter a value between 0 and ) In the Invalid Document Types field, enter the file extensions of documents that are not permitted in P6. A list of file extensions can be separated with either commas or spaces. 13

14 P6 EPPM Content Repository Configuration Guide for On-Premises For example: exe,bin,sh.exe.bin.sh 9) In the Login Name field, enter the user name for your content repository. 10) In the Password field, enter the password for the user name you entered above. 11) In the Authentication Mode field, enter authentication mode used to access the content repository server. P6 EPPM users cannot access content repository functions if you do not configure this setting. If you choose "Multiple User", all P6 EPPM content repository-related user names must match the equivalent content repository user name. For example, a P6 EPPM user named "Joe" must have an equivalent user named "Joe" in the content repository. If you choose "Single User", the administrative user specified in the setting above must have access to all appropriate Security Groups to browse to documents outside of the P6 EPPM home folder. 12) In the Repository Name field, enter the name for your content repository. Note: For SharePoint, enter the document library name you created for P6. 13) In the Document Home field, enter the location of the folder in the document library where you want to store P6 documents. 14) In the Web Service URL field, enter the URL for your web services home. 15) This is Web Service Endpoint with format host>/sites/<site name>/_vti_bin/cmissoapwsdl.aspx 16) Restart the P6 server. Configuring AutoVue without VueLink Configuring AutoVue without VueLink is the native AutoVue implementation. To use this implementation, you will configure a single AutoVue server that is common across all database instances. Notes: When you configure AutoVue without VueLink, you are creating global AutoVue settings. These settings override any individual settings you may have created to configure AutoVue with VueLink. When upgrading to Version 18 from 15 R2 or earlier, AutoVue connection details are lost and must be entered again. To configure AutoVue without VueLink, complete the following steps: 1) Open the Primavera P6 Administrator. 2) In the Configurations drop-down list, select your configuration. 3) In the sidebar select Document Viewing. 14

15 Configuring the Content Repository for P6 Note: Changes to these settings require you to restart the P6 server. 4) Select Enable. The default value is unselected. Notes: SSL mode does not work when the Enable option is set to false. By default, the ESAPI resources that come with VueLink is used. You can change the location of the resource files by using -Dorg.owasp.espai.resources JAVA_OPTIONS in the WebLogic application server or in the setdomainenv script. By default, dmsstamp.ini and the oracle sample stamp from VueLink is used to create markup. You can change the location of the dmsstamp.ini file, which contains the stampfile location, using -Dexternal.csi.intellistamp.def.location JAVA_OPTIONS in the WebLogic application server or in the setdomainenv script. If using Oracle Access Manager with your P6 EPPM deployment, add following context roots to the Oracle Access Manager exclusion list: /p6/vueservlet/** /p6/jvuedms/** /p6/p6autovuejnlplauncher/** /p6/av_cert.pem For more information about protecting your resources using Oracle Access Manager's exclusion list, see the "Protecting Your Resources" chapter in the Oracle Access Manager Configuration Guide. 5) In the Host Name field, enter the hostname for the server where AutoVue is installed. Note: Do not put a / at the end of the URL. 6) In the Host Port field, enter the port for the server where AutoVue is installed. The default port is ) Restart the P6 server. Configuring Outside In Outside In converts documents uploaded to your content repository into a raster-image file. To configure Outside In: 1) In the Primavera P6 Administrator, do the following: a. Select your configuration. b. In the sidebar, select Document Viewing. c. In the Fonts Directory field, enter the full path to your operating system-specific fonts folder. For example, C:\Windows\Fonts. 15

16 P6 EPPM Content Repository Configuration Guide for On-Premises Note: You cannot convert documents in languages that do not have a compatible font installed in the Fonts Directory. Before you convert these documents you must install the appropriate language font. d. In the Images Directory field, enter the full path to your Outside In images folder. For example, P6EPPM_HOME\P6\outsidein\ImageExport\Images. 2) Navigate to P6EPPM_HOME\P6. 3) Run outsideinconfig.cmd or outsideinconfig.sh (based on your operating system). Configuring the Oracle Database Content Repository You can use Oracle database as a content repository with your P6 EPPM installation. To configure the Oracle database as your content repository: 1) Open the Primavera P6 Administrator. 2) In the Configurations drop-down list, select your configuration. 3) In the sidebar select Database/Instance[n]/Content Repository. Note: Changes to these settings require you to restart the P6 server. 4) In the Type field, select Oracle Database. This option will save documents and associated information in the P6 database schema. This option is only applicable if you are using an Oracle database on-premises. 5) In the Maximum document size field, enter the maximum size in KB for documents that can be uploaded to P6. The default is KB. Enter a value between 0 and ) In the Invalid Document Types field, enter the file extensions of documents that are not permitted in P6. A list of file extensions can be separated with either commas or spaces. For example: exe,bin,sh.exe.bin.sh 7) In the Connection Maintenance Interval field enter the frequency at which the connection to the content repository is validated. The default is 10 minutes. Enter a value between 1 second and 24 days. Note: Ensure that the Enable Cloud Storage field is set to false. 8) Restart the P6 server. Upgrading the Content Repository If you upgraded to P6 or the content repository, you need to do one of the following: If you upgraded from a previous P6 version, see Migrating the Content Repository if Upgrading (on page 17). 16

17 Upgrading the Content Repository If you upgraded UCM to or higher, see Upgrading from Previous Universal Content Management Version to WCCC (on page 17). Migrating the Content Repository if Upgrading Run the migration utility before connecting the upgraded environment back to the Content Repository. Running the migration utility will ensure all project folder names in the Content Repository change from Database IDs to their Project ID field (from P6). If you upgraded P6 from a previous version, you must: 1) Go to the P6EPPM_Home/p6 folder. 2) Run migrationtool.cmd or migrationtool.sh (based on your operating system). Upgrading from Previous Universal Content Management Version to WCCC If you were using a previous version of Universal Content Management (UCM), you will notice many changes when you upgrade to a supported version of WCCC. To maintain your documents from P6, you should ensure that your framework folder has updated correctly. To do this, you should: 1) Shutdown all the P6 applications connecting to your current content repository. 2) Run the migration utility. a. Go to the P6EPPM_Home/p6 folder. b. Run migrationtool.cmd or migrationtool.sh (based on your operating system). Note: Users is a restricted folder name for folders within the folder structure in supported versions of WCCC. 3) Note the folder database converts project IDs to project short names. 4) Upgrade a previous version of UCM or WCCC to a supported version of WCCC or higher using the upgrade guide provided with the WCCC media packs. a. Enable the framework folders components. 5) After the migration: a. Locate the migration_run**** folder that was created. b. Move all the folders and documents under this folder to the Content repository home folder that you want to use. c. Ensure you select inhibit propagation to ensure proper movement of documents and folders. 6) After the move completes, you can start using the documents with the correct content repository home. Tips Have 4-6 GB open memory space. Don't propagate changes when given the option. 17

18

19 Troubleshooting If you started using the document functionality of the P6 application without running migration utility provided with P6 on an upgraded environment, where you were using a content repository for managing documents, you will be unable to use the documents that were earlier associated with any Projects or Users. 19

20 Legal Notices Oracle Primavera P6 EPPM Content Repository Configuration Guide for On-Premises Copyright 1999, 2019, 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. 20