Configuring a proxy server for SSL or HTTPS - example

You can configure a proxy server for WebLogic. For general guideline on how to configure a Web server, refer to the WebLogic example provided in this topic.

About this task

For information about how to configure a proxy server for WebSphere® and JBoss, refer to the documentation pertaining to those products.

Before you begin: The Oracle WebLogic 10.3 installation does not include the Apache HTTP server plug-ins. You must download these plug-ins in a separate compressed file from the Oracle download and support sites.

To configure a proxy server for SSL or HTTPS using the Apache HTTP Server and Oracle WebLogic:

Procedure

Install and run Sterling Selling and Fulfillment Foundation on the application servers.
Copy the appropriate plug-in to the /etc/apache2/modules directory.
For WebLogic 12.1.2, this is:
```
<WL_HOME>/wlserver_12.1.2/server/plugin/<OS>/<processor type>
```
Here, <WL_HOME> refers to the WebLogic installation directory. Example: /wls1212Linux/wlserver_12.1.2/server/plugin/linux/x86_64
- For i686, copy the WLS plug-in.
- For x86_64, copy the 64-bit plug-in. The 64-bit plug-in must be requested from Oracle Customer Service.
- Ensure the plugin is executable.

To enable the WebLogic plug-in for load-balancing using HTTP or HTTPS, modify the httpd.conf file and add the following. To enable an SSL, add include conf.d/ssl.conf as instructed by Apache. By default, RHAS3 has Include conf.d/*, which includes ssl.conf.

   LoadModule weblogic_module /etc/apache2/modules/<appserver_plugin_file>

For an HTTP proxy, outside any VirtualHost, add the following section. The context_root value is the context_root for the web application being proxied:

   <IfModule mod_weblogic.c>   
           WebLogicCluster
   <managed_server1_hostname/IP_address>,<managed_server2_hostname/IP_address>
           DynamicServerList OFF
           Debug ON
           IdemPotent OFF
   </IfModule>
   <Location /context_root>
           SetHandler weblogic-handler 
   </Location>

Modify the ssl.conf file and add the following lines to the <VirtualHost _default_:443> section. The context_root value is the context_root for the web application being proxied.

   <IfModule mod_weblogic.c>
             WebLogicCluster
   <managed_server1_hostname/IP_address>,<managed_server2_hostname/IP_address>
             DynamicServerList OFF
             Debug ON
             IdemPotent OFF
   </IfModule>
   <Location /context_root>
               SetHandler weblogic-handler
   </Location>

Create security or SSL certificate, if necessary. If you do not have a CA-signed certificate, you can get one from the Certificate Authority companies such as VeriSign.
Restart Apache, and verify access with any browser.
Continue and complete steps 7-10 if using an RCP application only.
Copy the security certificate to the <RCP_EXTENSIONS_FOLDER>/truststore directory.
Build the RCP client.
Edit the locations.ycfg file and modify the protocol, server, and port attributes of the Config element. Ensure that these attributes point to the proxy.
Start the client.