I experienced this error when I was updating my JDBC Master Jython Script

Simply, the reason for this is either you have tried to create another/new Datasource using the same JNDI name, or you are calling a create when you should be calling a modify. When modifying we can use the Datasource name to locate the MBean and use AdminConfig to update the Datasource, this means we can refer to the same JNDI name for the Mbean, but if we are not updating ie using AdminTask to create or AdminConfig to create, then we must specify a unique JNDI name because each MBean must have a uique JNDI name.

Note: You could iterate existing Datasources and see if this JNDI has been used before.

If you wish to purchase WAS 8.5.5.x / or previous version(s) of WebSphere automation scripts, then please ping me via my support site http://support.themiddlewareshop.com


Leave a Reply