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.Its not showing state as Active can some one help me please.In log files also there is no errors are showing
Related
In a SQL server in my environment, couple of days after patch(Not immediately after), syspolicy purge job started failing at step 3 executing powershell. When I created a test job with a simple print statement that is not working as well. If i create a Proxy with my account and run the job it suceeds. The agent account is a domain account with both local admin and sysadmin permissions on SQL server. I'm not sure why it crashes with the below error message everytime it calls powershell.
Application popup error - SQLPS.exe The application was unable to start correctly (0xc0000142). Click OK to close the application.
Reboot it is!! Whew! There aint anything wrong with the Agent account. Something with the agent account was broke! Glad the issue is resolved.
Note:: The server was rebooted after the patch and there was no pending reboot. Also, after patching the job ran successfully 2 days. So just a weird failure! I'm unable to find what broke the account.
Firstly connecting to the weblogic server using connect command then
I am deploying ears using the deploy command and i have many ears to be deployed so after every ear deployment i have to go to the console and click on activate changes
Is there any command for activate changes
connect(username, password, urladmin)
deploy(applName,deploymentFile,targets=deploymentTarget,appversion='v1',timeout=0)
There is an activate command.
activate([timeout], [block])
"Activates changes saved during the current editing session but not yet deployed. This command prints a message if a server restart is required for the changes that are being activated."
https://docs.oracle.com/middleware/1213/wls/WLSTC/reference.htm#WLSTC254
I am trying to deploy the MobileFirst Admin Operational console using Server Configuration Tool. Started the configuration tool as root user. Create a configuration and saved the xml. Pressed the "Deploy" button. Its failed with JVM terminated Exit code -1 error.
MobileFirst Server Version 7.1.0.0-MFPF-Server-IF201510051721
WebSphere 8.5.5.7
Installation Manager JRE:jre_7.0.7001.20140909_1712
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
After this error, I am able to see the Admin console application and admin services application in WebSphere. But in Configuration Tool not able to create / add runtime under this configuration. It says no configuration found.
This is not a solution to the JVM crash you experiment, but a workaround to enable to be able to add the runtime (I understand from the above description that the crash happens after the Server Configuration Tool saved the configuration and deployed it).
Go to (homeDir)/.mobilefirst_platform_server/server-configuration-tool. You should find a directory named after your configuration. In that directory, you should find a file named (ConfigName).xml. Copy this file as (ConfigName).lastdeployed (ie same name as the xml file but change the suffix). The Server Configuration Tool would have created this file after deployment completion (and uses it for later operations such as uninstall) and it uses it as an indicator that the configuration is deployed.
I am using IBM Worklight 6 and for auditing purposes would like to know if I it is possible to log the details of tasks performed on the Worklight Console, i.e. log the details when deploying new version of app/adapter?
Regards,
Tom
Worklight, or more specifically, the application server that Worklight Server is deployed to (WAS, WAS Liberty profile, Tomcat), does not have the ability to filter logs into seperate files, for example for the purpose you have mentioned.
What you might be able to do is take the server log, and create your own manual filtering (by script, of course). What you will need to do is to find the prefix for each action done and filter using it.
In Eclipse (or your production environment) open server.xml > Logging and change the Console log level from Audit (default) to Info.
This in turn will produce the following log lines in the sever log:
[INFO ] FWLSE0084I: Adapter 'aaa' was deployed successfully. [project test]
In your script you can now filter for FWLSE0084I for adapters and similar prefixes for other actions, likely. I am not sure if all Worklight Console actions have prefixes, but if they are ones that require a connection to the server, then likely that they do.
http://i.stack.imgur.com/sZ0fj.png
We are trying to deploy Worklight Enterprise edition on Ubuntu server over Tomcat
While we were successful with several steps, we got stuck with one error while getting the Tomcat up and running with our War file. We use MySQL as DB.
The specific error we are facing is ".BeanCreationException: Error creating bean with name 'deployService' defined in URL"
SEVERE: FWLST0003E: ========= Failed starting project /td_ibm
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'deployService' defined in URL [jar:file:/usr/share/tomcat6/lib/worklight-jee-library.jar!/conf/integration.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException
The complete log trace text file can be found at Tomcat Log
This is clearly a configuration issue.
1. run mysql-admin (MySQL UI front end) and make sure you can connect to the Worklight catalog under the name and user you defined in the worklight.properties.
if the database is on a different machine than the tomcat (make sure you have set the right remote access permissions for MySQL (for testing only: try giving Worklight DB user an untrusted access .i.e. use "#%" ))
another issue: if you are installing Worklight on Tomcat: did you run the SQL schema script to create the Worklight schema ? you must run it manually (there is a workaround though: connect to the same database from Eclipse which runs a Worklight project)
what files do you have under /var/lib/tomcat6/worklight.home/td_ibm/data/export/adapters ?
If its empty, there maybe a bug in the Worklight code.