What's New in Oracle WebCenter Forms Recognition on Marketplace

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

24.7.1 — July 2024

Feature Description
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 Forms Recognition Stack.
Options to use existing subnet when provisioning stack You have options to use an existing subnet when provisioning the stack. See Provision WebCenter Forms Recognition 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.

Get Started with Oracle WebCenter Forms Recognition on Marketplace

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

About Oracle WebCenter Forms Recognition on Marketplace

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

Oracle WebCenter Forms Recognition on Marketplace is available as a Paid Marketplace offering. See About the License for Oracle WebCenter Forms Recognition on Marketplace.

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

About the License for Oracle WebCenter Forms Recognition on Marketplace

Oracle WebCenter Forms Recognition on Marketplace is based on Oracle WebCenter Forms Recognition 14c (14.1.1). Oracle WebCenter Forms Recognition on Marketplace is available as a Paid offering:

About Roles and User Accounts

Oracle WebCenter Forms Recognition 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 Forms Recognition 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 Forms Recognition.

For information about how to add user accounts in Oracle Cloud, see:

Create and View Oracle WebCenter Forms Recognition on Marketplace Instances

The information in this chapter will help you create and view Oracle WebCenter Forms Recognition 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.

  1. Go to http://cloud.oracle.com.

  2. Enter your cloud account name and click Next.

  3. 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.

  4. 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 Forms Recognition stack.

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

System Requirements

You require access to the following services to use Oracle WebCenter Forms Recognition on OCI.

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 250GB
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.

Create a Compartment

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

  1. Sign in to the Oracle Cloud Infrastructure Console.

  2. Open the navigation menu and click Identity & Security. Under Identity, click Compartments. A list of the existing compartments in your tenancy is displayed.

  3. Click Create Compartment.

  4. Enter the following:

    • Name: Specify a name. For example, wfr-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.

  5. Click Create Compartment.

  6. 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 wfr and then create a policy with the following statements.

      • allow group wfr to manage instance-family in compartment wfr-compartment

      • allow group wfr to manage virtual-network-family in compartment wfr-compartment

      • allow group wfr to manage volume-family in compartment wfr-compartment

      • allow group wfr to manage load-balancers in compartment wfr-compartment

      • allow group wfr to manage orm-family in compartment wfr-compartment

        where wfr is the group name and wfr-compartment is the compartment name.

        You can use any name (wfr and wfr-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.

Complete the following to create a new DB system:

Create VCN

  1. Log in to OCI Console, navigate to Networking, then to Virtual Cloud Networks.

  2. Click Create VCN via Wizard.

  3. Click Start VCN Wizard.

  4. VCN name: Provide a name.

  5. Compartment: Specify the compartment in which the VCN needs to be created.

  6. VCN IPv4 CIDR block: Specify IPv4 CIDR block (for example, 10.0.0.0/16).

  7. Select the Use DNS hostnames in this VCN check box.

  8. In the Configure public subnet and Configure private subnet sections, specify the correct CIDR blocks and click Next.

  9. Make sure to create the necessary gateways such as Internet gateway, NAT gateway, and Service gateway.

  10. Click Create.

The VCN is created.

Create a New DB System

  1. Create a new DB system in the VCN you created earlier.

  2. 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 Forms Recognition 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

  1. 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.

  2. 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.

  3. 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
compute-instance-password Secret for WebCenter Forms Recognition Compute Instance Password The Secret Contents field should be populated with the password value for WebCenter Forms Recognition Compute Instance. The Windows compute instance password must comply with Microsoft's password policy (but the password length that is allowed is 12 to 14 characters).
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.
wfr-schema-password Secret for WebCenter Forms Recognition 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 Forms Recognition Stack

You can provision Oracle WebCenter Forms Recognition on Marketplace in a selected compartment in Oracle Cloud Infrastructure.

To provision Oracle WebCenter Forms Recognition on Marketplace:

  1. Navigate to the WebCenter Forms Recognition 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+Forms+Recognition.

      The Marketplace listings for WebCenter Forms Recognition 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 Forms Recognition. The Marketplace listings for WebCenter Forms Recognition are displayed.

    4. Click the title of the listing you want to use and review the information on the Overview page.

  2. Accept the terms and restrictions, and then click Launch Stack. The Create Stack wizard is displayed.

  3. 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, WFR). 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.

      • OCI Policies: Select this check box if you need the stack to create policies to provision WebCenter Forms Recognition 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 Forms Recognition Virtual Cloud Network: Select the VCN provisioned for WebCenter Forms Recognition.

      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.

        • 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 Forms Recognition with custom database schema prefix: Select this checkbox to provision WebCenter Forms Recognition with custom database schema prefix. If not selected, WebCenter Forms Recognition 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 Forms Recognition. It can only contain uppercase letters.

    4. WebCenter Forms Recognition 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 Forms Recognition Compute Instances: Select an existing subnet to use for WebCenter Forms Recognition compute instances.

      • WebCenter Forms Recognition Compute Instance Secret Password Compartment: Choose the compartment that holds the password secret for the WebCenter Forms Recognition Subnet Compute Instance.

      • Secret for WebCenter Forms Recognition Compute Instance Password: Select the secret that contains the password for the Windows compute instance.

    5. 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.

    6. WebCenter Forms Recognition Secrets:

      If you have not selected Enable Key Management with OCI Vault, then complete the following.

      • WebCenter Forms Recognition Schema Password: Provide the value for WebCenter Forms Recognition Schema password.

      If you selected Enable Key Management with OCI Vault, then complete the following that are displayed.

      • WebCenter Forms Recognition Schema Password Secret Compartment: Choose the compartment that holds the secret for the WebCenter Forms Recognition schema password.

      • Secret for the WebCenter Forms Recognition Schema Password: Select the secret for the WebCenter Forms Recognition 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 Forms Recognition stack and click the Application Information tab. You'll see all the provisioned end points for the services under section WebCenter Forms Recognition Endpoints.

