What's New in Oracle WebCenter Sites on Marketplace

Learn about the new and changed features in Oracle WebCenter Sites on Marketplace.

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 Sites Stack.
Options to use existing subnet when provisioning stack	You have options to use an existing subnet when provisioning the stack. See Provision WebCenter Sites 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 Sites Stack.
Migration from Oracle Content Management to Oracle WebCenter Sites	You can automatically import assets and data model from Oracle Content Management to Oracle WebCenter Sites using a new functionality available in WebCenter Sites. For more information, see Doc ID 3033752.1 in My Oracle Support.

24.6.1 — June 2024

Feature	Description
PDB name	You can now specify the PDB name when configuring the database. See Provision WebCenter Sites Stack.
Database Strategy	You can now specify the Database Strategy (type of database) such as Database System or Autonomous Transaction Processing Database when configuring the database. See Provision WebCenter Sites Stack.
Integration with OCI Logging	You can integrate WebCenter Logs with OCI Logging. See Integrating WebCenter Logs with OCI Logging.

Get Started with Oracle WebCenter Sites on Marketplace

Here’s information about Oracle WebCenter Sites on Marketplace that will help you get started:

About Oracle WebCenter Sites on Marketplace
About the License for Oracle WebCenter Sites on Marketplace
About Roles and User Accounts

About Oracle WebCenter Sites on Marketplace

Oracle WebCenter Sites on Marketplace is provided as a VM-based solution on Oracle Cloud Infrastructure.

Oracle WebCenter Sites on Marketplace is available in two types of Marketplace offerings: Paid and BYOL. See About the License for Oracle WebCenter Sites on Marketplace.

Oracle WebCenter Sites on Marketplace helps customers to provision/set up the environment in few clicks and enables to deliver WebCenter Sites solutions on cloud.

About the License for Oracle WebCenter Sites on Marketplace

Oracle WebCenter Sites on Marketplace is based on Oracle WebCenter Sites 12c (12.2.1.4). Oracle WebCenter Sites on Marketplace is available in two types of Marketplace offerings:

Paid: Use the following Oracle WebCenter Sites (Paid) listing to use Universal Credits pricing:
- Oracle WebCenter Sites 12c (Paid)
  
  See Oracle Universal Credits.
BYOL: Use the Oracle WebCenter Sites (BYOL) listing to Bring Your Own License using your existing Oracle WebCenter Sites 12c (12.2.1.4) on-premises license, or you can purchase a new license for Oracle WebCenter Sites 12c (12.2.1.4).

When you activate Oracle WebCenter Sites 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 Sites 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 Sites 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 Sites.

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 Sites on Marketplace Instances

The information in this chapter will help you create and view Oracle WebCenter Sites on Marketplace instances.

Before You Begin
- Sign in to Oracle Cloud Infrastructure Console
- Prerequisites
Provision WebCenter Sites Stack
Set Up Load Balancer Certificate and DNS
Set Up a WebCenter Sites Cluster

Before You Begin

Before you begin, you would need to complete the following tasks and prerequisites.

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 default domain.
- 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 Sites stack.

System Requirements
Generate SSH key pair
Create a Compartment
Create Database
IDCS

After completing the above prerequisites, you can proceed to provision the WebCenter Sites stack.

System Requirements

You require access to the following services to use Oracle WebCenter Sites 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 Sites nodes.

Create a Compartment

If your tenancy does not already include a compartment for your Oracle WebCenter Sites 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:

Sign in to the Oracle Cloud Infrastructure Console.
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, wcs-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.
Click Create Compartment.
Once the compartment is created, if you are not an administrator, ask your administrator to grant the following manage and use permissions in the compartment:
1. Navigate to Identity and Security, Policies, and then Create Policies.
2. To allow a non-administrator to execute the stack, create an IAM group called wcs and then create a policy with the following statements.
  - allow group wcs to manage instance-family in compartment wcs-compartment
  - allow group wcs to manage virtual-network-family in compartment wcs-compartment
  - allow group wcs to manage volume-family in compartment wcs-compartment
  - allow group wcs to manage load-balancers in compartment wcs-compartment
  - allow group wcs to manage orm-family in compartment wcs-compartment
    
    where wcs is the group name and cs-compartment is the compartment name.
    
    Note: You can use any name (wcs and wcs-compartment are examples).

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.

