Configuring SOA Schemas for Transactional Recovery Privileges Backing Up the Database

Database and Environment Preconfiguration 2-5 ■ For Oracle Enterprise Content Management, expand Enterprise Content Management , and select Oracle Content Server 11g - Complete. Click Next. 8. In the Schema Passwords screen, enter passwords for the main and additional auxiliary schema users, and click Next. 9. In the Map Tablespaces screen, choose the tablespaces for the selected components, and click Next.

10. In the Summary screen, click Create.

11. In the Completion Summary screen, click Close.

2.1.3 Configuring SOA Schemas for Transactional Recovery Privileges

You need the appropriate database privileges to allow the Oracle WebLogic Server transaction manager to query for transaction state information and issue the appropriate commands, such as commit and rollback, during recovery of in-flight transactions after a WebLogic Server container crash. To configure the SOA schemas for transactional recovery privileges:

1. Log on to sqlplus as a user with sysdba privileges. For example:

sqlplus as sysdba

2. Enter the following commands:

SQL Grant select on sys.dba_pending_transactions to soa_schema_prefix_ soainfra; Grant succeeded. SQL Grant force any transaction to soa_schema_prefix_soainfra; Grant succeeded. SQL

2.1.4 Backing Up the Database

After you have loaded the metadata repository in your database, you should make a backup. Backing up the database is for the explicit purpose of quick recovery from any issue that may occur in the further steps. You can choose to use your backup strategy for the database for this purpose or simply take a backup using OS tools or RMAN for this purpose. It is recommended to use Oracle Recovery Manager for the database, particularly if the database was created using Oracle ASM. If possible, a cold backup using operating system tools such as tar can also be performed. Note: This will auto-select Metadata Services as well. Note: These privileges should be granted to the owner of the soainfra schema, as determined by the RCU operations. 2-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

2.2 Network

This section covers the following topics: ■ Section 2.2.1, Virtual Server Names ■ Section 2.2.2, Load Balancers ■ Section 2.2.3, IPs and Virtual IPs ■ Section 2.2.4, Firewalls and Ports

2.2.1 Virtual Server Names

The WebCenter enterprise topology uses the following virtual server names: ■ Section 2.2.1.1, wc.mycompany.com ■ Section 2.2.1.2, admin.mycompany.com ■ Section 2.2.1.3, wcinternal.mycompany.com Ensure that the virtual server names are associated with IP addresses and are part of your DNS. The nodes running Oracle Fusion Middleware must be able to resolve these virtual server names.

2.2.1.1 wc.mycompany.com

wc.mycompany.com is a virtual server name that acts as the access point for all HTTP traffic to the runtime SOA and WebCenter components, such as soa-infra, workflow, and B2B. Traffic to SSL is configured. Clients access this service using the address wc.mycompany.com:443. This virtual server is defined on the load balancer.

2.2.1.2 admin.mycompany.com

admin.mycompany.com is a virtual server name that acts as the access point for all internal HTTP traffic that is directed to administration services such as WebLogic Administration Server Console and Oracle Enterprise Manager. The incoming traffic from clients is not SSL-enabled. Clients access this service using the address admin.mycompany.com:80 and the requests are forwarded to port 7777 on WEBHOST1 and WEBHOST2. This virtual server is defined on the load balancer.

2.2.1.3 wcinternal.mycompany.com

wcinternal.mycompany.com is a virtual server name used for internal invocations like callbacks and internal access to services. This url is not exposed to the internet and is only accessible from the intranet. The incoming traffic from clients is not SSL-enabled. Clients access this service using the address wcinternal.mycompany.com:80 and the requests are forwarded to port 7777 on WEBHOST1 and WEBHOST2. This virtual server is defined on the load balancer.

2.2.2 Load Balancers

This enterprise topology uses an external load balancer. For more information on load balancers, see Section 1.5.2, Web Tier.