I have deployed an application on weblogic 12c and all the deployment successful while I am trying to run the application the application status changed to "start running" after a while it changed to prepared.
how I can change that application status to Active?
You have to select the deployments and select service all requests from start dropdown.
In 12c you will find this option in control tab of deployments summary page.
check this out
Check all data sources bound to this deploy.
If there is a connection error, your deploy can revert to the 'prepared' state
Related
I have deployed my application on weblogic12C and all the deployments are successful while trying to activate deployments the status changed to "prepared" or "start running" state. its not showing the state as Active. checked logs as well there is no error. Can someone help to resolve the issue.
Tried re-creating domain, data source and deployments
I'm looking at implementing a blue/green deployment strategy. It will be for a database driven web application. We are using Teamcity and Octopus deploy currently.
To my knowledge, to achieve this strategy, the changes to the database need to be such that both versions of applications will continue to work, so in the case the of a rollback, the database changes don't need to be reverted.
I have read Octopus suggested implementation of this here.
My question:
Does anyone test the current active application in prod against the database changes prior to promoting to prod? E.g. In Test or UAT?
If so, how do you fit this requirement with the deployment strategy, especially when configuring it with Octopus?
Does anyone test the current active application in prod against database changes prior to promoting to prod.
Octopus lets you easily deploy the current live version to your pre-production environment, so you can test it against the upgraded database prior to deploying the upgraded database to your live server.
So if you have version 1 of your application live with database version a, and have version b of your database coming through, followed by version 2 of your application, you can test this in pre-production...
1 a - Same as live
1 b - First phase of testing (followed by release of `b`)
2 b - Second phase of testing (followed by release of `2`)
I have created some stored procedures on my dashDB instance on Bluemix, to manipulate data in tables in the same instance.
I can run these from Data Studio and they work as intended.
Next, I created a process in Workflow Scheduler, which I provisions as a service in the same app, where the dashDB is also a service.
While creating the job step in the process, I noticed a message in the dialog window. I have attached a screen shot here:
http://i.stack.imgur.com/EI2b7.jpg
When I did try to run the process step from Workflow Scheduler, the process failed with a JDBC not found error.
I do realize that the Workflow agent I'm using is hosted on Bluemix, so I am puzzled how I can install the JDBC client there.
Should I be setting up an agent on a local machine outside of bluemix, in a hybrid mode?
Currently there are 2 possibilities:
Open a ticket to ask for a dedicated cloud agent and then download
the JDBC driver on the agent.
Download and install an agent on a VM or on-prem.
It looks like you have the incorrect value for "JDBC jar class path" the correct value is /home/wauser/utils/
I'm not sure why it is required that we put enter this but I was able to get the connection to dashDB working with this change.
JDBC jar class path: /home/wauser/utils/
I created an simple skeletal web application. I created only a simple blank JSF page. Right click and run. Then I got the following message in the Log console.
The Server Instance cannot be started because the Integrated Weblogic domain was not built successfully.
Can anybody suggest me why I am getting this error?
Your question does not provide detailed information.
The best way would be to go to weblogic domain options from start menu and create a new domain.
Then link that domain in jdeveloper and use the same. Delete the integrated domain i.e. base_domain folder.
There were 2 ways this problem can be fixed:
Try starting and fixing any issues with the Integrated weblogic domain. Till that is not starting successfully, JDeveloper cannot do anything on that. For me one time startup of the current domain outside of the Jdeveloper solved the issue. After that it was working fine from JDeveloper too.
Another option is as stated by vijayinani above to create a new domain and link it. But, beware your integrated base_domain is not having anything which you need to preserve if you plan to delete that.
I am here to get some expert advice on deploying applications to WebLogic Production Server.
Is it a best practice to use Admin Server Console for deploying and redeploying applications in production. Actually I am deploying to a cluster having two managed server instances.
I have encountered this issue while i am redeploying application in the production. When i am deleting existing .ear file and adding updated .ear file will put the updated .ear file into prepared state. I can not make it Active state using Admin Server Console. If i try it will through some exceptions. But after some time it automatically goes in to active state, but i don't know what is happening inside. Sometimes i restart the server to make it active. Could anybody explain me what is the procedure when deploying application and redeploying applications in weblogic
Thanks in advance for any Help...
Generally WLST (WebLogic Scripting Tool) is used to deploy the applications. Administration Console can also be used to deploy/upgrade the applications but if there are many environments that need to be upgraded then WLST (which works like a command line tool) is much better option.
Get an overview of WLST to know how to use it to deploy/undeploy/upgrade applications.
Check out "Understanding WebLogic Server Deployment" and the "Redeploying Applications in a Production Environment". There are different factors that affect redeployment of an application which you might be running into.
http://docs.oracle.com/cd/E23943_01/web.1111/e13702/understanding.htm#i1057116
http://docs.oracle.com/cd/E23943_01/web.1111/e13702/redeploy.htm#g1039635
Additionally, there is a WebLogic Plug-in for Maven in more recent WebLogic releases that you can use for deployments in conjunction with Maven.