We are deploying our application war [180 mb] to IBM Websphere admin 8.5.5.9. It takes around 30 min to deploy a war.
In Weblogic there is a option for deploying a war, that is we don't need deploy a war second time onwards, so we just replace the updated war in that path and it takes a war from that path second time. Like, Is there any option in websphere. Please help me to resolve this.
This page Options for accelerating application deployment gives you several options for accelerating deployments. Article is to big to quote it here.
As alternative you can also do partial updates if you only need to change several files.
Related
I have deployed 3 war files in IBM WAS 8.5 (SupposeA.war ,B.war and C.war) ,I want A.war, B.war to be deployed first then C deployment should start.
Is there any way to do it.
This is required as my C.war is dependent on A.war and B.war.
Assuming that you are referring to the order of application start ("deploy" in WebSphere parlance is often used to refer to installation of an application, but that does not appear to be the issue here), then you would want to modify the applications' starting weights, as documented here: https://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.iseries.doc/ae/trun_app_startup.html
If these WARs are all part of the same EAR, the WARs' starting weights can be set separately within the EAR in the "Manage Modules" panel within the application configuration in the administrative console.
We have a large application deployed inside a huge war. Inside this package we have about 900 services using javax.jws.WebService, those guys impact the deployment time because when war file is put there, server starts to load any service!
There is any way to do some kind of "lazy load" on that?
Regards
Not that I know of. You can do some things to the ear file to get it to deploy faster but this can get quite involved. Or you could break it into multiple ear files. Some tuning options:
Mark modules with no annotations as metadata-complete so they won't be scanned.
Tune which packages are scanned: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/trun_app_reduce_annot.html
Rebuild webservices to include the wsdl with the service to avoid wsdl generation at deploy time.
I have installed IBM Worklight Server 6.0 in WAS 8.0.
I have deployed a projectA.war & projectB.war via ant script and I can access both the console with the different context root.
The problem I am facing here is, I have deployed the appA.wlapp in projectA.war via the Worklight console, the same application is available when I access the projectB.war console.
Can anyone help me to find the solution?
My only guess right now is that there is a mutual database for both projects so you see the same app in both consoles (and that too only happens w/out an error because maybe the different .war files have identical authenticationConfig.xml settings).
That is, the same database configuration is used for both projects; This configuration is either:
Part of the .war files that you deploy (in worklight.properties), or
Something that you configure in the Ant task script used to deploy the .war files, or
Some configuration in the application server hosting the .war files.
See documentation: http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fadmin%2Fc_clustering.html
Is it possible in Jboss deploying a ear and war file in the same server instance? If so any good source to get started? Any suggestion.
I have two applications deployed under my default deploy folder of jboss. I am running one application from which i have to call the other application to get some data. Is this possible? If so how to get started??
It is actually recommended that you only put 1 application in a server instance as a time. That said, I have had multiple ears and wars running in the same instance while I am developing. But for production it is better to separate them out. Since there is no extra cost involved this makes it easier to observe and debug apps.
Do you have a specific reason for wanting them to run side by side?
What version of JBoss are you running.
I have problem with deploying JSR168 portlet using xmlaccess. I have no problem with deploy and join to conrete page but I would like to add shared library reference automatically. Is it possible?? I added shared library named 'libshared' using IBM WS console. Can I add this reference in input xml using by xmlaccess?
I don't think you can do this in xmlaccess. But you may try putting a reference to the library under the Manifest.MF file of the META-INF directory of your portlet's war file.
Or could just put the shared jar file under your /shared/ext directory. Or you could put it inside your wps.ear file. Mind you, either of these two solutions would share your library with the entire portal installation, rather than just select portlets.
You can deploy the application using wsadmin or similar and use that to update the classpath (i.e. for the shared library), you can then use xmlaccess to deploy the portlets and reference the previously deployed application - although I think this may only work in WebSphere Portal 6.1.
Give me a shout if you need further details.
I encountered this as well, a while ago... and researched it to the max, including spending some time chatting with IBM's support in various levels.
The XMLAccess protocol doesn't provide for such "system-level" configuration alongside Portlet application deployment; it can only be used to install, customize and uninstall Portlet applications and related artifacts.
If your deployment strategy involves deploying WAR files directly through XMLAccess, then you will have to manually add the shared-library to the application through the WAS admin console; this will have to be done manually because, when deploying WAR files through XMLAccess, an EAR with some random name is being created by WebSphere Portal to "host" your WAR file; hence you can't script the attachment of a shared library.
(alternatively, you may wish to add the shared library to the server's (WebSphere_Portal) classpath)
If your deployment strategy, instead, involves deploying Portlet applications packaged as EARs, then you're in a better position; you could automate the shared-library attachment as part of your EAR deployment process, then use XMLAccess to inform WebSphere Portal about the location, in the EAR, of your Portlet applications (which is what Michael mentioned above; it works in WebSphere Portal 6.0 as well).
Good luck.