Troubleshooting
Problem
When you run the editAsset wsadmin command with the UpdateAppContentVersionsStep parameter, the parameter is ignored and you get a generic exception message.
Diagnosing The Problem
There is a missing exception message that describes a behavior change between WebSphere Application Server Version 7 and Version 8. See the following text of the missing message:
In the WebSphere Application Server Version 7 Feature Pack for OSGi Applications and JPA 2.0, bundle changes to the asset are applied by restarting the business-level application. In Version 8, these changes are applied by updating the composition unit. The new approach in Version 8 means that many bundle changes can be applied in place, without restarting the business-level application. To enable this new approach, the UpdateAppContentVersionsStep parameter has been disabled and replaced with the UpdateAppContentVersions parameter, and instead of restarting the business-level application you run the editCompUnit command with the CompUnitStatusStep parameter. See the information center topics "Updating bundle versions for an EBA asset using the editAsset command" and "Updating an OSGi composition unit using the editCompUnit command."
Resolving The Problem
To update bundle versions using wsadmin commands, complete the following steps:
- If you have created a script for updating bundle versions and applying the updates, modify your script to use the editAsset command with the UpdateAppContentVersions parameter instead of the UpdateAppContentVersionsStep parameter.
- Remove any business-level application restart behavior that was inserted to trigger updates to be applied, and instead use the editCompUnit command with the CompUnitStatusStep parameter to apply the updates; for example:
// *** Version 7 with OSGi Feature Pack script ***
AdminTask.editAsset('
-assetID WebSphere:assetname=test.eba
-UpdateAppContentVersionsStep [
[test.impl 1.0.0 1.1.0]
[test.use.bundle 1.0.0 1.0.1]
]
')
AdminConfig.save()
// wait for downloads to complete by polling the BundleCacheManager MBean
...
// restartBLA
AdminTask.stopBLA(['-blaID', 'WebSphere:blaname=test'])
AdminTask.startBLA(['-blaID', 'WebSphere:blaname=test'])
// *** Version 8 script ***
AdminTask.editAsset('
-assetID WebSphere:assetname=test.eba
-UpdateAppContentVersions [
[test.impl 1.0.0 1.1.0]
[test.use.bundle 1.0.0 1.0.1]
]
')
AdminConfig.save()
// wait for downloads to complete by polling the BundleCacheManager MBean
...
AdminTask.editCompUnit('[
-cuID WebSphere:cuname=test_0001.eba
-blaID WebSphere:blaname=test.app
-CompUnitStatusStep [[WebSphere:asssetname=test.eba]]
]')
// any number of AdminTask.editCompUnit items for new configuration
AdminConfig.save()
// no BLA restart
The missing exception message is added in fix pack 8.0.0.1. For more information about this fix pack, see http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-mp&topic=wasv8001_readme1.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21496409