Domain creation using WLST offline mode

Question

Hi,
We are migrating from WL8.1SP5 to WL10MP2. After reading through the various options (WLST online, WLST offline, WLST.configToScript(), and Configuration Wizard) , I have concluded that we will use WLST in offline mode to create domains in our prod, qa, and dev environments. In 8.1 I had a silent script that would create domains for me repeatedly in any environment very easily. I want to map this script into the corresponding SOME_NAME.py script to be used for WL10MP2 domain.
I have the BEA provided basicWLSDomain.py (please see below) script. I have difficulty in understanding more than half of that script! I know the basic concept is to traverse the MBean tree and creat and/or set parameters. But I do not know which MBean I will need to modify/create.
Example 1:
readTemplate("C:/bea/wlserver_10.0/common/templates/domains/wls.jar")
cd('Servers/AdminServer')
Q1] I went through http://e-docs.bea.com/wls/docs90/wlsmbeanref/core/index.html but could not find either ServersMBean or AdminServerMBean.
Example 2:
cd('/')
create('myJMSServer', 'JMSServer')
cd('/')
create('myJmsSystemResource', 'JMSSystemResource')
cd('JMSSystemResource/myJmsSystemResource/JmsResource/NO_NAME_0')
Q2] What is a JMSSystemResource? (If I remember correctly, there is no such thing in WL8.1)
Q3] What is JmsResource?
Example 3:
cd('/')
create('myDataSource', 'JDBCSystemResource')
cd('JDBCSystemResource/myDataSource/JdbcResource/myDataSource')
create('myJdbcDriverParams','JDBCDriverParams')
cd('JDBCDriverParams/NO_NAME_0')
set('DriverName','com.pointbase.jdbc.jdbcUniversalDriver')
set('URL','jdbc:pointbase:server://localhost/demo')
set('PasswordEncrypted', 'PBPUBLIC')
set('UseXADataSourceInterface', 'false')
create('myProps','Properties')
cd('Properties/NO_NAME_0')
create('user', 'Property')
cd('Property/user')
cmo.setValue('PBPUBLIC')
cd('/JDBCSystemResource/myDataSource/JdbcResource/myDataSource')
create('myJdbcDataSourceParams','JDBCDataSourceParams')
cd('JDBCDataSourceParams/NO_NAME_0')
set('JNDIName', java.lang.String("myDataSource_jndi"))
cd('/JDBCSystemResource/myDataSource/JdbcResource/myDataSource')
create('myJdbcConnectionPoolParams','JDBCConnectionPoolParams')
cd('JDBCConnectionPoolParams/NO_NAME_0')
set('TestTableName','SYSTABLES')
Q4] Can you please explain the above snippet line by line?
Q5] Why are certain attributes set like this --- set('TestTableName','SYSTABLES') while certain attributes like below are set like this -- myq.setJNDIName('jms/myqueue')?
Example 4:
myq=create('myQueue','Queue')
myq.setJNDIName('jms/myqueue')
myq.setSubDeploymentName('myQueueSubDeployment')
cd('/')
cd('JMSSystemResource/myJmsSystemResource')
create('myQueueSubDeployment', 'SubDeployment')
Q6] What us a SubDeployment?
I apologize for the long question. I would greatly appreciate any help!
Thanks!
Edited by: user10045656 on Oct 29, 2008 11:03 AM
Edited by: user10045656 on Oct 29, 2008 11:06 AM

Answer 1

1 - What is the best way to create a schema, for reporting application, during automated domain build process as we need to create new domains from the script and also be able to start and deploy applications on it. which will also require to have db schema for reporting application.
My suggestion would be to execute the scripts under /neelapu/bea/post31/RC4-samples/osb_10.3/dbscripts/oracle/*.sql with your automated process. OSB requires two simple tables WLI_QS_REPORT_DATA and WLI_QS_REPORT_ATTRIBUTE.
If reporting is not required then we can modify (I guess) in wlst offline mode to delete the below applications from domain.
<app-deployment>
<name>JMS Reporting Provider</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>/neelapu/bea/xyz/load4/Oracle_OSB1/lib/common/jmsreportprovider.ear</source-path>
<deployment-order>125</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>Message Reporting Purger</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>/neelapu/bea/xyx/load4/Oracle_OSB1/lib/common/msgpurger.ear</source-path>
<deployment-order>126</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
Thanks
Manoj