Create VCN
Create a New DB System

Create VCN

Complete the following to create a new DB system:

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.
1. Log in to the console.
2. Click Oracle Database.
3. Click Oracle Base Database Service and then click Create DB Systems.
4. 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 Sites 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.
5. Click Create DB System and wait for the DB provisioning to be completed before you proceed to the next step.

IDCS

Create a new IDCS Confidential App for WebCenter Sites provisioning. Log in to your IDCS administration console. For example, https://<your-idcs-link>.identity.oraclecloud.com/ui/v1/adminconsole. You can find this URL on the OracleIdentityCloudService section by navigating to Identity, Federation, and then Identity Provider Details. The field name that has this URL is Oracle Identity Cloud Service Console.
Click Integrated applications.
Click Add application on the Integrated Applications page to create a new confidential app.
Choose Confidential Application in the Add Application pop-up.
In the Details section, provide a name and click Next.
In the Client section, choose Configure this application as client now and select the following grant types under Authorization:
- Client Credentials
- JWT Assertion
- SAML2 Assertion
Skip all other sections by clicking Next till you reach the Finish button.
Make a note of the Client ID and Client Secret for this app. Client Secret will be added to the vault's secret later.
Navigate to the application created and click Activate to enable this app for use in WebCenter Sites provisioning.

Create Vault Secrets

Log in to the OCI console and search for Vault, and then create a vault app.
1. Click Create Vault.
2. Select the compartment you created earlier
3. 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
wcs-admin-password	Secret for WebCenter Sites 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.
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.
wcs-schema-password	Secret for Sites 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

Provision WebCenter Sites Stack

You can provision Oracle WebCenter Sites on a Marketplace instance in a selected compartment in Oracle Cloud Infrastructure.

To provision Oracle WebCenter Sites on a Marketplace instance:

Navigate to the WebCenter Sites listing on Marketplace by direct URL or by browsing in Oracle Cloud Infrastructure.

Using direct URL:
1. In your browser, enter https://cloudmarketplace.oracle.com/marketplace/en_US/homePage.jspx?tag=WebCenter+Sites.
  
  The Marketplace listings for WebCenter Sites are displayed.
2. Click the title of the listing you want to use. The landing page of that listing is displayed.
3. Click Get App.
4. Select your Oracle Cloud Infrastructure region and click Sign In.
5. Sign in to the Oracle Cloud Infrastructure Console.
By browsing:
1. Sign in to the Oracle Cloud Infrastructure Console.
2. Open the navigation menu and click Marketplace. Under Marketplace, click All Applications.
3. In the Marketplace search field, enter WebCenter Sites. The Marketplace listings for WebCenter Sites are displayed.
4. 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.
1. Stack information:
  - Enter name and description.
  - Create in Compartment: Select the compartment.
  - Terraform version: Specify the Terraform version and click Next.
2. Configure variables:
  
  Stack Configuration
  - Resource Name Prefix: Enter a prefix (for example, Sites). 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).
  - OCI Policies: Select this check box if you need the stack to create policies to provision WebCenter Sites resources, configure Database Network, and read Vault Secrets. Deselecting this option is for Advanced users only.
  - 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 Sites Virtual Cloud Network: Select the VCN provisioned for WebCenter Sites.
  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.
3. 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 (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 Sites with custom database schema prefix: Select this checkbox to provision WebCenter Sites with custom database schema prefix. If not selected, WebCenter Sites will be provisioned with random schema prefix.
      
      If you selected the above checkbox, then complete the following.
      - Custom database schema prefix: Provide a value for custom database schema prefix for provisioning WebCenter Sites. It can only contain uppercase letters.
4. 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).
5. WebCenter Sites 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 Sites Compute Instances: Select an existing subnet to use for WebCenter Sites compute instances.
6. 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 Sites 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.
7. 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.
8. Identity Cloud Service Integration:
  - Identity Domain URL: Provide the value for IDCS domain URL.
  - 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.
