Creating a new domain in Weblogic Server

I am using Weblogic 9.2 here. Although the steps are same, the screens may vary in
Weblogic 10x. The following steps are required to create a new domain in the Weblogic.

Use of creating a new domain: Creating new domain help us isolating our applications,
servers, settings and workshop settings from others. This will help us in assigning
multiple servers to multiple project resources with single installation of Weblogic.

1. To create a new domain, goto %BEA_HOME%/weblogic92/common/bin:

2. Then run config.cmd (config.sh incase of Linux versions) file. This will bring the
following screen:

Created by P.V.J. Pavan Kumar

Alternatively, we can also run the same from the Programs > BEA Weblogic > Tools >
configuration wizard to get this screen:

Created by P.V.J. Pavan Kumar

3. Click on Next. Select the option: “Generate a domain configured automatically…”

4. Give the username and password:

Created by P.V.J. Pavan Kumar

5. Select the Development mode on the left side (We can change to production mode,
incase, after creating the domain) and also select the desired JDK version. Suggest to
leave it to Sun JDK.

6. To customize the server settings, click on Yes:

Created by P.V.J. Pavan Kumar

7. Enter the desired port for Weblogic server and choose SSL incase it is needed (these
can be changed after the installation as well):

8. Add for any managed servers and any WL instances that needed to configured:

Created by P.V.J. Pavan Kumar

9. Change the domain summary if needed:

Created by P.V.J. Pavan Kumar

10. Enter the name of the domain. The domain will be created in the directory
%BEA_HOME%\user_projects\domains (by default). Click on Create to create the
domain:

11. Once the domain is created, check the “Start Admin Server” to start the server (OR)
click on “Done” to finish the wizard.

Created by P.V.J. Pavan Kumar

To start the Weblogic domain that we created, use the following navigation:

Start > Programs > BEA Products > User Projects > <domain>_name > Start Admin
Server for Weblogic Server Domain to start the server.

Replace <domain> with the domain name that is given in the previous screens.

Summary:

The whole idea is creating a new domain. For that run the
%BEA_HOME%/weblogic92/common/bin/config.cmd file. Once the wizard starts, it is all
user-friendly steps.

Created by P.V.J. Pavan Kumar

Issues:

1. Getting the following warning when trying to start the Weblogic server:

<WSEE>Warning: JMS queue 'weblogic.wsee.DefaultQueue' is not found, as a result,

Web Service async responses via jms transport is not supported. If the target s
ervice uses JMS transport, the responses will not be able to come back.<JmsQueue
Listener.connect:227>

(OR)

Getting the following exception when tried to send a message to the Weblogic (OSM)
queue:

java.rmi.RemoteException: Error in ejbCreate:; nested exception is:

javax.ejb.CreateException: While trying to lookup 'mslv.oms.oms1.interna
l.jms.ConnectionFactory' didn't find subcontext 'jms'. Resolved 'mslv.oms.oms1.i
nternal'
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(
EJBRuntimeUtils.java:95)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(B
aseEJBObject.java:724)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(B
aseEJBObject.java:681)
at weblogic.ejb.container.internal.BaseEJBObject.preInvoke(BaseEJBObject
.java:220)
at weblogic.ejb.container.internal.StatelessEJBObject.preInvoke(Stateles
sEJBObject.java:64)
Truncated. see log file for complete stacktrace

Cause:

The WSEE JMS server is exclusively used for Webservices. If queue is NOT present,
then the web service async responses via jms transport is not supported. Also, this queue
is used by OSM internally for message communication. So, if we ignore the warning and
try to enqueue a message to this queue, then the above exception is thrown at runtime.

Solution:

The WSEE JMS server is by default provided only with the Workshop installatoin of the
Weblogic. If this is NOT installed, then the WSEE JMS server needs to be installed /
configured manually.

Created by P.V.J. Pavan Kumar

1. Ensure that there are NO messages in the Weblogic queue. If there are any messages,
they might be corrupted. So, atleast have a backup of the Weblogic server before
proceeding further.

2. To install the WSEE JMS server, invoke the Configuration Wizard (by running the
config.cmd from %BEA_HOME%\weblogic92\common\bin directory OR BEA 9.2
Products > Tools > Configuration Wizard) and then choose the second option: Extend
the existing domain.

Created by P.V.J. Pavan Kumar

3. Choose the domain you want to extend:

4. The Configuration Wizard reads the domain information and then displays what is
installed already and what components are not installed. Select the Workshop for
weblogic platform option and then click next to install the Workshop and thereby the
WSEE JMS server.

Created by P.V.J. Pavan Kumar

2. Getting the following warning when the server is started:
<Sep 4, 2008 10:45:34 AM IST> <Warning> <WorkManager> <BEA-002919>
<Unable to find a WorkManager with name weblogic.wsee.mdb.DispatchPolicy.
Dispatch policy weblogic.wsee.mdb.DispatchPolicy will map to the default
WorkManager for the application bea_wls9_async_response>

Cause:
There is no WorkManager with the given name

Solution:
This means that you configuration is not correct. Ensure that the dispatch policy name
matches with WorkManager name defined either within the same application or one
defined globally.
But this is a just a warning and can be ignored if you are not using the Dispatch
policy.

Created by P.V.J. Pavan Kumar