Application Server Settings Installation Panels
Each environment option requires to fill in different sets of details to function properly.
Oracle WebLogic deployment details
This section describes Oracle WebLogic deployment options. Both Oracle WebLogic 10.3 and Oracle WebLogic 11g are supported.
Invoke Oracle WebLogic installation by selecting WebLogic deployment option in the following installer screen:
Page 29
Oracle WebLogic deployment details
Note
WL_HOME refers to the WebLogic directory or Oracle Middleware Home.
WL_SERVER_HOME refers to the WebLogic server installation directory. The default value is
WL_HOMEwlserver_10.3 . If you want to use direct deployment from Oracle Service Registry installer, you must
provide this path. It is used to locate WebLogic deploy tool JAR files. REGISTRY_HOME
refers to the Oracle Service Registry installation directory. It must be placed under Oracle Middleware Home in case Domain Configuration.
REGISTRY_DEPLOY_DIR refers to the application server directory where the Oracle Service Registry distribution
is unpacked. The default path is WL_HOMEuser_projectsdomains DOMAIN_NAME servers SERVER_NAME tmp_WL_user REGISTRY_CONTEXT RANDOM_NAME public
on both Oracle WebLogic 10.3 and 11g. Oracle Service Registry Setup tool uses this directory to locate registry configuration files.
The next installation screen requests a method deployment.
Page 30
Oracle WebLogic deployment details
Domain Configuration is supported for Weblogic 11g only. Upon completion, you must run the Oracle WebLogic Configuration Wizard to create WebLogic domains. See more at
Creating WebLogic Domains Using the Configuration Wizard
. If you select Oracle Weblogic 10.3 on the previous page, Domain Configuration will not be shown.
Page 31
Oracle WebLogic deployment details
The next installation screen requests URL components hostname, port, ssl port, context that Oracle Service Registry uses in its web user interface. If you use proxy or load-balancer, the URL components should point to it. The registry
administrator can change the URL later in Registry Management. If the URL is incorrect the web UI cannot be accessed until the URL value is corrected in the configuration files. In the case of domain configuration, the hostname and port
values in this page must be the same as the values set when running the Configuration tools to create the weblogic domain.
Page 32
Oracle WebLogic deployment details
If you select Online Server Deployment in the Deployment method page, the following screen opens:
Page 33
Oracle WebLogic deployment details
• Fill-in the first directory to point to the Oracle Weblogic server directory. This directory should contain the deployer
.jar serverlibweblogic.jar inside. •
The second directory is the JAVA_HOME of the Java Virtual Machine JVM to use with the deployer. Both SUN Java and JRockit Java distributed with Oracle WebLogic should work.
• Hostname field indicates the machine you want to deploy to.
• Admin username and password refer to the name and password of the administrator account in your WebLogic
installation. If you want to deploy manually you must specify the location of the Oracle Service Registry .war file. This file is in
REGISTRY_HOMEconfportingweblogicbuild[context_name].war if installation succeeded.
Other required changes to complete the integration: 1.
If you selected Use SSL HTTPS in the installer, import the SSL certificate of the WebLogic server to the Oracle Service Registry configuration.
Use one of the following methods to obtain the WebLogic SSL certificate: •
Use Internet Explorer 6.0 web browser connected to Oracle WebLogic via HTTPS. Select Properties in context menu of the page, button Certificates, tab Details, button Copy to file, and then export certificate in Base
64 encoded X.509 .cer format.
Page 34
Oracle WebLogic deployment details
• Use REGISTRY_HOMEbinsslTool.sh or REGISTRY_HOME\bin\sslTool.bat to get the certificate. Run command:
sslTool serverInfo --url https:HOST:9043 --certFile weblogic.cer This command connects to the specified host and port using HTTPS and stores the server certificate in the
specified file. To import this certificate use the following command:
PStoreTool located in [registry_home]bin PStoreTool.sh add -config [registry_home]confclientconf.xml - certFile [weblogic.cer]
2. Enable SSL in WebLogic if not yet enabled and restart the Oracle WebLogic server.
Deployment should now be complete. The Oracle Service Registry URL is http:[hostname]:[http_port][context]uddiweb
Creating WebLogic Domains Using the Configuration Wizard
This section provides information and examples for some common domain configuration tasks using the Configuration Wizard
Create New Domain with default Managed Server
1. Start the Configuration Wizard in graphical mode.
• On Windows: Start—Programs—BEA Products—Tools—Configuration Wizard or enter
WEBLOGIC_HOMEcommonbinconfig.cmd •
On UNIX: enter WEBLOGIC_HOMEcommonbinconfig.sh 2.
In the Welcome window select Create a new WebLogic domain
Page 35
Create New Domain with default Managed Server
3. In the Select a Domain Source window, select Generate a domain configured automatically to support the
following BEA products
and the Oracle Service Registry check box is selected
Page 36
Create New Domain with default Managed Server
4. In the Specify Domain Name and Location window, enter the name and location for the domain.
Page 37
Create New Domain with default Managed Server
5. In the Configure Administrator Username and Password window, enter a valid username and password, and click
Next. This username is used to boot the Administration Server and connect to it
Page 38
Create New Domain with default Managed Server
6. In the Configure Server Start Mode and JDK window, specify whether to start the server in development mode
or production mode, and select which JDK to use
Page 39
Create New Domain with default Managed Server
7. In the Configure JDBC Data Sources window, fill in the empty Password field to connect to the database successfully
Page 40
Create New Domain with default Managed Server
8. In the Test JDBC Data Sources window, check that the JDBC Data Sources configuration in the previous page is
correct.
Page 41
Create New Domain with default Managed Server
9. In Select Optional Configuration indicate whether you want to change the distribution of your domain across
servers, clusters, and machines
Page 42
Create New Domain with default Managed Server
10. In Configuration Summary, review the values supplied to the configuration and click Create to create the domain
Page 43
Create New Domain with default Managed Server
11. The domain will be created so long as there are no erroneous or conflicting values.
Page 44
Create New Domain with default Managed Server
Extend Existing Domain and Target on an existing Managed Server
1. Start the Configuration Wizard in graphical mode.
• On Windows: Start—Programs—BEA Products—Tools—Configuration Wizard or enter
WEBLOGIC_HOMEcommonbinconfig.cmd •
On UNIX: enter WEBLOGIC_HOMEcommonbinconfig.sh 2.
In the Welcome window, select Extend an existing WebLogic domain
Page 45
Extend Existing Domain and Target on an existing Managed
3. In the Select a WebLogic Domain Directory window, navigate to the domain directory that you want to extend
Page 46
Extend Existing Domain and Target on an existing Managed Server
4. In the Select Extension Source window, you can choose to extend your domain by selecting an Oracle Service
Registry
Page 47
Extend Existing Domain and Target on an existing Managed
5. In the Configure JDBC Data Sources window, fill in the empty Password field to connect to the database successfully
Page 48
Extend Existing Domain and Target on an existing Managed Server
6. In the Test JDBC Data Sources window, check that the JDBC Data Sources configuration in the previous page is
correct.
Page 49
Extend Existing Domain and Target on an existing Managed
7. In Select Optional Configuration, select these options to configure servers, clusters, and machines
Page 50
Extend Existing Domain and Target on an existing Managed Server
Page 51
Extend Existing Domain and Target on an existing Managed
8.
Page 52
Extend Existing Domain and Target on an existing Managed Server
9.
Page 53
Extend Existing Domain and Target on an existing Managed
10.
Page 54
Extend Existing Domain and Target on an existing Managed Server
11.
Page 55
Extend Existing Domain and Target on an existing Managed
12.
Page 56
Extend Existing Domain and Target on an existing Managed Server
13.
14. After configuring these environments you can extend the existing domain.
Page 57
Extend Existing Domain and Target on an existing Managed