9. WebCenter Sites WebLogic Domain Configuration:
  - WebCenter Sites 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 Sites Admin Password: Provide the value for WebCenter Sites Admin password.
  - WebCenter Sites Schema Password: Provide the value for WebCenter Sites Schema password.
  If you have selected Enable Key Management with OCI Vault, then complete the following that are displayed.
  - WebCenter Sites Admin Secret Compartment: Choose the compartment that holds the secret for the WebCenter Sites Server administrator password.
  - Secret for WebCenter Sites Admin Password: Select the secret for WebCenter Sites administrator password.
  - WebCenter Sites Schema Password Secret Compartment: Choose the compartment that holds the secret for the WebCenter Sites schema password.
  - Secret for the WebCenter Sites Schema Password: Select the secret for the WebCenter Sites 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 Sites stack and click the Application Information tab. Under the Output section, you'll see the end points for the services.

webcenter_sites_x1_weblogic_console_endpoint = "https://<host-IP>:7001/console"
webcenter_sites_x2_webcenter_sites_endpoint = "https://<host-IP>:7003/sites"
webcenter_sites_cas_endpoint = "https://<host-IP>:7003/cas"
webcenter_sites_sites_config_setup_endpoint = "https://<host-IP>:7003/sites/sitesconfigsetup"
webcenter_sites_sites_patch_setup_endpoint = "https://<host-IP>:7003/sites/sitespatchsetup"

To navigate to the WebCenter Sites stack:

In the side menu, select Developer Services, Resource Manager, and then Stacks.
Select your compartment and click the name of the WebCenter Sites 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 Sites deployment, use Destroy Job to do the clean-up.

Set Up Load Balancer Certificate and DNS

For Oracle WebCenter Sites, set up the load balancer certificate and DNS record.

Update the Listener

Navigate to the load balancer details page of the WebCenter Sites stack by selecting Networking, Load balancers, Load balancer and then selecting the load balancer.
Click Certificates under Resources.
Under Certificates, select Load balancer managed certificate from the drop-down list. Click Add certificate. See SSL Certificates for Load Balancers documentation for information about setting up the SSL certificate.
Click Listeners under Resources and edit the <stack name>-sites-lsnr listener.
On the Edit Listener page, select the load balancer managed certificate (created in step 3) from the drop-down list and click Save changes.

Note: Wait for the work request to complete and reach Succeeded status.

Add DNS Record for the Load Balancer IP

Note the public IP of the load balancer created for the stack.
Log in to OCI administration VM.
Add a DNS record for the domain name mapped to the IP of the load balancer. See DNS Service documentation for information about management of DNS records.

Set Up WebCenter Sites Configurator

Access the WebCenter Sites Configurator URL https://<DNS host>:7003/sites/sitesconfigsetup and click Begin.
Retain the default values for WebCenter Sites Shared Directory section and click Next.
Retain the default value for Database Parameters section and click Next.
For Web Application Parameters section, specify the following and click Next:
- Host name for WebCenter Sites: Specify the DNS host name.
- Port number for WebCenter Sites: 7003
- Are you installing over a secure connection?: Yes
For CAS Deployment Information section, specify the following and click Next:
- Server host name: Specify the DNS host name.
- Server port number: 7003
- Server host name of internally accessible CAS: Specify the DNS host name
- Server port number of internally accessible CAS: 7003
- Server host name where CAS is actually deployed: DNS host name
For WebCenter Sites Administrator Accounts section, retain the default values or change the values if required, and then click Next.
For Sample Sites section, specify as needed and click Next.
In the Configuration Summary section, click Test. After the test is successful, click Start.
You'll see that the configuration is in progress. Once the configuration is completed, you'll see a message indicating that it has been completed.
Restart the WebCenter Sites servers and access the WebCenter Sites URL https://<DNS host>:7003/sites. Log in using the credentials (set in Step 6).
Access https://<DNS host>:7003/sites/sitespatchsetup and click Begin. Once the configuration is completed, you'll see a message indicating that it has been completed.

Scale Out Job

