Oracle Portal Enterprise Deployment Guide: 11.1.1.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Enterprise Deployment Overview........................................................ 1 Terminology .................................................................................... 2 Benefits of Oracle Recommendations............................................. 4 Built-in Security ............................................................................... 4 High Availability.....................................................
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 About the Node Manager .............................................................. 57 Enabling Host Name Verification for Node Manager - APPHOST157 Starting the Node Manager on APPHOST1 .................................. 61 Enabling Host Name Verification for Node Manager - APPHOST262 Starting the Node Manager on APPHOST2 .................................. 66 Install and Configure the Web Tier.........................................
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Enterprise Deployment Overview What is an Enterprise Deployment? An enterprise deployment is an Oracle best practices blueprint based on proven Oracle high-availability and security technologies and recommendations for Oracle Fusion Middleware.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Terminology Table 1-1 provides definitions for some of the terms that define the architecture of an Oracle Fusion Middleware environment: Table 1-1 Oracle Fusion Middleware Architecture Terminology Term Definition Oracle Base Oracle Mount point, all binaries and configuration information are in relation to this mount point.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 domains. Oracle instance An Oracle instance contains one or more system components, such as Oracle Web Cache, Oracle HTTP Server, or Oracle Internet Directory. The system components in an Oracle instance must reside on the same machine. An Oracle instance directory contains updatable files, such as configuration files, log files, and temporary files.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Control is a Web browser-based, graphical user interface that you can use to monitor and administer an Oracle Fusion Middleware farm. An Oracle Fusion Middleware farm is a collection of components managed by Fusion Middleware Control. It can contain a WebLogic Server domain, one or more Managed Servers and the Oracle Fusion Middleware system components that are installed, configured, and running in the domain.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 • Components are separated between DMZs on the Web Tier, application tier, and the directory tier. • Direct communication between two firewalls at any one time is prohibited. • If a communication begins in one firewall zone, it must end in the next firewall zone. • Oracle Internet Directory is isolated in the directory tier DMZ. • Identity Management components are in the DMZ.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 The Enterprise Deployment Reference Topology The instructions and diagrams in this guide describe a reference topology, to which variations may be applied. This guide provides instructions for creating the Application and Web Server tiers of the myPortal company architecture, distributing the software components into the Enterprise Deployment architecture depicted below.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Understanding the Web Tier The Web Tier is in the DMZ Public Zone. Web Cache and HTTP Servers are deployed in the Web Tier. Web Cache is the first point on entry into the site, it performs two functions; Its primary function is to serve static web content from its cache, much faster than could be achieved by the Oracle HTTP Servers alone.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 WLS_PORTAL and WLS_PORTAL1 are clustered together and mod_wl_ohs will load balance requests amongst them. When a request needs authorization the Oracle HTTP Server will intercept the request and if necessary redirect the browser to the Oracle Single Sign Server(s) for authentication. The Oracle Web Caches are clustered together to provide a global cache which is consistent across nodes.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Installing an Enterprise deployment is complex; to simplify this and to provide intermediary checkpoints this guide uses the following approach: 1. Install Oracle Portal on APPHOST1. 2. Fully configure APPHOST1 to support access via the load balancer. 3. Install APPHOST2. 4. Fully configure APPHOST2 to support access via the load balancer. The above steps include configuring Oracle Web Cache and the Oracle HTTP server.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Oracle Portal Oracle Portal, Forms, Reports and Discoverer CD (11.1.1.2.0) Repository Creation Utility Oracle Fusion Middleware Repository Creation Utility CD (11.1.1.2.0) Oracle Web Tier Oracle Fusion Middleware Web Tier and Utilities CD (11.1.1.2.0) Third Party Components of Enterprise Deployments load balancer This enterprise topology uses an external load balancer.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 • Ability to detect node failures and immediately stop routing traffic to the failed node. • Resource monitoring / port monitoring / process failure detection: The load balancer must be able to detect service and node failures (through notification or some other means) and to stop directing non-Oracle Net traffic to the failed node. If your external load balancer has the ability to automatically detect failures, you should use it.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 http://download.oracle.com/docs/cd/B14099_19/core.1012/b13998/security.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 • FW0 refers to the outermost firewall. • FW1 refers to the firewall between the Web Tier and the application tier. • FW2 refers to the firewall between the application tier and the directory tier.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Database Access FW2 1521 SQLNET In/out WC Invalidation FW3 Requests 9401 HTTP Out Node Manager NA TCP/IP NA Database sends invalidation requests to loadbalancer. NA Assumptions For the remainder of this document the following assumptions have been made, when building an Enterprise deployment, the values listed below (especially usernames/passwords) should be changed.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Single Sign On SSOHOST 7777 Single Sign on Listening Port.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 11. Create a Database Wallet. 12. Register Portal with Oracle Single Sign On. 13. Configure Host Assertion in Oracle WebLogic Server. 14. Install Oracle WebLogic Server on APPHOST2 15. Install and perform initial configuration of Oracle Portal on APPHOST2 16. Copy Files from APPHOST1 to APPHOST2 17. Introduce APPHOST2 to Web Cache. 18. Cluster Web Cache Instances on APPHOST1 an APPHOST2 19.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 • A virtual IP address (VIP1) that listens for requests to myPortal.mycompany.com on port 443 (an HTTPS listening port), and balances them to the application tier Oracle Web Caches running on WEBHOST1 and WEBHOST2 port 7777 (an HTTP listening port). You must configure the load balancing router to perform protocol conversion. • The virtual IP address VIP1 listens for requests to myPortal.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 To monitor port 7777, use the following URL in the load balancing router configuration: hostname:port/_oracle_http_server_Web Cache_static_.html For example: http://webhost1.mycompany.com:7777/_oracle_http_server_Web Cache_static_.html If the load balancing router receives a response from this URL, then the OracleAS Web Cache instance is running.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 The sqlnet.ora file must be updated to prevent connection time outs related to the load balancing router and firewall. See Section 4.1.5, "Configuring the Time out Value in the sqlnet.ora File". Summary To summarize, the load balancer requires the following configuration: Configuring the Database for Enterprise Deployments The myPortal.mycompany.com application requires a database to store its information in.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 SQL>select version from sys.product_component_version where product like 'Oracle%'; Real Application Clusters The database used to store the metadata repository should be highly available in its own right, for maximum availability Oracle recommends the use of an Oracle Real Application Clusters (RAC) database. Ideally the database will use Oracle ASM for the storage of data, however this is not necessary.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 • When the installer is run, select the Configure Automatic Storage Management option in the Select Configuration page to create a separate Automatic Storage Management home. Oracle Real Application Clusters • For 10g Release 2 (10.2), see Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide. • For 11g Release 1 (11.1), see Oracle Real Application Clusters Installation Guide.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 sga_target 512Mb sga_max_size 800Mb pga_aggregate_target 100Mb Database Services Oracle recommends using the Oracle Enterprise Manager Cluster Managed Services Page to create database services that client applications will use to connect to the database.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Note: For more information about the SRVCTL command, see the Oracle Real Application Clusters Administration and Deployment Guide. If you already have a service created in the database, make sure that it is enabled for highavailability notifications and configured with the proper server-side Transparent Application Failover (TAF) settings.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Create Repository Select Create Click Next.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 All other components should be unchecked. Click Next Check PreRequisites Click OK when the pre-requisites have been validated. Schema Passwords Enter passwords for each of the portal schemas or use the same password for all schemas. Click Next Map Tablespaces Click Next to accept the defaults Create Tablespaces Select Yes to allow the RCU to create any missing tablespaces.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 On Windows issue the command: server103_win32.exe Screen Action Welcome Click Next. Choose Middleware Home Directory Select Create a New Middleware Home Enter a value for the Middleware Home directory. This will be known henceforth MW_HOME. For example /u01/app/oracle/product/FMW Click Next. Register for Security Updates Choose whether or not to receive security updates from Oracle Support.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 On Windows issue the command: setup.exe Note: Before starting the install ensure that the following environment variables (UNIX) are not set: • LD_ASSUME_KERNEL • ORACLE_BASE • LD_LIBRARY_PATH Screen Action Welcome Click Next. Installation Type Install Software and Configure Click Next. Prerequisite Checks Once all checks have passed.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Home. This will be known henceforth as ORACLE_INSTANCE For example /u01/app/oracle/admin/PortalDomain/Portal1 Oracle Instance Name: Portal1 Click Next Select Domain Select Create New Domain and enter the values: User Name: Name of user to log into the WebLogic domain. User Password: Password for the domain.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Specify Schema Specify the following values: Database Connect String in the format: racnode1-vip:ListenerPort:racnode2vip:ListenerPort@mydb.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Test URL Result Test Portal http://APPHOST1.mycompany.com:7777/portal/pls/portal/ Portal Home Page Displayed Test Portal Login http://myPortal.mycompany.com/portal/pls/portal Log into Portal using the user account orcladmin Test WebLogic Admin Console http://APPHOST1.mycompany.com:7001/console Login using admin credentials specified above Test EM http://APPHOST1.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Restarting the Administration Server will encrypt the values in the above file, for that reason it is recommended that the Administration Server be restarted on each node, which can host it. The Administration Server is stopped using the script stopWebLogic.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Configure Virtual Hosts In order for Portal to work with the load balancer two virtual hosts need to be created. Create a file called virtual_hosts.conf in ORACLE_INSTANCE/config/OHS/ohs1/moduleconf Add the following entries to the file: NameVirtualHost *:7778 ServerName https://myPortal.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Select Create Site Enter the following information to add the following site: Site: myPortal.mycompany.com Host Name myPortal.mycompany.com Port 443 Default site Yes Site Wide Compression Yes Site Alias – Host Name myPortal.mycompany.com Site Alias - Port 7777 Site Alias – Host Name myPortal.mycompany.com Site Alias - Port 80 Leave everything else at the default. and then click Submit.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Click OK to store the site. Remove all other site entries from the list by clicking on each entry and then clicking the Delete button. Ensure that the site APPHOST1.mycompany.com:443 appears first in the list of site to server mappings. Click Apply to save the changes. Enable Session Binding The session binding feature in OracleAS Web Cache is used to bind user sessions to a given origin server to maintain state for a period of time.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 This is achieved by: In the Navigator window, expand the Web Tier tree. Click on the component wc1 From the drop down list at the top of the page select Administration – Passwords Enter a new invalidation password and administration passwords, confirm and click Apply Restart Web Tier (OHS and Web Cache) Having made the above changes the Web Tier components need to be restarted.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 (**) Note: owa_util.print_cgi_env needs to be enabled by: Adding: PlsqlExclusionList "#None#" in the portal_dads.conf. file located in DOM_HOME/config/fmwconfig/servers/WLS_PORTAL/applications/portal/configuration/ portal_dads.conf From the database servers check that it is possible to contact the Webcache page invalidator. From each database host issue the command: telnet myPortal.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 WebCache host Enter the DNS name of the load balancer for example myportal.mycompany.com Invalidation Port Enter the Portal Invalidation port as configured at the load balancer e.g. 9401 Invalidation User Name invalidator Invalidation Password Password for the above account. Click Apply to start the rewire.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 In the Advanced Properties section add the following information: UsePort Select the internal loopback port number for example: 7777 Use Scheme http HTTPS Ports 443 Click Apply to save the settings. Restart the WebLogic Managed Server from the WebLogic admin console: Connect to the console using the URL: http://APPHOST1.mycompany.com:7001/console Select Servers, and then select the Control tab.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Find the certificate in the various certificate stores (the location will depend on where you requested it to be stored when you imported the certificate when you accessed the site). Highlight the certificate Click on Export The Export wizard will be started. Click Next Select DER encoded binary X.509 (.CER), which is the default. Click Next Specify a file name Click Next Click Finish. Import Certificate into database wallet.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Select “Select a file that contains the certificate” and Click OK Select the certificate file selected above and click import. Select Wallet and Save As Select a location for the wallet for example $ORACLE_BASE/admin/DB_NAME/wallet Repeat for successive nodes. Identify the Wallet to Portal Now that the certificate is stored inside the database wallet, the location of the wallet has to be stored within the Portal repository.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 5. Execute ORACLE_HOME/sso/bin/ssoreg.sh (ssoreg.bat on Windows) with the following parameters -site_name myPortal.mycompany.com -mod_osso_URL https://myPortal.mycompany.com -config_mod_osso TRUE -oracle_home_path ORACLE_HOME -config_file /tmp/osso.conf -admin_info cn=orcladmin -virtualhost -remote_midtier 6. Copy /tmp/osso.conf to the Portal mid-tier home location $ORACLE_INSTANCE/config/OHS/ohs1 7.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Because the Oracle HTTP Server acts as a proxy for WebLogic, by default certain CGI environment variables are not passed through to WebLogic. These include the host and port. WebLogic needs to be told that it is using a virtual site name and port so that it can generate internal URLs appropriately. Log into the WebLogic administration console using the following URL http://apphost1.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Click Yes to shutdown the managed server. Once the server is shutdown Select the box next to WLS_PORTAL Click on Start Click Yes to start the managed server Validate Configuration In order to validate the configuration the following tests should be performed: Test URL Result Test load balancer SSL Termination https://myPortal.mycompany.com/portal/pls/portal/ owa_util.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Sometimes after performing the above steps a WWC-0000 message is displayed along with error text which starts something like: @ ;i=pls%2Forasso%2Forasso.wwsso_app_admin.fapp_process_login%3Fp_app_id%3D; Accept=text/html Accept-Charset=ISO-8859-1,utf-8;q=0.7,*;q=0.7….. This error text indicates that the load balancers certificate is not correctly stored in the database wallet and identified correctly to Portal.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Security Updates desired enter an email address and the appropriate Oracle Support Password. Click Next Choose Install Type Select Typical Click Next. Choose Product Installation Directories Click Next. Installation Summary Click Next. Installation Complete Uncheck runQuickstart and Click Done.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Installation Type Install Software and Configure Click Next. Prerequisite Checks Once all checks have passed Specify Installation Location Enter the following Values: Click Next Middleware Home: Enter the value for MW_HOME for example: /u01/app/oracle/product/FMW Oracle Home: Enter the installation directory for Portal. ** Note this will be placed under the MW_HOME directory.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Port: Port Admin Server is using for example: 7001 User Name: Admin Server administrator account name. Password: Admin Server Password Click Next Configure Components At a minimum ensure that the following values are checked (Note this should be the same list as that selected for APPHOST1: Server Components – Oracle Portal Click Next.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Configure application tier on APPHOST2 Introduce WLS_PORTAL1 to Oracle HTTP Server on APPHOST1 Now that the managed server WLS_PORTAL1is up and running, the Oracle HTTP Server (OHS) on APPHOST1 needs to be told of its existence, so that it can route requests to it. Update Oracle HTTP Server configuration to be cluster aware.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 to: SetHandler WebLogic-handler WebLogicCluster apphost1.mycompany.com:9001,apphost2.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 osso.conf ORACLE_INSTANCE/config/OHS/o hs1 ORACLE_INSTANCE/config /OHS/ohs1 sqlnet.ora ORACLE_INSTANCE/config/ ORACLE_INSTANCE/config / Configure Virtual Hosts Edit the file ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/virtual_hosts.conf on APPHOST2 Remove the virtual Host entry for APPHOST1 and add one for APPHOST2 so that the file looks like: NameVirtualHost *:7778 ServerName https://myPortal.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Update Instance Paths Two of the copied files have hard coded entries for the above directories; these files need amending to reflect the paths above. Edit the files: portal_cache.conf – Change PlsqlCacheDirectory portal_plsql.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Log into the Enterprise Manager Administration Console Log into the Enterprise Manager Console using the URL: http://apphost1.mycompany.com:7001/em Default User Name and Password are the same as the domain username and password entered during the installation. Change Web Cache Passwords The Web Cache invalidation and admin passwords are randomly generated, however they are required later.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Port 7778 Capacity 100 Protocol HTTP Failover Threshold 5 Ping URL / Ping Frequency 10 And select OK to save the changes. Select Apply to save the changes. Add Origin Server Site to Server Mapping In the Navigator window, expand the Web Tier tree.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Click on Add The Web Cache from APPHOST2 will automatically be added. Select Apply to apply the changes Click on the newly created Web Cache entry (be sure not to click on the URL part of it) Click on Synchronize to copy the configuration to the Web Cache on APPHOST2. Click Yes when prompted to confirm that you wish you perform the operation.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Test load balancer Termination https://myPortal.mycompany.com/portal/pls/ portal/owa_util.print_cgi_env REQUEST_PROT OCOL value of HTTPS Setting up Node Manager This section describes how to configure Node Manager per the EDG recommendations. Oracle Fusion Middleware EDG recommends using host name verification for the communications between Node Manager and the Administration Server.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Step 3: Creating a Trust Keystore Using the keytool Utility Step 4: Configuring Node Manager to Use the Custom Keystores Generating Self-Signed Certificates Using the utils.CertGen Utility Follow these steps to create self-signed certificates on APPHOST1.mycompany.com. These certificates should be created using the network name/alias.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Syntax: java utils.CertGen [export | domestic] [hostname] Examples: APPHOST1> java utils.CertGen welcome1 APPHOST1_cert APPHOST1_key domestic APPHOST1.mycompany.com Creating an Identity Keystore Using the utils.ImportPrivateKey Utility Follow these steps to create an Identity Keystore on APPHOST1.mycompany.com. 1.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 1. Create a new trust keystore called appTrustKeyStore using the keytool utility: APPHOST1> keytool -keystore appTrustKeyStore.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 certificates generated by utils.CertGen tool. Import CertGenCA.der using the following syntax: keytool -import -v -noprompt -trustcacerts -alias -file -keystore Configuring Node Manager to Use the Custom Keystores To configure the Node Manager to use the custom keystores, add the following lines to the end of the nodemanager.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 APPHOST1> ./startNodeManager.sh Enabling Host Name Verification for Node Manager - APPHOST2 Perform these steps to set up SSL for communication between the Node Manager and the Administration Server: Step 1: Generating Self-Signed Certificates Using the utils.CertGen Utility Step 2: Creating an Identity Keystore Using the "utils.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 APPHOST2> cd certs 4. Run the utils.CertGen tool from the user-defined directory to create the certificates for APPHOST2. Syntax: java utils.CertGen [export | domestic] [hostname] Examples: APPHOST2> java utils.CertGen welcome1 APPHOST2_cert APPHOST2_key domestic APPHOST2.mycompany.com Creating an Identity Keystore Using the "utils.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 1. Create a new trust keystore called appTrustKeyStore using the keytool utility: APPHOST2>keytool -keystore appTrustKeyStore.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 sign all certificates generated by utils.CertGen tool. Import CertGenCA.der using the following syntax: keytool -import -v -noprompt -trustcacerts -alias -file -keystore Configuring Node Manager to Use the Custom Keystores Follow these steps to configure the Node Manager to use the custom keystores. 1. Add the following lines to the end of the nodemanager.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Starting the Node Manager on APPHOST2 Run these commands to start Node Manager on APPHOST2: APPHOST2> cd ORACLE_BASE/product/FMW/wlserver_10.3/server/bin APPHOST2> ./startNodeManager.sh Install and Configure the Web Tier At this point a highly available Portal configuration is now available.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Prerequisite Checks Click Next. Specify Installation Location Specify the following values: Configure Components Select: Fusion Middleware Home Location (Installation Location) for example: /u01/app/oracle/product/FMW/web Oracle HTTP Server Oracle Web Cache Associate Selected Components with WebLogic Domain Click Next.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 OHS Component Name: http1 WebCache Component Name: Web Cache1 Click Next. WebCache Administrator Password Specify a value for the Webcache administrator password. Confirm the password and click Next Configure Ports In HA implementations whilst not mandatory it makes life simpler if all of the ports used by the various components are synchronized across hosts.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 #INVALIDATION port no for WebCache component Web Cache Invalidation Port = 9401 [OPMN] #Process Manager Local port no Oracle Process Manager Local Port No = 1880 You can find a sample staticports.ini file on installation Disk1 in the stage/Response directory. Click Next. Specify Security Updates Choose whether or not to receive security updates from Oracle Support.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 The Web Tier needs certain files such as images and configuration information to be able to display the Portal pages correctly. Copy the following directories from APPHOST1 to WEBHOST2 APPHOST1 WEBHOST1 ORACLE_HOME/portal ORACLE_HOME/portal ORACLE_INSTANCE/config/OHS/ohs1 /moduleconf ORACLE_INSTANCE/config/OHS/http1 /moduleconf ORACLE_INSTANCE/config/OHS/ohs1 /osso.conf ORACLE_INSTANCE/config/OHS/http1 /osso.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Log into the Enterprise Manager Administration Console Log into the Enterprise Manager Console using the URL: http://apphost1.mycompany.com:7001/em Default User Name and Password are the same as the domain username and password entered during the installation. Create Origin Server In the Navigator window, expand the Web Tier tree.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Click on the component wc1 (make sure it is the one associated with APPHOST1) From the drop down list at the top of the page select Administration – Sites In the Site to Server Mapping section click on the Host:port myPortal.mycompany.com:443 Click on Edit Select the origin server WEBHOST1.mycompany.com:7778 and move it to the selected Origin servers list. Click OK to save the changes. Select Apply to save the changes.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Click Apply to Apply the new configuration Restart Web Tier (OHS and Web Cache) Having made the above changes the Web Tier components need to be restarted.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Install Oracle HTTP Server on Webhost2 Start the Oracle Universal Installer as follows: On UNIX, issue this command: runInstaller On Windows, double-click setup.exe Before Starting the install ensure that the following environments are not set. • LD_ASSUME_KERNEL • ORACLE_INSTANCE Screen Action Welcome Click Next. Select Installation Type Select Install and Configure. Prerequisite Checks Click Next.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 example: wladmin.mycompany.com Domain port Number (WebLogic Administration server Port) for example: 7001 Username (WebLogic Admin Server user) for example: WebLogic Password (Password for above account) Click Next. Specify Component Details Specify the following values: Instance Home Location: /u01/app/oracle/admin/web1 AS Instance Name: web2 OHS Component Name: http2 WebCache Component Name: Web Cache2 Click Next.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 UNIX installations only. Configuration Multiple configuration assistants are launched in succession; this process can be lengthy. When it completes, click Next and the Installation Complete screen appears. Click Finish to confirm your choice to exit. Validate the Installation Once the installation is completed check that it is possible to access the Oracle HTTP Server home page using the following URL: http://webhost1.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Remove the Virtual Host entry for APPHOST1 and add an entry for WEBHOST2. The resulting file should look like: NameVirtualHost *:7778 ServerName https://myPortal.mycompany.com:443 RewriteEngine On RewriteOptions inherit UseCanonicalName On ServerName webhost2.mycompany.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Port 7778 Capacity 100 Protocol HTTP Failover Threshold 5 Ping URL / Ping Frequency 10 Select OK to save the changes. Select Apply to save the changes. Add Origin Server Site to Server Mapping In the Navigator window, expand the Web Tier tree. Click on the component Web Cache1 From the drop down list at the top of the page select Administration – Sites In the Site to Server Mapping section click on the Host:port myPortal.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 From the drop down list at the top of the page select Administration – Cluster Click on Add The Web Cache from WEBHOST2 will automatically be added. Select Apply to apply the changes Click on the newly created Web Cache entry (be sure not to click on the URL part of it) Click on Synchronize to copy the configuration to the Web Cache on WEBHOST2. Click Yes when prompted to confirm that you wish you perform the operation.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Note: Prior to issuing these commands ensure that the environment variable ORACLE_INSTANCE is set to the value that was entered during the install above. Note: For Validation purposes only restart the Web Tier on WEBHOST2. Leave the others shutdown. Once validation is complete, restart the Web Tier components on WEBHOST1.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 In the Navigator window, expand the Web Tier tree. Click on the component Web Cache1 From the drop down list at the top of the page select Administration – Sites In the Site to Server Mapping section click on the Host:port myPortal.mycompany.com:443 Click on Edit Select the origin servers APPHOST1.mycompany.com:7778 and APPHOST1.mycompany.com:7778 and remove them from the selected Origin servers list. Click OK to save the changes.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 Click on Synchronize to copy the configuration to the Web Cache on WEBHOST2. Click Yes when prompted to confirm that you wish you perform the operation.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 opmnctl deletecomponent -componentName wc1 -adminHost APPHOST1 -adminPort 7001 adminUsername WebLogic Enter the WebLogic Administration Password when requested. Issue the following command to remove the Oracle HTTP Server: opmnctl deletecomponent -componentName ohs1 -adminHost APPHOST1 -adminPort 7001 adminUsername WebLogic Enter the WebLogic Administration Password when requested.
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2 References 1. Oracle Maximum Availability Architecture Web site http://www.otn.oracle.
White Paper Title November 2009 Author: Michael Rhys Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Copyright © 2009, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice.
