WLST deployment scripts not installing ODSI created services

Question

Some time ago, I modified some example scripts that installed ALDSP 3.0 assets into an ALDSP 3.0 domain, and everything was working dandily. A few months ago, we upgraded our ALDSP 3.0 domain to ODSI 10gR3. We also found we were still able to use the same WLST scripts with no modifications to install the assets into our ODSI domain.
Now, what I have found is that when we export a dataspace into an ODSI jar from ODSI Workshop and install it with this script, the script only installs those services that were originally created in the ALDSP Workshop. If I install the exact same jar through the ODSI console, it installs all of the services as expected.
Has anyone else seen this sort of behavior with using WLST scripts to deploy ODSI assets. I'm guessing something has changed that I need to account for in my script, but I haven't been able to find it yet. Any help would be appreciated.
Edited by: DoubleT on Oct 8, 2009 5:20 PM

Answer 1

so you have some dataspaces (projects) in ODSI that you can export and then deploy with WLST, and some dataspaces that you cannot, correct?
To make sure that the first bunch actually do deploy, you could go to the ODSI console, delete them, deploy with WLST and check the console to see if they have reappeared. When you're convinced that works, and you're convinced that the others don't deploy - your just left with figuring out the difference. The simpler they are, the easier to diff them. If you're down to something really simple and don't see anything - engage customer support to help.
It's unlikely that deployment fails without emitting some sort of error message - I would be looking in the server log.
In ODSI 10.3 - the sample wlst scripts - SessionCommands.py expects the jar to be in user.dir instead of "rootFolder" in 3.2. (see below). There is also a README.TXT and a DspSecurityPolicy.py script.
--------------------- ODSI 10.3 - SessionCommands.py ------------------
import DspCommonCommands as dsp
print 'Connecting to weblogic server instance...'
connect("weblogic","weblogic","t3://localhost:7001")
print 'Creating a deployment session...'
dsp.createDeploymentSession('ALDSP_WLST_SESSION')
#Import here uses the default DeploymentOptions
#To use fancier DeploymentOptions inline the code of dsp:importDataSpace
#and make necessary changes
userDir=System.getProperty('user.dir')
importJarPath=userDir+'/SimpleApp.jar'
print 'Importing ' + importJarPath
dsp.importDataSpace('SimpleApp','ALDSP_WLST_SESSION',importJarPath)
print 'Activating the deployment session...'
dsp.activateDeploymentSession('ALDSP_WLST_SESSION')
#Export here uses the default ExportOptions
#To use fancier ExportOptions inline the code of dsp:exportDataSpace
#and make necessary changes
exportJarPath=userDir+'/dataspace_with_config.jar'
print 'Exporting the dataspace to ' + exportJarPath
dsp.exportDataSpace('SimpleApp',exportJarPath)
print 'Disconnecting from weblogic server...'
disconnect()