Log in to the OCI console and navigate to your WebCenter Sites stack (that you created earlier) and click Edit stack.
Verify the stack name and click Next.
In the Node Count field, specify 2 (or more as needed) and click Next.
In the Review section, verify the configuration changes, select the Run apply check box and click Save changes.
This will start a new job (scale out operation) that will take some time to complete.
Upon completion of the scale out job, log in to the WLS console (https://<DNS host>:7001/console) to verify that your environment has been updated with the number of additional managed servers matching the node count specified in step 3.

Configuration of Manual Unicast Cluster

Connect to each of the WebCenter Sites custom nodes. Make sure to connect to the Bastion machine first and then connect to the target WebLogic server node.

Connect to your Bastion server: ssh i <key> opc@<bastion-ip>

Then, connect to node(s): ssh -i <key> opc@<wls-node-ip> sudo su oracle

Replace "cacheManagerPeerListenerFactory" and "cacheManagerPeerProviderFactory" with data listed below in linked-cache.xml, cs-cache.xml, ticket-cache.xml, cas-cache.xml, and ss-cache.xml files located in the directory /u01/data/domains/wcs_domain/wcsites/wcsites/config.

Note: rmiUrls parameter should include IP addresses of other nodes in the cluster. For example, if your cluster consists on node1, node2, and node3, and you're updating files on node1, rmiUrls should include IP addresses of node2 and node3. If you're updating files on node2, rmiUrls should include IP addresses of node1 and node3.

linked-cache.xml

# Replace or comment out the following nodes


    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4445, timeToLive=1" />

# with following

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=40001" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//[IP ADDRESS OF NODE MEMBER 3]:40001/notifier|//[IP ADDRESS OF NODE MEMBER 3]:40001/notifier|..." />

# For example:

<!--   
    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4445, timeToLive=1" />
-->

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=40001" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//10.0.8.180:40001/notifier" />

cs-cache.xml

# Replace or comment out the following nodes

   <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4444, timeToLive=1" />

# with following

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=41001" />

   <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//[IP ADDRESS OF NODE MEMBER 2]:41001/notifier|//[IP ADDRESS OF NODE MEMBER 3]:41001/notifier|..." />

# For example:

 <!--   
   <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4444, timeToLive=1" />
-->

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=41001" />

   <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//10.0.8.180:41001/notifier" />

ticket-cache.xml

# Replace or comment out following nodes

  <cacheManagerPeerProviderFactory
        class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
        properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.1, multicastGroupPort=4346, timeToLive=1"
        propertySeparator="," />

  <cacheManagerPeerListenerFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
      properties="port=4346,remoteObjectPort=41002" />

# With following

  <cacheManagerPeerProviderFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
      properties="peerDiscovery=manual,rmiUrls=//[IP ADDRESS OF NODE MEMBER 2]:42001/cas_st|//[IP ADDRESS OF NODE MEMBER 2]:42001/cas_tgt"|//[IP ADDRESS OF NODE MEMBER 3]:42001/cas_st|//[IP ADDRESS OF NODE MEMBER 3]:42001/cas_tgt|..." />
  <cacheManagerPeerListenerFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
      properties="port=42001" />    

# For example:

 <!--
  <cacheManagerPeerProviderFactory
        class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
        properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.1, multicastGroupPort=4346, timeToLive=1"
        propertySeparator="," />
-->
<!--
  <cacheManagerPeerListenerFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
      properties="port=4346,remoteObjectPort=41002" />
 -->

  <cacheManagerPeerProviderFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
      properties="peerDiscovery=manual,rmiUrls=//10.0.8.180:42001/cas_st|//10.0.8.180:42001/cas_tgt" />
  <cacheManagerPeerListenerFactory
      class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
      properties="port=42001" />

cas-cache.xml

# Replace or comment out following nodes

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />


    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4666, timeToLive=1" />

# With following

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=43001" />
    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              //[IP ADDRESS OF NODE MEMBER 2]:43001/notifier|//[IP ADDRESS OF NODE MEMBER 3]:43001/notifier|..." />

# For example:

<!--
    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />


    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4666, timeToLive=1" />
-->

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=43001" />
    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//10.0.8.180:43001/notifier" />

ss-cache.xml

# Replace or comment out following nodes

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4844, timeToLive=1" />

# With following

    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=44001" />
    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//[IP ADDRESS OF NODE MEMBER 2]:44001/notifier|//[IP ADDRESS OF NODE MEMBER 3]:44001/notifier|..." />

# For example:

<!--
    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="" />

    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0,
                                multicastGroupPort=4844, timeToLive=1" />
-->


    <cacheManagerPeerListenerFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory"
            properties="port=44001" />
    <cacheManagerPeerProviderFactory
            class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
            properties="peerDiscovery=manual,
                              rmiUrls=//10.0.8.180:44001/notifier" />

Restart the managed servers.
To verify, log in to https://<DNS host>:7003/sites. Check the CAS Cache, Site Cache, and so on for the configuration changes by navigating to them. Select Administration, System Tools, and then Cache Management to navigate to them.

Set Up a WebCenter Sites Cluster

You can set up a WebCenter Sites cluster with a primary cluster node on one machine and one or more secondary cluster nodes on the same or different machines. The first WebCenter Sites managed server you create is the primary node, and any additional WebCenter Sites managed servers in the same domain are the secondary nodes.

To create a WebCenter Sites cluster:

Log in to WebCenter Sites (https://<host-IP>:7003/sites). Navigate to Admin, System Tool, and then Cluster Management.
Complete the following by choosing the Add option from the Choose Option drop-down menu:
1. Node name: Enter a name. For example: wcsites_server1.
2. Host name: The host IP address of wcsites_server1. The actual listener address of the node and not the load balancer.
3. Port number: 7003
4. Batch Host name: The IP address of the host where wcsites_server1 is running (wcsites_server1 is the dedicated batch host.)
5. Batch Port number: 7003
6. Are you installing over a secure connection?: No Click Add.
  
  Note: The primary node wcsites_server1 must be registered first.
Complete the following for the secondary node:
1. Node name: Enter a name. For example: wcsites_server2.
2. Host name: The host IP address of wcsites_server2. The actual listener address of the node and not the load balancer.
3. Port number: 7003
4. Batch Host name: The IP address of the host where wcsites_server1 is running (wcsites_server1 is the dedicated batch host.)
5. Batch Port number: 7003
6. Are you installing over a secure connection?: No Click Add.

Create and View Oracle WebCenter Sites Satellite Server on Marketplace Instances

If you want to configure WebCenter Sites Satellite Server on Marketplace, complete the steps mentioned in this chapter. You can skip this chapter if you do not want to configure WebCenter Sites Satellite Server on Marketplace.

About the License for Oracle WebCenter Sites Satellite Server on Marketplace

Oracle WebCenter Sites Satellite Server on Marketplace is based on Oracle WebCenter Sites Satellite Server 12c (12.2.1.4). Oracle WebCenter Sites Satellite Server on Marketplace is available as a Paid offering:

Paid: Use the following Oracle WebCenter Sites Satellite Server (Paid) listing to use Universal Credits pricing:

Oracle WebCenter Sites Satellite Server 12c (Paid)

See Oracle Universal Credits.

Before You Begin

Before you begin, you would need to complete the following tasks and prerequisites.

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 default domain.
- 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 Sites Satellite Server stack.

System Requirements
Generate SSH key pair
Create a Compartment
Create Database
Create Vault Secrets

After completing the above prerequisites, you can proceed to provision the WebCenter Sites Satellite Server stack.

System Requirements

You require access to the following services to use Oracle WebCenter Sites Satellite Server on OCI.

Identity and Access Management (IAM)
Compute, Network, Block Storage
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
Vault & Key	1
Secrets	4
Load Balancer	Flexible Load Balancer

See Service Limits in the Oracle Cloud Infrastructure documentation.

Generate SSH key pair

See generate_ssh_key for generating an SSH key pair.

Create a Compartment

If your tenancy does not already include a compartment for your Oracle WebCenter Sites Satellite Server 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:

Sign in to the Oracle Cloud Infrastructure Console.
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, wcss-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.
Click Create Compartment.
Once the compartment is created, if you are not an administrator, ask your administrator to grant the following manage and use permissions in the compartment:
1. Navigate to Identity and Security, Policies, and then Create Policies.
2. To allow a non-administrator to execute the stack, create an IAM group called wcss and then create a policy with the following statements.
  - allow group wcss to manage instance-family in compartment wcss-compartment
  - allow group wcss to manage virtual-network-family in compartment wcss- compartment
  - allow group wcss to manage volume-family in compartment wcss-compartment
  - allow group wcss to manage load-balancers in compartment wcss-compartment
  - allow group wcss to manage orm-family in compartment wcss-compartment
    
    where wcss is the group name and wcss-compartment is the compartment name.
    
    Note: You can use any name (wcss and wcss-compartment are examples).

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.

Create VCN
Create a New DB System

Create VCN

Complete the following to create a new DB system:

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.
1. Log in to the console.
2. Click Oracle Database.
3. Click Oracle Base Database Service and then click Create DB Systems.
4. 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 Sites Satellite Server 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.
5. Click Create DB System and wait for the DB provisioning to be completed before you proceed to the next step.

Create Vault Secrets

Log in to the OCI console and search for Vault, and then create a vault app.
1. Click Create Vault.
2. Select the compartment you created earlier
3. 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
wcss-admin-password	Secret for WebCenter Sites Satellite Server 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.
wcss-schema-password	Secret for WebCenter Sites Satellite Server 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

Provision WebCenter Sites Satellite Server

You can provision Oracle WebCenter Sites Satellite Server on a Marketplace instance in a selected compartment in Oracle Cloud Infrastructure.

To provision Oracle WebCenter Sites Satellite Server on a Marketplace instance:

Navigate to the WebCenter Sites Satellite Server listing on Marketplace by direct URL or by browsing in Oracle Cloud Infrastructure.

Using direct URL:
1. In your browser, enter https://cloudmarketplace.oracle.com/marketplace/en_US/homePage.jspx?tag=WebCenter+Sites+Satellite+Server.
  
  The Marketplace listings for WebCenter Sites Satellite Server are displayed.
2. Click the title of the listing you want to use. The landing page of that listing is displayed.
3. Click Get App.
4. Select your Oracle Cloud Infrastructure region and click Sign In.
5. Sign in to the Oracle Cloud Infrastructure Console.
By browsing:
1. Sign in to the Oracle Cloud Infrastructure Console.
2. Open the navigation menu and click Marketplace. Under Marketplace, click All Applications.
3. In the Marketplace search field, enter WebCenter Sites Satellite Server.
  
  The Marketplace listings for WebCenter Sites Satellite Server are displayed.
4. 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.
1. Stack information:
  - Enter name and description.
  - Create in Compartment: Select the compartment.
  - Terraform version: Specify the Terraform version and click Next.
2. Configure variables:
  
  Stack Configuration
  - Resource Name Prefix: Enter a prefix (for example, Sites). 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).
  Virtual Cloud Network
  - Network Compartment: Select the compartment you created earlier.
  - Network: Select the VCN you created earlier.
3. 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.
  - 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.
4. Bastion Instance:
  - Bastion Host Subnet CIDR: Provide the value for Bastion host subnet CIDR. For example, 10.0.2.0/24.
  - Bastion Host Shape: Select the appropriate Bastion host shape (keep the default value).
5. WebCenter Sites Satellite Server Compute Instance:
  - Compute Shape: Select the appropriate compute shape.
  - OCPU count: Select the OCPU count. The default value is 2.
  - WebCenter Sites Satellite Server Subnet CIDR: Provide the value for WebCenter Sites Satellite Server subnet CIDR. For example, 10.0.3.0/24.
6. Load Balancer:
  - Provide the value for Load Balancer Subnet CIDR. For example, 10.0.4.0/24.
  - Provide the value for Minimum Bandwidth for Flexible Load Balancer.
  - Provide the value for Maximum Bandwidth for Flexible Load Balancer.
7. WebCenter Sites Satellite Server WebLogic Domain Configuration:
  - WebCenter Sites Satellite Server Admin User Name: Leave the value 'weblogic' as is.
  - WebCenter Sites Satellite Server Admin Secret Compartment: Choose the compartment that holds the secret for the WebCenter Sites Satellite Server administrator password.
  - Secret for WebCenter Sites Satellite Server Admin Password: Select the secret for WebCenter Sites Satellite Server administrator password.
  - WebCenter Sites Satellite Server Schema Password Secret Compartment: Choose the compartment that holds the secret for the WebCenter Sites Satellite Server schema password.
  - Secret for the WebCenter Sites Satellite Server Schema Password: Select the secret for the WebCenter Sites Satellite Server 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 Sites Satellite Server stack and click the Application Information tab. Under the Output section, you'll see the end point for the service.

webcenter_sites_satellite_weblogic_console_endpoint = "https://<host-IP>:7001/console"

To navigate to the WebCenter Sites Satellite Server stack:

In the side menu, select Developer Services, Resource Manager, and then Stacks.
Select your compartment and click the name of the WebCenter Sites Satellite Server stack you created.

Note: If provisioning fails, check the log at: /u01/data/domains/logs/provisioning.log.

After the stack is created, complete the following steps:

Update the values for the following properties in the wcs_satelliteserver_properties_bootstrap.ini file at /u01/data/domains/ wcs_domain/wcsites/satelliteserver/config/.

oracle.wcsites.hostname ### associated WebCenter Sites DNS host name
oracle.wcsites.system.admin.user ### associated WebCenter Sites user name
oracle.wcsites.system.admin.password ### associated WebCenter Sites password
oracle.wcsites.cas.internal.hostname ### associated WebCenter Sites DNS host name
oracle.wcsites.satelliteserver.user ### satellite server user name
oracle.wcsites.satelliteserver.password ### satellite server password

Execute the following command to run the configuration of the satellite server in silent mode:

java -jar /u01/app/oracle/middleware/wcsites/satelliteserver/satellite-configurator.jar \
-silent /u01/data/domains/wcs_domain/wcsites/satelliteserver/config


###############
Example Output:
SatelliteServer config directory will be configured at: /u01/data/domains/wcs_domain/wcsites/satelliteserver/config/

Satellite Server Configuration is successful. Please complete Web Application Deployment steps and Start application server.

Start the satellite server (https://<Host IP>:7003/ss/cachetool/inventory.jsp).
Tail the following out file and make sure that the server starts without any issue:

tail -f /u01/data/domains/logs/satellite_server1.out

Also tail the sites log, to make sure that the registration is successful.

tail -f /u01/data/domains/wcs_domain/servers/satellite_server1/logs/sites.log

The log information in the sites log for successful registration should look similar to the following.
```
[2024-03-19T13:57:41.949+00:00] [satellite_server1] [NOTIFICATION] [] [oracle.wcsites.rest.registration]
[tid: 28] [userId: <anonymous>] [ecid: 319dd37c-3332-4da6-9ab2-03325e5a9726-00000006,0]
[APP: satelliteserver] [partition-name: DOMAIN] [tenant-name: GLOBAL] 
[SatelliteServerRegistrationImpl] Registration successful with id : 1700061855642
```

Title and Copyright Information

Using Oracle WebCenter Sites on Marketplace in Oracle Cloud Infrastructure

G10780-02

Last updated: July 2024

Primary Author: Oracle Corporation

What's New in Oracle WebCenter Sites on Marketplace

24.7.1 — July 2024

24.6.1 — June 2024

Get Started with Oracle WebCenter Sites on Marketplace

About Oracle WebCenter Sites on Marketplace

About the License for Oracle WebCenter Sites on Marketplace

About Roles and User Accounts

Create and View Oracle WebCenter Sites on Marketplace Instances

Before You Begin

Sign in to Oracle Cloud Infrastructure Console

Prerequisites

System Requirements

Generate SSH key pair

Create a Compartment

Create Database

Create VCN

Create a New DB System

IDCS

Create Vault Secrets

Provision WebCenter Sites Stack

Set Up Load Balancer Certificate and DNS

Update the Listener

Add DNS Record for the Load Balancer IP

Set Up WebCenter Sites Configurator

Scale Out Job

Configuration of Manual Unicast Cluster

Set Up a WebCenter Sites Cluster

Create and View Oracle WebCenter Sites Satellite Server on Marketplace Instances

About the License for Oracle WebCenter Sites Satellite Server on Marketplace

Before You Begin

Sign in to Oracle Cloud Infrastructure Console

Prerequisites

System Requirements

Generate SSH key pair

Create a Compartment

Create Database

Create VCN

Create a New DB System

Create Vault Secrets

Provision WebCenter Sites Satellite Server