So uncheck this option and add a DataSource with the correct JNDI name via the WLS console.įorum: WebLogic Server - Upgrade / Install / Environment / Migration It’s not possible to automatically deploy your ear file with this option. You have to adjust your application properties in a way that they‘ll not include the weblogic-jdbc.xml. :-)Īt .prepare(JDBCModule.java:290)Īt .ModuleListenerInvoker.prepare ModuleListenerInvoker.java:93)Īt (ExecuteThread.java:173)Ĭaused by: : : : : : No credential mapper entry found for password indirection user=cm for data source CMĪt .DataSourceConnectionPoolConfig.getPoolProperties(DataSourceConnectionPoolConfig.java:84)Īt .prepare(JDBCModule.java:252) Grab a pint of (Belgium) Beer, sit down, relax and see how the job is now done for you. I added a new ‘Windows batch command’ Build step in Hudson that executes the deployWLS.cmd file. Java weblogic.WLST Deploy to WLS Finished I changed the bottom of deployWLS.cmd to look Your environment has been Deploy to WLS I created a python script file called deployDummy.py and added it to the same directory.Ĭonnect('weblogic','weblogic1','t3://localhost:7101')ĭeploy('dummy_application1','C:\Hudson_Slave_Node\workspace\trunk\dummy.ear',targets='DefaultServer') I copied the MIDDLEWARE_HOME\wlserver_10.3\server\bin\setWLSEnv.cmd to C:\Hudson_Slave_Node\workspace, and renamed it to deployWLS.cmd With the help of a blog post of Jay senSharma it actually was quite an easy job. As I told in my previous post on Hudson I had the wish/idea to extend my Hudson build script in a way that it would fully automate the deployment of the ear file to a WebLogic server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |