I have deployed an App in weblogic server (no_stage mode).
When the timestamp of app ear changes, WLS redeploys it on its next restart (hot deploy is the name for this i think).
Is there anyway i can prevent this behavior and make it redeploys only when i specifically tell it to redeploy
Related
I've created multiple managed servers in Weblogic. Each managed server has same IP(IP of weblogic server) and unique port.
I've installed ear and war files in these managed servers and all of them has their own context-root.
For example I have ear file A with context-root A on server A and a war file B with context-root B on server B.
Whenever I browse IP:PORT(A) which has set on server A, this application needs some files on war file B which has deployed in server B. So A can not find its resources and I get error.
I should mention that I put them in a cluster too but nothing changed.
How can handle this matter?
The cluster won't help you in this way because each web app is isolated from others in its own web container. If you need to share data or resources between web apps you can use a shared file system or a database for instance.
For this purpose I've used Oracle Http Server (OHS) plugin. after hours of searching in internet I've found that Weblogic application server does not implement anything to handle this issue.
https://docs.oracle.com/middleware/1213/webtier/
I wan to know if the wars are redeployed on each start/restart of Tomcat.
Or is necessary to delete the deployed folder before restart it?
If that is not redeployed, how can I configure tomcat to deploy with every start.
Thanks.
Tomcat does not redeploy war files on restart. Restart is simply turning the underlying service off and back on. Tomcat does not do the deployment so you will need some other tool (like Jenkins) to automate your deployment.
I installed Apache Tomcat 7. During the install, it asks if I want to do a full install or if I want to install just the web service. I chose to install the full package (Tomcat and a web service). When it finished, I had a windows service I could start. I could then view/use the web-based tomcat admin panel.
I shut down the service and re-ran the installer to setup an additional web service. I will have a couple dozen web apps to setup. During the install, I selected the "Web Service Only" so I could install the additional web app without installing Tomcat again. The installation finished OK.
I checked the installation folders and see both of my web services setup in the webapps folder. I start the tomcat service OK. When I attempt to view the web-based admin panel for either web service .. the originally installed web service and the second web service, tomcat seems to hang. When I attempt to shutdown the service, it doesn't shutdown properly and displays the windows error "unable to shutdown service". Eventually I can kill the process.
What could be causing this issue? I'm new to Tomcat on Windows so I apologize if I did not provide enough information. The web-based admin panel DOES work when I have a single webapp. When I have two or more webapps, the admin panel quits working (hangs).
Any ideas?
If you have Tomcat install a separate service for each web application, then you should be able to control each of them separately. They will be running separate JVMs, separate Tomcat services, etc.
If you had instead intended to have a single service with multiple applications deployed on it, then it appears that you may have made a mistake and configured multiple services instead.
From the command-line, you can launch the Tomcat service manager and specify exactly which of the Windows Services you'd like to control. For example:
C:\path\to\tomcat> tomcat8w.exe //ES//MyService
(Where MyService is the name you gave to your Windows Service when you configured it.)
You can find more information on Tomcat's Windows Service Documentation.
I have installed Worklight 6.2 on Linux, using Liberty 8.5.5 and DB2 10.5. Created the DB2 databases for WRKLGHT and WLREPORT. Have executed the Server Configuration Tool and successfully created a Worklight Server configuration (did not have any errors in the Console view when running the Ant tasks, tables were created successfully in the database, and configuration shows deployed status in the SCT). Created a runtime environment in the SCT, also seemed to succeed (no errors in Console view, tables created/updated, runtime environment shows deployed in the SCT). Stopped and restarted the Liberty server.
Can hit Worklight admin at (/worklightconsole) and log in successfully using my demo user, however it then indicates there are no runtime environments. When trying to access runtime environment at /worklight/console (which should be the correct URL given how I created the runtime config in SCT using my Worklight project WAR), I get various errors: first "Service unavailable since initialization is not yet complete." then after retrying for about a minute or two I get "javax.servlet.ServletException: java.lang.RuntimeException: Timeout while waiting for the management service to start up at com.worklight.core.auth.impl.AuthenticationFilter.isWaitingForInitialization(AuthenticationFilter.java:561)".
Seems the management service is not starting up successfully. Upon reviewing the messages.log I see the following error precede it: "FWLSE0242E: Failed to synchronize application runtime information. The servlet initialization failed and the servlet will deny serve. The most common reason is a failure in JMX communication with the ''worklightadmin'' service. You need to restart the web application after fixing the problem. [project worklight]" and this creates an FFDC log.
I know this is a lot of information but trying to be complete. Anything I should check to fix the JMX communication issue and get the management service starting?
Thank you for the replies back. Turns out there is an issue with Liberty (I was on 8.5.5.0) and the IBM JDK I was using (1.7_64). Swapped out to the Oracle JRE (1.7.0_60-b19), pointed Liberty to use it, and the problem was solved. I am pursuing a fix with the Liberty team through IBM Support for this issue.
I cannot give a unique solution, but I can explain the situation and this may lead to a solution.
The runtime servlet initialization tries to contact the Worklight Admin service. The Worklight Admin service is a web application that must be running when the runtime starts. The runtime was not able to find the Worklight Admin service. It waited a while, in case that the Worklight Admin service is just starting up, but then gave up due to a timeout because within a given time, it could not find the Worklight Admin service.
Possible reasons:
the web server is not at all configured to run the Worklight Admin service. In your case, this seems not the problem, since you can access the Worklight Console. You should also see in the log file whether the Worklight Admin service did start.
the worklightadmin service might never start up ... this could be a configuration problem, e.g. with the WLADMIN data base. This could also be detected from the server logs.
when the runtimes and the Worklight Admin service start up together, it might be that the Worklight Admin service simply takes too long to start. Let's say you have 100 webapps, and the runtime starts first and the Worklight Admin service starts last, it could be that the 98 other webapps take too much time to start. In that case, make your web server lighter ... run only Worklight on that webserver, nothing else.
the Worklight Admin service starts, but the runtime cannot communicate with it. This indicates that the JMX communication is misconfigured. Follow the documentation of the webserver how to configure JMX. For liberty, see http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_admin_restconnector.html?cp=SSD28V_8.5.5%2F1-5-2-10-1&lang=en
I have installed WebLogic 10.3.6 in Production mode and I have deployed an EAR application in my Managed Server. How can I make sure that when I restart my Managed server then WebLogic will re-deploy my application once again?
There are a couple ways you can verify a deployment...
Click the deployments link in the admin console, find your deployment, click it, and verify the path, staging mode, and targets are correct. You can also click on the monitoring tab to verify it is in the Active state.
You can verify the same by opening the config.xml file in your /config directory. Look for the tags
Once you've deployed, you don't need to worry about it disappearing when you restart. It will be there until you choose to remove it OR you delete the .ear file.