If you create a OSB domain with WLST offline and the standard templates your Managed server will always be called osb_server1.
To get around this I normally just change the name directly in the config.xml.
But there is an alternative. Oracle has created a special domain template you can get of MOS. From “OSB 11.1.1.3+ How to Create an OSB Cluster with WLST (Doc ID 1327262.1)” you can download the scriptedwlsb.jar template.
It’s solves some problems with creating OSB clusters and lets you name the Managed servers.
I have tested it with a OSB 11.1.1.7 and it works fine.
Default it creates a Cluster with 3 Managed servers.
1. Install the WebLogic server and the OSB software
2. Copy the scriptedwlsb.jar file
cp scriptedwlsb.jar /u01/app/oracle/product/osb/Oracle_OSB1/common/templates/applications/.
3. osbDomain.properties
Edit the osbDomain.properties file. Set number of Managed servers, names, ports, Data source parameters, Cluster parameters etc.
4. Create the domain
cd /u01/software/WLSTcreate_domain-cluster . /u01/app/oracle/product/osb/wlserver_10.3/server/bin/setWLSEnv.sh /u01/app/oracle/product/java_current/bin/java -Dwlst.offline.log=wlstlog.log -Dwlst.offline.log.priority=debug weblogic.WLST createDomain.py
5. oracle.jrf.coherence
The only problem I had was that oracle.jrf.coherence was not target to the cluster.
. /u01/app/oracle/product/osb/wlserver_10.3/server/bin/setWLSEnv.sh java weblogic.WLST -skipWLSModuleScanning connect(username='weblogic',password='weblogic1',url='t3://wintermute:7001') domainConfig() edit() startEdit() cd('/Libraries/oracle.jrf.coherence#3@11.1.1') set('Targets',jarray.array([ObjectName('com.bea:Name=AdminServer,Type=Server'), ObjectName('com.bea:Name=alsbCluster,Type=Cluster')], ObjectName)) save() activate()
6. EM is missing
So you have to add it. Here is a simple script to do that – addEM.py.
. /u01/app/oracle/product/osb/wlserver_10.3/server/bin/setWLSEnv.sh java weblogic.WLST -skipWLSModuleScanning addEM.py
{ 6 comments… read them below or add one }
Hi Peter
Thanks for pointing this out, but can’t you just rename the OSB servers with WLST (server.setName())? Or is that not supported? (I wonder how the config wizard does it… I would have thought it used the template too?)
Simon
Hi Simon,
It is sometime ago that I was messing around with this. Not sure you can use setName etc. in offline WLST? I will test it.
Yes I would love to know how the wizard does it. I have not been able to find anything about it.
Regards Peter
Hi Peter, thanks for the post, looks like this scriptedwlsb.jar template is just what I needed to create an OSB cluster with fully customizable managed servers (name, listen address, ports, etc).
I wrote a WLST script loading the standard templates and performing all the customizations but I always ended up with incorrect targeting of OSB components, filestores not created and so on. Thanks again 🙂
Hi Peter,
Please send me the scriptedwlsb.jar
Sorry Gouri. I am not allowed to distribute it. You must download it from MOS yourself.
Regards Peter
Hi Peter,
The article is very useful. Kindly send me the scripts. Thanks in advance