Note: If provisioning fails, connect to Windows RDP and check the following logs: C:\Program Files\Cloudbase Solutions\Cloudbase-Init\log and C:\u01\data\domains\logs.

To navigate to the WebCenter Forms Recognition stack:

About Connecting to Windows VM using Bastion and RDP

See Creating a Port Forwarding Session in Bastion and Connecting to a Port Forwarding Session for information.

To Update the Administrator Password in the WebCenter Forms Application

  1. Connect to the Windows VM by following the steps in About Connecting to Windows VM using Bastion and RDP.

  2. Open the WebCenter Forms Recognition Designer Application.

  3. Load the AP Project: C:\AP_Projects\AP Project 3520\Global\AP Packaged Project_3520.sdp

  4. Open Options, then Users, Groups and Roles.

  5. Go to the Change Password tab. Provide old and new passwords to update the password. Keep the Update password in Database check box selected.

  6. Click Apply. A confirmation pop-up dialog indicating that the password has been changed will show up. Click OK in the pop-up dialog to continue.

  7. Another pop-up dialog asking if you want to save your current project file will show up. Click Yes and close the WebCenter Forms Recognition Designer application.

  8. Log in to the WebCenter Forms Recognition endpoints with the new password to confirm that the password change has completed successfully.

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 Forms Recognition deployment, use Destroy Job to do the clean-up.

To Destroy Stack

First step: Complete the following steps to execute the destruct script on the Windows VM:

  1. Connect to the Windows VM by following the steps in About Connecting to Windows VM using Bastion and RDP.

  2. Open PowerShell (without administrator) terminal.

  3. Execute the following command to trigger the destruct script: python C:\u01\scripts\python\provisioning\destruct.py

Second step: On the Stack details page (from the OCI console), use Destroy and Delete Stack options for the stack.