| Oracle® Retail Service Backbone Installation Guide Release 15.0.2 E90691-01 |
|
 Previous |
 Next |
Before you begin installation, check to be sure that you have the most recent version of this installation guide. Oracle Retail installation guides are available on the Oracle Technology Network.
Oracle Service Bus (OSB) supports 3 types of topologies: Admin-only, Admin + Managed Server and Cluster. The first two topologies are non-clustered topologies which are not high-available, therefore we recommend using Cluster topology and this document describes how to configure a sample cluster topology for RSB applications.
This section describes step-by-step process of creating and configuring an OSB domain using the configuration wizard. In this configuration, there are following servers:
One Admin Server
Three Managed Servers: rsb_server1, rsb_server2 and rsb_http_proxy.
Cluster: The cluster consists of rsb_server1 and rsb_server2 as managed servers. OSB features are deployed on this cluster. Also, rsb_server1 hosts the singleton resources of OSB.
Managed server rsb_http_proxy acts as the proxy server of the cluster. It does not have OSB code installed on it.
Perform the following steps to create a new WebLogic domain:
Run <WLS_HOME>/wlsserver/common/bin/config.sh.
Select Create a new Domain. Click Next.
Select Oracle Service Bus -12.2.1.2 [osb] option as shown, this will select other required options for OSB like EM, OWSM, JRF etc. Click Next.
Select Application Location and click Next.
Enter Name (Username) and User password for the domain. Please note down the username and password. These are required again in the compilation phase of RSB.
Select domain mode option as production and point to latest jdk location. Click Next.
Select RCU Data option and enter database details like driver, hostname, service, port, schema owner and password. The schema must be created already using the RCU tool. Then click on Get RCU Configuration button to get the RCU data for RSB. If connection result logs are OK, then click Next.
This screen shows all RCU schemas for RSB. Select all schemas by clicking on Component Schema Label and click Next.
Here all the schemas will be tested and corresponding data sources will be created in domain. When all statuses are green, click Next.
Select the options for creating AdminServer, Node Manager, Managed Servers and Cluster. Click Next.
Enter Admin Server details, Listen address will be IP address and enter valid Listen port. If you are using SSL, you can enable SSL in this step and specify the SSL port.
Enter Node Manager details like select Per Domain Default Location and provide Node Manager Credentials same as weblogic credentials. Click Next.
Enter details of all managed servers. If you are using SSL, you can enable the SSL in this step and specify the SSL port. Click Next.
|
Note: Oracle recommends to disable SSLv3 in all products. We recommend to use TLSv1.2 protocol. WebLogic server can be configured to use TLSv1.2 protocol by adding the following line in the setDomainEnv.sh. Restart the server after making the change.JAVA_OPTIONS=" $JAVA_OPTIONS -DwebLogic.security.SSL.minimumProtocolVersion=TLSv1.2" |
Enter the cluster name.
Add managed servers to the cluster. Notice that the proxy server, rsb_http_proxy, is not added to the cluster because we need that server as the HTTP proxy of the cluster.
Enter HTTP Proxy details.
Do not modify coherence cluster details keep it as is and Click Next.
Configure Machine details. Click Unix Machine and specify the Name, Node Manager hostname and port. Click Next.
Add servers to the machine. Add all the servers.
From the Configuration Summary page, click Create.
Domain creation confirmation page
The following screen appears after successful domain creation. Click Finish.
Grant required permission for WebLogic to access the credential store. Edit the <wlsHome>/wlserver/server/lib/weblogic.policy file and add the following permission, after replacing <domain-home> with the correct value.
grant codeBase "file:<domain-home>/-" {
permission java.security.AllPermission;
permission oracle.security.jps.service.credstore.CredentialAccessPermission "credstoressp.credstore", "read,write,update,delete";
permission oracle.security.jps.service.credstore.CredentialAccessPermission "credstoressp.credstore.*", "read,write,update,delete";
};
Edit the DOMAIN-HOME/bin/setDomainEnv.sh to add the max and min memory requirement for the servers. It is recommended to use 2GB or more for max memory.
USER_MEM_ARGS="-Xms1024m -Xmx2048m -XX:MaxPermSize=1024m"
If NodeManager is used to control the servers in the cluster, edit WL_HOME/common/nodemanager/nodemanager.properties file to change the StartScriptEnabled property to true and make sure the StartScriptName property is set to startWebLogic.sh. Below is a sample from the file:
StartScriptName=startWebLogic.sh
StartScriptEnabled=true
If you are using https (for Policy A), you will have to configure the following:
|
Note: For additional information on configuring Policy A or Policy B, see the Oracle Retail Service Backbone Security Guide. |
Enable https port for AdminServer, Http Proxy Server and all managed servers. Specify the Listen Address. The Listen Address must match the CN entry of the server certificate. Sometimes the CN entry of the server certificate is the fully qualified name (for example, rsbhost.example.com) instead of the short hostname (for example, rsbhost). If the entries do not match, the security configurations will not work.
Enable secure replication. Enable the Secure Replication Enabled option available in Environment --> Clusters --> <cluster name> --> Configuration --> Replication
Set the Frontend Hostname for the cluster. This should match the CN entry of the certificate. Environment --> Clusters --> <cluster name> --> Configuration --> HTTP
Enable WebLogic plug-in. Check WebLogic Plug-In Enabled checkbox in Environment --> Clusters --> <cluster name> --> Configuration --> General --> Advanced. After the change, Save, Activate Changes and restart the Admin Server.
