I am new to Websphere and I found many answers for *.ear file deployment. Most of them use format similar to "
./wsadmin.sh -host vmllkb056933n.myspace.com -port 5000 -c '$AdminApp> install /apps/test-app.ear'
I am always getting errors like:
WASX8011W: AdminTask object is not available. WASX7015E: Exception running command: "$AdminApp install /apps/cdm-fi.ear"; exception
information: com.ibm.ws.scripting.ScriptingException: WASX7206W: The
application management service is not running. Application management
commands will not run.
I am in a RHEL 6 Environment and runing IBM Websphere 8.5.5.3
What is the easiest way to deploy ear file to IBM Websphere 8.5.5
Make sure your are using the deployment manager wsadmin.sh and that the dmgr process is running. Also the port you reference should be the SOAP_CONNECTOR_ADDRESS of the dmgr. Referencing the cluster or server name in a federated environment tells the dmgr where to put the code, as in the two examples below.
$AdminApp install "myapp.ear" {-cluster clusterName}
or
$AdminApp install app_server_root/installableApps/DynaCacheEsi.ear
{-appname MyApp -cell myCell -node myNode -server server1
-filepermission .*\\.jsp=777#.*\\.xml=755}
Don't forget to save and syncnodes. As in the jython below.
AdminConfig.save()
AdminNodeManagement.syncActiveNodes()
Try this.
Syntax :
installApp $earFile $appName $destinationDir $serverName $nodeName $cellName $wasprofile
Related
It is required to install the application on the WebSphere via jython using the AdminApp class.
I delete through the method AdminApp.uninstall
wsadmin.bat -user alex19 -password qwerty19 -c "AdminApp.uninstall('MK.MyApplicaiton')" -lang jython
I want to use the installation method to install the same ear, but I did not succeed using the IBM documentation. Please tell me how to use the wsadmin.bat and AdminApp to install the application?
I get such an error, but the problem is that I do not know how to transfer the file with the properties and the configuration file:
C:\WSAS\bin>wsadmin.bat -user alex19 -password qwerty19 -c "AdminApp.install('C:/ear/my-applicaiton.ear')" -lang jython
WASX7209I: Connected to process "adminagent" on node KSDD using SOAP connector; The type of process is: AdminAgent
WASX7015E: Exception running command: "AdminApp.install('C:/ear/my-applicaiton.ear')"; exception information:
com.ibm.websphere.management.exception.AdminException
javax.management.MBeanException
com.ibm.websphere.management.exception.AdminException
com.ibm.websphere.management.exception.AdminException: ADMA0043E: C:\Users\Administrator\AppData\Local\Temp\app9157482086909190098.ear does not exist for installation.
WASX7209I: Connected to process "adminagent"
You ran wsadmin against an admin agent, which cannot run applications. You should install applications to a deployment manager (ND) or an individual application server (base/standalone application servers)
I have deployed an application on server1 in Websphere 8.5.5
Can I clone it to create server2 with the same application deployment and datasources.
In case you are in an ND environment you can create a server template (From the console: Websphere Application Servers > Templates > New ) based on the server1 and then create server2 based on this template.
This way you easily get all configuration of server1 (datasources, jvm arguments etc) into server2.
You can install WAS at same level on second machine and then use "manageprofiles -backupProfile" and "manageprofiles -restoreProfile" commands to move profile to machine2. Then use the AdminTask.changeHostName ('[-interactive]') to change hostname on the machine.
You can change nodename to different nodename using renameNode.bat also. The only thing is there will be no command to change cellname and you will have same cellname as original server.
For more details please review the link below :
http://www-01.ibm.com/support/docview.wss?uid=swg27020204
I have googled this extensively before posting it here. I've been trying to find out a way to enable JMX Access on a Tomcat instance installed as Windows service. Its quite straightforward when Tomcat is invoked via the startup.bat script, one just needs to set the CATALINA_OPTS environment variable to something like "-Dcom.sun.management.jmxremote.port=1234 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false"
But how do i get the Tomcat Windows service to read these options? I tried this:
C:>tomcat\server\bin> service.bat install #install the Tomcat7 windows service
C:>tomcat\server\bin> tomcat7.exe //US//Tomcat7 ++JvmOptions "-Djava.io.tmpdir=$INSTDIR\server\temp;-XX:MaxPermSize
=256m;-Dcom.sun.management.jmxremote.port=8090;-Dcom.sun.management.jmxremote.au
thenticate=false;-Dcom.sun.management.jmxremote.ssl=false" --JvmMs 256 --JvmMx 1
024 #update the installed service using the //US switch; set tmpdir, JMX access and heap size
When i start the service from Services panel, the service fails to start and i get the following error on the logs\tomcat7-stderr-yyyy-mm-dd.log file:
yyyy-mm-dd hh:mm:ss Commons Daemon procrun stderr initialized
Error: Invalid com.sun.management.jmxremote.port number: 8090 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
I don't have a Java background, am i trying to achieve something outlandish here? Please advise.
Answering my own question; turned out to be easier than i thought.
Following needs to be done, for enabling JMX access for Tomcat installed as a Windows service, that has a name "ApacheTomcatWindowsServer" for example:
Install Tomcat as Windows service, either using the command (first cd into \bin\ )
service.bat install
or your custom scripts.
Enable Apache Service Manager for the installed service using the following command:
tomcat7w.exe //MS//ApacheTomcatWindowsServer
This should start Apache Service Monitor program on your system tray. Click on its icon. select 'Configure', click on the 'Java' tab and append the following on the 'Java Options' text box, one option per line:
-Dcom.sun.management.jmxremote.port=8090
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
Save and exit and restart the service.
To connect to the JMX console, fire jconsole from your JDK installation, click 'New Connection', specify 'Remote Process' and enter hostname:8090.
you can also uninstall the service by
service.bat remove
then edit the service.bat and add the parameters in your StartPath and add the options
-Djavax.management.builder.initial=;-Dcom.sun.management.jmxremote.port=8090;-Dcom.sun.management.jmxremote.authenticate=false;-Dcom.sun.management.jmxremote.ssl=false
here is the sample StartPath in my file
--StartPath "C:\tomcat7\" --Startup auto --JvmOptions "-Dcatalina.home=%CATALINA_HOME%;-Dcatalina.base=%CATALINA_BASE%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed;-Djava.io.tmpdir=%CATALINA_BASE%\temp;-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager;-Djava.util.logging.config.file=%CATALINA_BASE%\conf\logging.properties;-Djava.rmi.server.hostname=;-Djavax.management.builder.initial=;-Dcom.sun.management.jmxremote.port=8090;-Dcom.sun.management.jmxremote.authenticate=false;-Dcom.sun.management.jmxremote.ssl=false" %JAVA_OPTS% ^
re-install the service by
service.bat install
then start Tomcat to apply changes
I am using RAD 7 with WebSphere 6.1, after creating a new profile and a new server I am unable to start the server. The server fails to start with this error:
ADMU0128I: Starting tool with the AppSrv03 profile ADMU3100I: Reading
configuration for server: newserver
ADMU0111E: Program exiting with
error:
com.ibm.websphere.management.exception.NoServerDefinedException: No
configuration defined for server: newserver
This implies that there is no server with the name newserver.
How did you create the profiles? If i recall correctly, if you create a standalone server profile in WAS 6.1 the name of the server is a sacred "server1".
You have to run scripts to change the name of the server from "server1" to anything meaningful. I am guessing you haven't done that.
Go to the runtimes directory of your RAD and run the command serverstatus.bat and this would list the server names for that profile (run it froom your profile's bin directory).
This should tell you the server names. Run start server from within the command line and ensure that the server runs's properly.
This is what I would do for a start to move forward
HTH
Manglu
What command are you using to start the server here? I am assuming "newserver" is the name of profile here, so you can start the server using the following command
startServer server1 -profileName newserver
If you have only one profile then you don't need to specify profile name
startServer server1
I saw something once for wrappers used to do this but it asked for a licensing fee. Is there an open source way to do this?
"JBoss AS comes with Windows service executable as part of JBossNative
that can run JBoss Application Server as service.
The service executable jbosssvc.exe transforms the run.bat and
shutdown.bat batch scripts to services. This means that any change
made to those scripts will be used both in service and command
line mode."
http://www.jboss.org/community/wiki/JBossNativeWindows
A Problem I had was the remote Access to JBoss. In JBoss 4.2.3 you must start it with the Parameter run.bat -b 0.0.0.0 to have access from other hosts.
I think since JBoss 4.2 remote access is turned off by default.
My solution was to adjust the :RESTART Section in the file run.bat like this:
:RESTART
"%JAVA%" %JAVA_OPTS% ^
-Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" ^
-classpath "%JBOSS_CLASSPATH%" ^
org.jboss.Main -b "0.0.0.0" %*