What's New in Oracle WebCenter Content on Marketplace
Learn about the new and changed features in Oracle WebCenter Content on Marketplace. For known issues, see Known Issues.
24.8.1 — August 2024
Feature | Description |
---|---|
New Redwood User Interface | The Redwood UI and Viewer introduce a modern interface for WebCenter Content, created with the Oracle Redwood design system. This general-purpose interface is available as an optional standalone client application, enabling users to upload, search, browse, manage, and view documents within the repository. See Using the Redwood User Interface of Oracle WebCenter Content for more information. |
New option to enable authentication using IDCS | You can now enable authentication using IDCS as the security provider when configuring the stack. There is a new field to specify the IDCS user name. See Provision WebCenter Content Stack. |
Quick Start option | A new option called Quick Start is available to quickly provision a WebCenter Content environment using default values. See Provision WebCenter Content Stack and Quick Start for WebCenter Content for more information. |
Patching-related updates | The steps to apply a patch have changes. See Apply Patch. |
Updates related to integration with OCI Process Automation | OCI Process Automation process invocation can happen via direct checkin with profile or via WebCenter Content workflow. There are updates to prerequisites for the integration. When registering a new process, if the profile is not specified, the process can be invoked only via WebCenter Content Workflow. For more information, see Integrating Oracle WebCenter Content with OCI Process Automation. |
Public links | WebCenter Content on Marketplace supports public links that allow guest users (anonymous users) to access certain folders and files in WebCenter Content without a WebCenter Content account or login credentials. In this release, we only support read-only public links. See Public Links in Oracle WebCenter Content. |
REST API | Anonymous calls are now supported. There are 7 new end points for the new public links feature. Resources such as Checkout a Document, Query a DataSource, Delete a File, and Delete a Folder are new. See REST API for Oracle WebCenter Content. |
Support to configure OpenSearch | You can now configure OpenSearch v2.x for Oracle WebCenter Content (on marketplace). Note that you need to use Basic Auth as the authorization method if you are using OpenSearch 2.11. See About OpenSearch 2.x for information specific to 2.x and Basic Auth. See Managing OpenSearch. |
Set Up DNS and SSL Certificate | You can set up DNS and SSL Certificate for WebCenter Content. See Set Up DNS and SSL Certificate for WebCenter. |
24.7.1 — July 2024
Feature | Description |
---|---|
Integration with OCI Monitoring and Console Dashboard | You can integrate Oracle WebCenter on Marketplace with OCI Monitoring and OCI Console Dashboard. See Integrate WebCenter with OCI Monitoring and Console Dashboard. |
Patch Tool | Oracle WebCenter on Marketplace in OCI provides a patching utility tool to download and apply patches for WebCenter instances. See About the Patch Tool. |
Backup and Restore scripts for WebCenter | Oracle WebCenter on Marketplace in OCI provides scripts to perform backup and restore operations for WebCenter instances. See Backup and Restore scripts for WebCenter. |
New options in Stack Configuration | When configuring the stack, you now have options such as OCI Policies, Enable Private Service, Enable Key Management with OCI Vault, and option to specify custom database schema prefix. For more information, see Provision WebCenter Content Stack. |
Options to use existing subnet when provisioning stack | You have options to use an existing subnet when provisioning the stack. See Provision WebCenter Content Stack. |
Configuring the vault is now optional | You can now specify the secret phrase directly instead of referring from vault. |
Updates related to integration with OCI Logging | See the latest version of the documentation: Integrating WebCenter Logs with OCI Logging. |
Option to use existing file system when provisioning stack | You can optionally now use an existing file system when provisioning the stack. See Provision WebCenter Content Stack. |
REST API | There are new resources such as Update Document, Update Document by dID, and Create Folder. See REST API for Oracle WebCenter Content. |
Updates related to integration with OCI Process Automation | The name of the Weblogic server’s credential map has changed. See Integrating Oracle WebCenter Content with OCI Process Automation. |
REST API for WebCenter Content: Imaging | REST APIs are now available for WebCenter Content: Imaging on marketplace. See Doc ID 3030786.1 in My Oracle Support. |
Updates related to FA integration | The value of the URL definition when creating a mashup has been updated. See Create a Mashup. You can specify a custom title for the Managed Attachments UI. See Create a Global Function to Call WebCenter Content Grant. |
24.6.1 — June 2024
Feature | Description |
---|---|
Object Storage for documents is optional | You can choose to store documents in the file system or in Object Storage. See Provision WebCenter Content Stack. Customers can now leverage Object Storage’s Infrequent Access storage class tier to address the need for a storage tier that is ideal for data that is accessed infrequently (and optimize cost), but that must also be available immediately when needed. For more details, refer to OCI Object Storage documentation. |
PDB name | You can now specify the PDB name when configuring the database. See Provision WebCenter Content Stack. |
Integration with OCI Logging | You can integrate WebCenter Logs with OCI Logging. See Integrating WebCenter Logs with OCI Logging. |
REST API | There are new WebCenter Content REST APIs that allow you to interact with content in WebCenter Content. See REST API for Oracle WebCenter Content. |
Integration with OCI Process Automation | You can integrate WebCenter Content with OCI Process Automation. See Integrating Oracle WebCenter Content with OCI Process Automation. |
Large dID | WebCenter Content on Marketplace now supports very large dID. dIDs of large size can now successfully flow through the system. A dID is an internally generated integer that refers to a specific revision of a content item. To understand what dIDs are, see Developing with Oracle WebCenter Content. |
Migration from Oracle Content Management to Oracle WebCenter Content | Oracle provides migration utilities and documentation to migrate from Oracle Content Management to Oracle WebCenter Content. For information about the tools, please raise a support ticket in My Oracle Support. |
24.5.1 — May 2024
Feature | Description |
---|---|
Object Storage for documents | Object Storage (a storage provider component) is now available to store documents. See Provision WebCenter Content Stack. |
Configure FA adapter integration with WebCenter Content | You can install and configure FA integration with WebCenter Content on marketplace. See Configure FA Adapter Integration with WebCenter Content. |
Configure SAML2 IDCS Single Sign-On in WebCenter Content | You can configure SAML2 IDCS Single Sign-On in WebCenter Content on marketplace. See Configure SAML2 IDCS Single Sign-On in WebCenter Content. |
WebCenter Content Reports | WebCenter Content Reports feature is now available in WebCenter Content on Marketplace. See Doc ID 3023292.1 in My Oracle Support |
Smart Tagging | You can now enable smart tagging feature in WebCenter Content on Marketplace. See Doc ID 3023045.1 in My Oracle Support. |
Embeddable Document Viewer | This feature offers a first look at the WebCenter Content user interface using the Redwood design. This new viewer interface is offered as an option to view documents from within the existing native WebCenter Content UI and to reference documents directly using a service URL. See Doc ID 3024420.1 in My Oracle Support. |
REST API | The WebCenter Content REST APIs allow you to interact with content in WebCenter Content. See Doc ID 3021636.1 in My Oracle Support. |
Get Started with Oracle WebCenter Content on Marketplace
Here’s information about Oracle WebCenter Content on Marketplace that will help you get started:
About Oracle WebCenter Content on Marketplace
Oracle WebCenter Content on Marketplace is provided as a VM-based solution on Oracle Cloud Infrastructure.
Oracle WebCenter Content on Marketplace is available in two types of Marketplace offerings: Paid and BYOL. See About the License for Oracle WebCenter Content on Marketplace.
Oracle WebCenter Content on Marketplace helps customers to provision/set up the environment in few clicks and enables to deliver Content solutions on cloud.
About the License for Oracle WebCenter Content on Marketplace
Oracle WebCenter Content on Marketplace is based on Oracle WebCenter Content 12c (12.2.1.4). Oracle WebCenter Content on Marketplace is available in two types of Marketplace offerings:
Paid: Use one of the following Oracle WebCenter Content (Paid) listings to use Universal Credits pricing:
Oracle WebCenter Content 12c (Paid)
Oracle WebCenter Universal Content Management 12c (Paid)
Oracle WebCenter Imaging 12c (Paid)
Oracle WebCenter Enterprise Capture 12c (Paid)
Oracle WebCenter Enterprise Capture Standard Edition 12c (Paid)
BYOL: Use the Oracle WebCenter Content (BYOL) listing to Bring Your Own License using your existing Oracle WebCenter Content 12c (12.2.1.4) on-premises license, or you can purchase a new license for Oracle WebCenter Content 12c (12.2.1.4).
When you activate Oracle WebCenter Content on Marketplace using the BYOL listing, you are charged only for the Oracle Cloud Infrastructure resources consumed. You must have sufficient supported on-premises licenses as required and specified in the Service Description for Oracle PaaS.
For the processor conversion ratios and license requirements for the BYOL offering, go to the Cloud Service Descriptions page and go to the Cloud Service Description PDF. In particular, note the following conversion ratios for BYOL:
For each supported Processor license, you may activate up to 2 OCPUs of the BYOL Cloud Service.
For every 10 supported Named User Plus licenses, you may activate 1 OCPU of the BYOL Cloud Service.
About Roles and User Accounts
Oracle WebCenter Content on Marketplace uses roles to control access to tasks and resources. A role assigned to a user gives certain privileges to the user.
Access to Oracle WebCenter Content on Marketplace is based on the roles and users set up for the Oracle Cloud Infrastructure console. You need OCI Administrator role to provision WebCenter Content.
For information about how to add user accounts in Oracle Cloud, see:
Add Users to a Cloud Account with Identity Cloud Service in Getting Started with Oracle Cloud.
Managing Oracle Identity Cloud Service Users and Groups in the Oracle Cloud Infrastructure Console in the Oracle Cloud Infrastructure documentation.
Create and View Oracle WebCenter Content on Marketplace Instances
The information in this chapter will help you create and view Oracle WebCenter Content on Marketplace instances.
Before You Begin
Before you begin, you would need to complete the following tasks and prerequisites.
Sign in to Oracle Cloud Infrastructure Console
Complete the following steps to sign in to the Oracle Cloud Infrastructure console.
Go to http://cloud.oracle.com.
Enter your cloud account name and click Next.
Sign in to the Oracle Cloud Infrastructure console:
If your cloud account uses identity domains, sign in to the Oracle Cloud Infrastructure console as a user configured in Oracle Cloud Infrastructure Identity and Access Management (IAM).
Select the domain you normally use to log in to the OCI console.
If your cloud account does not use identity domains, sign in to the Oracle Cloud Infrastructure console as a user federated through Oracle Identity Cloud Service.
Under Single Sign-On (SSO) options, note the identity provider selected in the Identity Provider field and click Continue.
Enter the user name and password provided in the welcome email, and click Sign In. The Oracle Cloud Infrastructure console is shown.
Prerequisites
You'll need to complete the following prerequisites before provisioning the WebCenter Content stack.
After completing the above prerequisites, you can proceed to provision the WebCenter Content stack.
System Requirements
You require access to the following services to use Oracle WebCenter Content on OCI.
Identity and Access Management (IAM)
Compute, Network, Block Storage, Block Volume
Vault, Key, Secret
Resource Manager
Database
Load Balancer
Tagging
Make sure you have the following minimum limits for the services in your Oracle Cloud Infrastructure tenancy, and if necessary, request for an increase of a service limit.
Service | Minimum Limit |
---|---|
Identity and Access Management (IAM) Policy | 1 |
Compute Shape VM.Standard.E4.Flex or VM.Standard.E5.Flex | 1 |
Virtual Cloud Network | 1 |
Block Storage | 1 TB |
Block Volume | 50 GB |
Vault & Key | 1 |
Secrets | 1 |
Load Balancer | Flexible Load Balancer |
In Oracle Cloud Infrastructure Vault (formerly known as Key Management), a standard vault is hosted on a hardware security module (HSM) partition with multiple tenants, and it uses a more cost-efficient, key-based metric for billing purposes. A virtual private vault provides greater isolation and performance by allocating a dedicated partition on HSM. Each type of vault has a separate service limit in your Oracle Cloud Infrastructure tenancy. The limit for secrets spans all the vaults.
See Service Limits in the Oracle Cloud Infrastructure documentation.
Generate SSH key pair
See generate_ssh_key for generating an SSH key pair.
This SSH key pair will be used for connecting to Bastion and Compute instances after stack execution.
Note: This will be used to create DB and WebCenter Content nodes.
Create a Compartment
If your tenancy does not already include a compartment for your Oracle WebCenter Content on Marketplace instances, you can create a new one.
Note: To create a compartment, your administrator must first add the following policy for your group: allow group groupName to manage compartments in tenancy
To create a compartment in Oracle Cloud Infrastructure:
Open the navigation menu and click Identity & Security. Under Identity, click Compartments. A list of the existing compartments in your tenancy is displayed.
Click Create Compartment.
Enter the following:
Name: Specify a name. For example, wcc-compartment. Restrictions for compartment names are: Maximum 100 characters, including letters, numbers, periods, hyphens, and underscores. The name must be unique across all the compartments in your tenancy.
Description: A friendly description.
Parent Compartment: Select the parent compartment where you want the new compartment to be created. When the parent compartment is not selected, the new compartment is created under the root compartment.
Click Create Compartment.
Once the compartment is created, if you are not an administrator, ask your administrator to complete the following steps to grant you the permissions needed to perform the required tasks in the compartment:
Note: You can use any name (wcc-admins and wcc-compartment are examples).
Create an IAM group with the user that will do the Marketplace install.
Navigate to Identity and Security, and then Domains.
If not already selected, select the compartment where you’ll install the Marketplace product.
Click the domain where you’ll create the group.
Click Groups.
On the Create group page, provide the following information:
- Name: wcc-admins
- Description: Webcenter Content Administrators
- Users: Add the user that will do the Marketplace installation.
Click Create.
Create an IAM group with the user that will do the Marketplace install.
Navigate to Identity and Security, and then Policies.
Click Create Policy.
Create a policy with the following statements.
allow group wcc-admins to manage instance-family in compartment wcc-compartment
allow group wcc-admins to manage virtual-network-family in compartment wcc-compartment
allow group wcc-admins to manage volume-family in compartment wcc-compartment
allow group wcc-admins to manage load-balancers in compartment wcc-compartment
allow group wcc-admins to manage orm-family in compartment wcc-compartment
where
wcc-admins
is the group name andwcc-compartment
is the compartment name.
Create a Master Key
You'll need to create a master key for the vault.
Open the navigation menu and click Identity & Security and then Vault.
Change the necessary compartment.
Click the already created vault name.
On the left side, click Master Encryption keys and then click Create Key.
Complete the following:
Create In Compartment : Name of the selected compartment
Protection Mode: Software
Name: Specify a name.
For remaining fields, retain the default values.
Click Create Key.
Wait for the status to show green.
Create Database
You’d need a new DB system only if you want to provision a new database.
Note: Otherwise, you can use an existing database too.
Note: Currently, only the Oracle Base Database Service is supported. Support for other versions will be provided in upcoming releases. For any additional questions, contact the Oracle Support team.
Complete the following to create a new DB system:
Create VCN
Log in to OCI Console, navigate to Networking, then to Virtual Cloud Networks.
Click Create VCN via Wizard.
Click Start VCN Wizard.
VCN name: Provide a name.
Compartment: Specify the compartment in which the VCN needs to be created.
VCN IPv4 CIDR block: Specify IPv4 CIDR block (for example, 10.0.0.0/16).
Select the Use DNS hostnames in this VCN check box.
In the Configure public subnet and Configure private subnet sections, specify the correct CIDR blocks and click Next.
Make sure to create the necessary gateways such as Internet gateway, NAT gateway, and Service gateway.
Click Create. The VCN is created.
Create a New DB System
Create a new DB system in the VCN you created earlier.
Make a note of the SSH keys used for the DB system creation. This private SSH key will be added to the vault's secret later.
Note: Ensure to provide a DB System SSH private key without a passphrase as passphrase is not allowed.
Log in to the console.
Click Oracle Database.
Click Oracle Base Database Service and then click Create DB Systems.
Provide the following parameters:
Select a Compartment Name: Choose the appropriate compartment name.
Name your DB system: Specify a suitable name.
Select an availability domain: Choose AD1. You can choose any AD but make sure that WebCenter Content and DB are in the same AD.
Configure shape: AMD VM Standard E4 Flex
Configure storage: 1 TB
Configure the DB system: The total node count is 2 and Oracle Database software edition is Enterprise Edition Extreme Performance.
Add SSH keys: Upload the public SSH key you created in the first step. You can either reuse the keys generated in the first step or you can generate a new pair of keys too for database instances.
License: Choose the appropriate license.
Virtual cloud network: Choose the VCN you created earlier.
Client subnet: Select (either private or public subnet as needed) from the drop- down list.
Hostname prefix: Choose an appropriate name.
Database name: Specify a name for your database. Click Next.
Database image: Oracle Database 19c.
PDB Name: pdb1
Create administrator credentials: Specify ‘sys’ and an appropriate password.
Backup destination: Object Storage
For remaining input fields: Select the default values.
Click Create DB System and wait for the DB provisioning to be completed before you proceed to the next step.
Create IDCS Application
An IDCS confidential application is needed to configure the IDCS security provider in Weblogic domain during provisioning. Follow the below instructions based on whether OCI Tenancy IAM is with Identity Domains or not.
For OCI accounts where IAM is with Identity Domains (tenancy with IAM domains), complete the following:
Log in to OCI console.
Navigate to Identity and then Domains.
Select the domain which needs to be used for SSO log-in.
Go to Integrated Applications and click Add application.
Choose Confidential Application and launch the workflow.
On the Add Application Details page, fill the Name and Description fields, and then click Next.
On the Configure OAuth page, select the Configure this application as a client now option under Client configuration section.
In the Authorization section, select the Client credentials check box for the Allowed Grant Types field.
Scroll down and select the Add app roles check box. In the App roles section, add the Identity Domain Administrator role.
Click Next. Leave the default settings for the next page as is and click Finish.
Make a note of the client ID and client secret. These values will be needed when you run the script.
Activate the application.
For OCI accounts where IDCS is not yet migrated to IAM Domains (tenancy without IAM domains), complete the following:
Log in to the IDCS administration console of the federated IDCS.
For example,
https://idcs-abcde.identity.oraclecloud.com/ui/v1/adminconsole
.Navigate to Applications. Click + to add an application. Choose Confidential Application in the wizard:
Add a name and a description on the App details page.
Click Next. Select the Configure this application as a client now option.
In the Authorization section, select the Client credentials check box for the Allowed Grant Types field.
In the Grant the client access to Identity Cloud Service Admin APIs section, click Add to add the application roles. You need to add the Identity Domain Administrator role.
Click Next. Leave the default settings for the next pages as is and click Finish.
Make a note of the client ID and client secret. These values will be needed when you run the script.
Activate the application.
Create the Object Storage Bucket in OCI
Click the navigation menu in the upper left corner of the page and click Storage.
Click Buckets.
Confirm that you're in the correct compartment and the correct region.
Click Create Bucket on the "Buckets in <compartment name> Compartment" page.
Provide a value for Bucket Name.
Leave the Default Storage Tier set to Standard.
Leave the Encryption set to Encrypt using Oracle managed keys.
Click Create.
See Object Storage Buckets for more information.
Create a New User API Key
Click on your avatar in the upper-right corner of the page.
Click My profile.
In the Resources menu on the left side of the page, click API Keys.
Click Add API Key.
Download the private key by clicking Download private key. The private key will be added to the vault's secret later.
Click Add.
Click Copy to copy the content of the configuration file which has user OCID and fingerprint as this will be required later. Close the dialog.
Create Vault Secrets
Log in to the OCI console and search for Vault, and then create a vault app.
Click Create Vault.
Provide a name and click Create Vault.
Click the vault app you created earlier. Create a master encryption key by specifying the compartment, protection mode, name, algorithm, length, and so on in the Create Key section.
Click Secrets on the left side and start adding secrets by specifying the compartment, name, key, secret type template, secret contents, and so on in the Create Secret section.
Secret Name | Secret Description | Comment |
---|---|---|
wcc-admin-password | Secret for WebCenter Content Admin Password | The Secret Contents field should be populated with the Weblogic password value. The password needs to meet the following password policy: The password must be at least 8 alphanumeric characters with at least one number or a special character. |
db-system-sys-password | Secret for DB System SYS Password | SYS user password of DB created in the Create a New DB System section should be used in the Secret Contents field. |
db-system-ssh-private-key | Secret for DB System SSH private key | The Secret Contents field should be populated with the private key value that was used to create DB in the Create a New DB System section section. |
idcs-client-secret | Secret for IDCS Client secret | The Secret Contents field should be populated with the Client Secret value that was noted when the IDCS Confidential App was created in the IDCS section. |
wcc-schema-password | Secret for WCC schema password. | The password needs to meet the following password policy: •The password must start with a letter. •The password must contain at least two digits. •The password must contain at least two uppercase letters. •The password must contain at least two lowercase letters. •The password must contain at least two special characters from the set [$#_]. •The password must be at least 15 characters long. Example: OCI#db#456789123 |
oci-user-private-key | Secret for user API private key | The Secret Contents field should be populated with the private key value downloaded earlier in the Create a New User API Key section. |
Provision WebCenter Content Stack
You can provision Oracle WebCenter Content on a Marketplace instance in a selected compartment in Oracle Cloud Infrastructure.
To provision Oracle WebCenter Content on a Marketplace instance:
Navigate to the WebCenter Content listing on Marketplace by direct URL or by browsing in Oracle Cloud Infrastructure.
Using direct URL:
In your browser, enter https://cloudmarketplace.oracle.com/marketplace/en_US/homePage.jspx?tag=WebCenter+Content.
The Marketplace listings for WebCenter Content are displayed.
Click the title of the listing you want to use. The landing page of that listing is displayed.
Click Get App.
Select your Oracle Cloud Infrastructure region and click Sign In.
By browsing:
Open the navigation menu and click Marketplace. Under Marketplace, click All Applications.
In the Marketplace search field, enter WebCenter Content.
The Marketplace listings for WebCenter Content are displayed.
Click the title of the listing you want to use and review the information on the Overview page.
Accept the terms and restrictions, and then click Launch Stack. The Create Stack wizard is displayed.
Provide information about the stack for the instance.
Stack information:
Enter name and description.
Create in Compartment: Select the compartment.
Terraform version: Specify the Terraform version and click Next.
Configure variables:
Stack Configuration
Resource Name Prefix: Enter a prefix (for example, WCC). The name of all compute and network resources will begin with this prefix. It must begin with a letter and it can contain only letters or numbers.
SSH Public key: Provide the SSH public key (created in Generate SSH key pair).
Quick Start: Select this check box to quickly provision a WebCenter Content environment using default values. See Quick Start for WebCenter Content for more information.
OCI Policies: Select this check box if you need the stack to create policies to provision WebCenter Content resources, configure Database Network, and read Vault Secrets. Deselecting this option is for Advanced users only.
Enable Authentication Using Identity Cloud Service: Select this check box if you need to use Identity Cloud Service (IDCS) as the security provider in WebCenter Content. If not selected, the local Weblogic identity store will be used.
Enable Object Storage as default storage: Select this check box if you need object storage as the default storage instead of file system for storing documents. If selected, you need to complete the fields in the Object Storage section.
Enable Private Service: Select this check box if you need to provision service in private subnet for Fast Connect usage.
Enable Key Management with OCI Vault: Select this check box if you need to enable Key Management with OCI Vault. If selected, you need to pre-create vault secrets as mentioned in Create Vault Secrets.
Virtual Cloud Network
If you're using an existing VCN, complete the following:
Network Compartment: Select the compartment you created earlier.
Existing WebCenter Content Virtual Cloud Network: Select the VCN provisioned for WebCenter Content.
If you need to use a new VCN, then select the Create the Virtual Cloud Network check box and complete the following:
Network Compartment: Select the compartment you created earlier.
Virtual Cloud Network Name: Specify a name for the new VCN to be created for this service.
Virtual Cloud Network CIDR: Specify a CIDR to assign to the new VCN.
Object Storage
This section is optional. Complete this section only if you selected the Enable Object Storage as default storage check box in the Stack Configuration section.
Object Storage Compartment: Select the compartment where the bucket was created.
Bucket Name: Specify the bucket name which you created earlier.
User OCID: This will be pre-populated with the current user's OCID. If you are using a different user for creating the API key, specify the user OCID of that user.
Public Key Fingerprint: Specify the fingerprint from the configuration file (that you copied when you created the user API key as part of the prerequisites).
OCI User Private Key Secret Compartment: Choose the compartment that holds the secret for the user API private key.
Secret for OCI User Private Key: Select the secret for the user API private key.
Database Configuration:
Database Strategy: Select the type of database to use for provisioning. The supported databases are: Database System and Autonomous Transaction Processing Database.
If you selected Autonomous Transaction Processing Database as the Database Strategy, then complete the following that are displayed:
Select the value for Autonomous Database compartment.
Select the value for Autonomous Database.
Autonomous Database Admin Password Secret Compartment: Choose the compartment that holds the secret for the Autonomous Database Admin Password.
Secret for Autonomous Database Admin Password: Select the secret for Autonomous Database Admin Password.
If you selected Database System as the Database Strategy, then complete the following that are displayed:
Select the value for DB System compartment.
Select the value for DB System OCID.
PDB name: Provide the PDB name of the DB system.
Select the value for DB System Network Compartment.
Select the value for DB System VCN OCID.
DB System PDB User: Leave the value 'sys' as is. Do not change this user name.
If you have not selected Enable Key Management with OCI Vault, then complete the following that are displayed.
DB System Password: Provide the value of DB System password.
DB System SSH Private key: Upload the DB System SSH Private key which is created without passphrase.
If you selected Enable Key Management with OCI Vault, then complete the following that are displayed.
DB System Password Secret Compartment: Choose the compartment that holds the secret for the DB system password.
Secret for DB System Password: Select the secret for DB system password. When defining the secret key, you must have specified a user-friendly name for each secret. Use the same name here so that it is easy.
DB System SSH Private key Secret Compartment: Choose the compartment that holds the secret for the DB system SSH private key.
Secret for DB System SSH Private key: Select the secret for DB System SSH private key.
Provision WebCenter Content with custom database schema prefix: Select this checkbox to provision WebCenter Content with custom database schema prefix. If not selected, WebCenter Content will be provisioned with random schema prefix.
If you selected the above checkbox, then complete the following that are displayed.
- Custom database schema prefix for WebCenter Content: Provide a value for custom database schema prefix for provisioning WebCenter Content. It can only contain uppercase letters.
Bastion Instance:
If you're using an existing VCN, complete the following:
Existing Subnet for Bastion Host: Select an existing public subnet to use for a Bastion compute instance.
Bastion Host Shape: Select the appropriate Bastion host shape (keep the default value).
WebCenter Content Compute Instance:
Compute Shape: Select the appropriate compute shape.
OCPU count: Select the OCPU count. The default value is 2.
If you're using an existing VCN, complete the following:
Existing Subnet for WebCenter Content Compute Instances: Select an existing subnet to use for WebCenter Content compute instances.
Node Count: Specify the node count. The default value is 2.
File System:
Use Existing File System: Select this check box to use an existing File System and Mount Target.
If selected, you will need to select the compartment and availability domain of the existing File System and provide the File System OCID. The Mount Target must have security rules configured to allow traffic to the chosen VCN CIDR. See Configuring VCN Security Rules for File Storage.
File System Compartment: Choose the compartment where the WebCenter Content stack will be created.
File System Availability Domain: Select the Availability Domain.
Mount Target Subnet CIDR: Provide the value for Mount Subnet CIDR. For example, 10.0.5.0/24.
Load Balancer:
If you're using an existing VCN, complete the following:
Existing Subnet for Load Balancer: Select an existing subnet to use for the load balancer.
Provide the value for Minimum Bandwidth for Flexible Load Balancer.
Provide the value for Maximum Bandwidth for Flexible Load Balancer.
Identity Domain:
Identity Domain URL: Provide the value for IDCS domain URL.
Identity Domain Username: Provide the value for IDCS username who will be configured as the product administrator.
Identity Client ID: Provide the value for IDCS Client ID.
Identity Client Secret Compartment: Choose the compartment that holds the secret for the IDCS client secret.
Secret for the Identity Client Secret: Select the secret for the IDCS client secret.
WebCenter Content WebLogic Domain Configuration:
- WebCenter Content Admin User Name: Leave the value 'weblogic' as is.
If you have not selected Enable Key Management with OCI Vault, then complete the following that are displayed.
WebCenter Content Admin Password: Provide the value for WebCenter Content Admin password.
WebCenter Content Schema Password: Provide the value for WebCenter Content Schema password.
If you selected Enable Key Management with OCI Vault, then complete the following that are displayed.
WebCenter Content Admin Secret Compartment: Choose the compartment that holds the secret for the WebCenter Content Server administrator password.
Secret for WebCenter Content Admin Password: Select the secret for WebCenter Content administrator password.
WebCenter Content Schema Password Secret Compartment: Choose the compartment that holds the secret for the WebCenter Content schema password.
Secret for the WebCenter Content Schema Password: Select the secret for the WebCenter Content schema password.
Click Next. Review all the configuration variables and then select the Run apply check box under Run apply on the created stack section. Click Create.
If everything goes as expected, then navigate to the WebCenter Content stack and click the Application Information tab. You'll see all the provisioned end points for the services under section WebCenter Content Endpoints:
webcenter_content_x1_weblogic_console_endpoint =
"https://<host-IP>:7001/console"
webcenter_content_x2_imaging_endpoint =
"https://<host-IP>:16000/imaging"
webcenter_content_x3_cs_endpoint =
"https://<host-IP>:16200/cs"
webcenter_content_x4_wcc_endpoint =
"https://<host-IP>:16225/wcc"
webcenter_content_x5_ibr_endpoint =
"https://<host-IP>:16250/ibr"
webcenter_content_x6_dc_console_endpoint =
"https://<host-IP>:16400/dc-console"
After provisioning the stack, to create a connection from Imaging to WebCenter Content:
Note: You should not use the public IP of load balancer when making the RIDC connection. To get the private IP of WebCenter Content Load Balancer for RIDC connection, log in to OCI console and navigate to the load balancer details page for WebCenter Content load balancer. Click Backends sets. From the list of backend sets, click the backend set having a name like %-intradocsvr-bset. Hover the mouse over the green tick (next to OK) to get the private IP of the load balancer.
Note:
If you see a stale web location when opening content in the Content Server application (when content is created via Imaging application), then do the following to resolve this issue:
Update the following file in all the WebCenter Content node VMs when you create an application in the Imaging application:
/u01/data/domains/wcc_domain/ucm/cs/data/ipmsys/apps/app<app-no>.hda
In the
app<app-no>.hda
file, update the value forViewerUrlFormat
with correct host name and port of Imaging application:ViewerUrlFormat=https://<hostname>:<port>/imaging/faces/Pages/UrlTools.jspx?ToolName=AWVWR&DocumentId=%s
After making this change, you need to bounce all the WebCenter Content servers from the Weblogic console.
To navigate to the WebCenter Content stack:
In the side menu, select Developer Services, Resource Manager, and then Stacks.
Select your compartment and click the name of the WebCenter Content stack you created.
If something goes wrong or if for any reason you want to do a clean-up of all the resources that were provisioned as part of the WebCenter Content deployment, use Destroy Job to do the clean-up.
Configure FA Adapter Integration with WebCenter Content
Learn to install and configure FA integration (using AdapterFA component) with WebCenter Content on marketplace.
Install WebCenter Content using Marketplace image and stack if not installed yet.
Log in to wls-1 WebCenter Content VM and run the following commands to configure it for FA integration.
sudo su - oracle # For existing stacks after patching (This will have latest scripts and should be used as preferred location) cd /u01/scripts/patch/lcm/sh # For new stacks (If in case configure_wcc_fa_adapter.sh script is not found on above path) cd /u01/scripts/lcm/sh
For non-IDCS SSO-based environment
sh configure_wcc_fa_adapter.sh --fa_domain <fa-domain-host> --ucm_domain <ucm domain host>
For example:
sh configure_wcc_fa_adapter.sh --fa_domain fa-demo.fa.ocs.oc-test.com --ucm_domain wccdemo.cec.ocp.oc-test.com
For IDCS SSO-based environment
sh configure_wcc_fa_adapter.sh --fa_domain <fa-domain-host> --ucm_domain <ucm domain host> --idcs_user <idcs user with wcc administrator role>
For example:
sh configure_wcc_fa_adapter.sh --fa_domain fa-demo.fa.ocs.oc-test.com --ucm_domain wccdemo.cec.ocp.oc-test.com --idcs_user user@oracle.com
Log in to Webcenter Content as an administrator.
Navigate to Administration and then to Configuration for wcc****.
On the Configuration Information page, make a note of the value for the search engine under the System Configuration section.
Under Administration, click Oracle Advanced Security Configurations.
On the Oracle Advanced Security Configurations page, complete the following updates:
If WebCenter Content is set to use DATABASE.METADATA as the search engine:
Select the Core QueryText Security Config check box.
Custom table names: AFOBJECTS
Custom field names: Leave this field blank.
Click Update.
If WebCenter Content is set to use DATABASE.FULLTEXT or OracleTextSearch as the search engine:
Select the Core QueryText Security Config check box.
Custom table names: AFOBJECTS
Custom field names: dreleasestate
Click Update.
If custom metadata is used with DATABASE.METADATA:
Select the Core QueryText Security Config check box.
Custom table names: Leave this field blank.
Custom field names: <xCustomMetadataField1; xCustomMetadataField2; xCustomMetadataField3;...>
Click Update.
If custom metadata is used with DATABASE.FULLTEXT or OracleTextSearch:
Select the Core QueryText Security Config check box.
Custom table names: Leave this field blank.
Custom field names: <xCustomMetadataField1; xCustomMetadataField2; xCustomMetadataField3;...>
Click Update.
Log in to Enterprise Manager as administrator.
Navigate to UCM_Server1, Deployments, Oracle UCM Webservices, Modules and Components, Webservices, AfGrantService, and then to AfGrantAccessPort.
Click Attach/Detach policies.
Click Directly Attached Policies and then click Attach/Detach.
In the Available Policies section, search for oracle/wss_http_token_service_policy
Click Attach, click Validate, and then click Ok.
Restart all WebCenter Content servers.
Configure SAML2 IDCS Single Sign-On in WebCenter Content
Learn to configure SAML2 IDCS Single Sign-On in WebCenter Content.
Prerequisites
Complete the following before running the configuration script.
Create a WebCenter Content Stack
A WebCenter Content stack should have been created from OCI Marketplace on which SAML2 IDCS SSO configuration needs to be configured.
Create an OAuth Client for IDCS
Follow the below instructions based on whether OCI Tenancy IAM is with Identity Domains or not.
For OCI accounts where IAM is with Identity Domains (tenancy with IAM domains), complete the following:
Log in to OCI console.
Navigate to Identity and then Domains.
Select the domain which needs to be used for SSO log-in.
Go to Integrated Applications and click Add application.
Choose Confidential Application and launch the workflow.
On the Add Application Details page, fill the Name and Description fields, and then click Next.
On the Configure OAuth page, select the Configure this application as a client now option under Client configuration section.
In the Authorization section, select the Client credentials check box for the Allowed Grant Types field.
Scroll down and select the Add app roles check box. In the App roles section, add the Identity Domain Administrator role.
Click Next. Leave the default settings for the next page as is and click Finish.
Make a note of the client ID and client secret. These values will be needed when you run the script.
Activate the application.
For OCI accounts where IDCS is not yet migrated to IAM Domains (tenancy without IAM domains), complete the following:
Log in to the IDCS administration console of the federated IDCS.
For example,
https://idcs-abcde.identity.oraclecloud.com/ui/v1/adminconsole
.Navigate to Applications. Click + to add an application. Choose Confidential Application in the wizard:
Add a name and a description on the App details page.
Click Next. Select the Configure this application as a client now option.
In the Authorization section, select the Client credentials check box for the Allowed Grant Types field.
In the Grant the client access to Identity Cloud Service Admin APIs section, click Add to add the application roles. You need to add the Identity Domain Administrator role.
Click Next. Leave the default settings for the next pages as is and click Finish.
Make a note of the client ID and client secret. These values will be needed when you run the script.
Activate the application.
Configuration in WebCenter Content Stack
Run the Configuration Script
A configuration helper script will be available in WebCenter Content stack VM. It can be executed from Admin compute VM or VM-1 (*-wls-1).
The script expects the following inputs.
Argument | Description |
---|---|
idcs_tenant | IDCS tenant name For example, if IDCS URL is idcs-abcde.identity.example.com, then IDCS tenant name would be idcs-abcde. |
idcs_domain | IDCS domain For example, if IDCS URL is idcs-abcde.identity.example.com, then IDCS domain would be identity.example.com. |
idcs_client | Client ID of the OAuth client created in prerequisites |
idcs_client_secret | Client secret of the OAuth client created in prerequisites |
service_host | WebCenter Content stack service host with DNS record mapped to load balancer IP. For example, wccstack1.xyz.com If service host is not available, WebCenter Content stack load-balancer IP can be provided here for testing. |
idcs_user_name | IDCS user who is configured as WebCenter product administrator user |
Complete the following steps to execute the script:
ssh -o ProxyCommand="ssh -W %h:%p -i <key> opc@<bastion-ip>" -i <key> opc@<vm-ip>
sudo su - oracle
cd /u01/scripts/sh
nohup sh configure_sso.sh --idcs_tenant <idcs-tenant> --idcs_domain identity.oraclecloud.com --idcs_client <idcs_client> --idcs_client_secret <idcs_client> --idcs_username <idcs_username> --service_host <service_host> &
The script execution progress can be monitored from /u01/logs/provisioning.log. Once the execution completes without any error, the configuration is completed in WebCenter Content stack environment.
This script covers the steps mentioned in Configuring SAML 2.0 (IDCS) Single Sign-On.
Note: If the configuration was done with load-balancer IP, then the above script needs to be executed again with the service host once the DNS mapping to load-balancer IP is created.
Configuration in your IDCS Tenant
Once the SAML configuration is completed on WebCenter Content, SAML applications will be created under Integrated Applications in the IDCS domain. The WebCenter Content role mapping groups (as described in the table below) are also created.
WebCenter Content Groups | Description |
---|---|
admin | The admin role is assigned to the system administrator. By default, this role has Admin permission to all security groups and all accounts, and has rights to all the administration tools. |
contributor | The contributor role has Read and Write permissions to the Public security group, which enables users to search for, view, check in, and check out content. |
guest | The guest role has Read permission to the Public security group, which enables users to search for and view content. |
sysmanager | The sysmanager role has privileges to access the Admin Server links from the Administration menu in the user interface. |
The Admin user is granted membership to the admin group and can be used to access the service.
The SAML applications will be prefixed with the stack service name. For example, wcc12_ucm_saml, wcc12_capture_saml, wcc12_wcc_saml, and wcc12_imaging_saml.
Add Users to Groups
To add a new user other than the administrator, you would need to add the user to the IDCS WebCenter Content groups based on the permissions required for their usage.
Verification
After the configuration of SAML, verify the WebCenter Content application URLs and validate that the IDCS SSO log-in is working.
Content Server: https://<service_host|lb_ip>:16200/cs
Web UI: https://<service_host|lb_ip>:16225/wcc
Capture: https://<service_host|lb_ip>:16400/dc-console
Imaging: https://<service_host|lb_ip>:16000/imaging
Troubleshoot
This chapter describes common problems that you might encounter and also provides information that can be helpful with the troubleshooting process.
Issue: Provisioning failed
Description
If you encountered a failure when trying to provision WebCenter Content, do the following to see the logs which might help in troubleshooting:
Log in to bastion host.
From bastion host perform ssh to wls-1 VM. For example:
ssh -I <private key> opc@<IP Address of wls-1 VM>
sudo su – oracle
cd /u01/data/domains/logs
vi provisioning.log
Issue: Stale web location when opening content in the Content Server application
Description
If you see a stale web location when opening content in the Content Server application (when content is created via Imaging application), then do the following to resolve this issue:
Update the following file in all the WebCenter Content node VMs when you create an application in the Imaging application:
/u01/data/domains/wcc_domain/ucm/cs/data/ipmsys/apps/app<app-no>.hda
In the
app<app-no>.hda
file, update the value forViewerUrlFormat
with the correct host name and port of Imaging application:ViewerUrlFormat=https://<hostname>:<port>/imaging/faces/Pages/UrlTools.jspx?ToolName=AWVWR&DocumentId=%s
After making this change, you need to bounce all the WebCenter Content servers from the Weblogic console.
Appendix
This appendix provides supporting information related to WebCenter Content stack-provisioning, OpenSearch, and also includes information about known issues.
How to Access WebCenter Content IBR Endpoint accessible via a Private Loadbalancer IP?
WebCenter Content IBR endpoint is accessible via a private loadbalancer IP. Complete the following steps to access this endpoint using SSH tunnelling:
Obtain the Load Balancer private IP from the Stacks UI.
Go to Stacks and then <created_stack>
Click the Application Information tab.
In the Networking section, Load Balancer Private IP will be available.
Execute the following from your local machine:
ssh -i <ssh_private_key_for_bastion> -L 16250:<lb_private_ip>:16250 opc@<bastion_ip>
Access the IBR endpoint using: https://localhost:16250/ibr
About OpenSearch 2.x
Note: You need to use Basic Auth as the authorization method if you are using OpenSearch 2.11.
When configuring OpenSearch 2.11 for WebCenter Content with OCI, use the following steps to get the OpenSearch certificate and test the connection from WebCenter Content instance to the OpenSearch cluster.
To get the OpenSearch certificate, in a shell of WebCenter Content instance, run the following command:
openssl s_client -showcerts -connect <OpenSearch private IP>:9200 </dev/null | sed -n -e '/-.BEGIN/,/-.END/ p' > cert.pem
To test the connection from WebCenter Content instance to the OpenSearch cluster:
/usr/bin/curl -u <username>:<password> https:<OpenSearch private IP>:9200 –insecure
This is merely a simple test to see if WebCenter Content instance can reach the OS cluster. If successful, it will return the following:
[oracle@wcctestinstance ~]$ /usr/bin/curl -u <username>:<password> https://<OpenSearch private IP>:9200 { "name" : "opensearch-master-0", "cluster_name" : "amaaaaaal6hvfiqauqzbmvklzsowhydlrvpdfa544kitmgdymnugepq5nkwq", "cluster_uuid" : "EtrnIgjXQmmuK4gBdf02xg", "version" : { "distribution" : "opensearch", "number" : "2.11.0", "build_type" : "tar", "build_hash" : "unknown", "build_date" : "2024-05-28T05:20:26.940869407Z", "build_snapshot" : false, "lucene_version" : "9.7.0", "minimum_wire_compatibility_version" : "7.10.0", "minimum_index_compatibility_version" : "7.0.0" }, "tagline" : "The OpenSearch Project: https://opensearch.org/" }
The following image shows the OpenSearch Configuration Page when Basic Auth is used as the authorization.
Known Issues
24.8.1 — August 2024
Feature | Description |
---|---|
New Redwood UI | The new Redwood UI supports English only as the UI language and does not offer any translation/localization to other languages. Accessibility guidelines pertaining to WCAG have not been tested for the new Redwood UI. There are alternative UIs, namely the Native UI and the ADF UI that meet the accessibility guidelines. You can use these alternative UI options in case you find any accessibility limitations with the new Redwood UI. |
Using Oracle WebCenter Content on Marketplace in Oracle Cloud Infrastructure
F98077-03
Last updated: August 2024
Copyright © 2024, Oracle and/or its affiliates.
Primary Author: Oracle Corporation