![]() | |
|
Using a monitored directory
With WebSphere Application Server V8, you can deploy or update applications automatically by copying an application archive to a specified, monitored directory. Monitored directories support the following types of applications:
Enterprise archive (EAR)
Web archive (WAR)
Java archive (JAR)
Session Initiation Protocol (SIP) module (SAR)
The monitored directory feature is disabled by default.
For stand-alone servers, the following directory is used:
profile_root/monitoredDeployableApps/servers/server_name
For distributed systems, the following directories are used:
directory for all servers named server_name
dmgr_profile_root/monitoredDeployableApps/servers/server_name
directories for a specific server_name
on a specific node_name
dmgr_profile_root/monitoredDeployableApps/nodes/node_name/servers/server_name
directory for the members of cluster_name
dmgr_profile_root/monitoredDeployableApps/clusters/cluster_name
Figure below shows a cell topology with one node (exampleNode01
). The node has
one stand-alone server (server1
).
test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 # mkdir -p monitoredDeployableApps/nodes/exampleNode01/servers/server1 test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 # mkdir -p monitoredDeployableApps/servers/server1 test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 # chmod -R 777 monitoredDeployableApps/
Figure below illustrates the monitored directory structure for the topology shown above. The directories marked with red ovals are the directories where you can copy an application to deploy it on specified run time.
Setting up a monitored directory
To enable and set up the monitored directory in WebSphere Application Server, complete the following steps:
In the administrative console, click Applications > Global deployment settings.
Select the Monitor directory to automatically deploy applications option, as illustrated in figure below. You can also change the default location of the monitored directory in the Monitored directory field.
Important: the WebSphere Application Server will not create a configured monitored directory for you. It must already exist on the system.
To change the standard polling interval setting, specify a number of seconds in the Polling interval field. Note that minimum value is 5 seconds. If you specify a lower or negative value, WebSphere Application Server will use 5 seconds automatically.
Click Apply to save the configuration.
Also, you can use wsadmin.sh
scripting to set monitored directory values:
test317:~ # /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jython WASX7209I: Connected to process "dmgr" on node test317CellManager01 using SOAP connector; The type of process is: DeploymentManager WASX7031I: For help, enter: "print Help.help()" wsadmin> wsadmin>c1 = AdminConfig.getid('/Cell:test317Cell01/') wsadmin>md = AdminConfig.showAttribute(c1, "monitoredDirectoryDeployment") wsadmin>AdminConfig.modify(md, [['enabled', "true"]]) '' wsadmin>print AdminConfig.show(md) [enabled true] [monitoredDirectory ${USER_INSTALL_ROOT}/monitoredDeployableApps] [pollingInterval 5] wsadmin>AdminConfig.save() '' wsadmin>
Working with a monitored directory
When an application is copied into the monitored directory, WebSphere Application Server creates a temporary copy of that application in another directory and installs it on the server. If you copy an application with a name that is already deployed on the server, it will be updated.
The monitored directory works only when the application server or cluster is running.
NOTE: Installing an EAR, JAR, WAR, or SAR file by adding it to a monitored
directory does not change existing Java Naming and Directory (JNDI) or other application
bindings. If you need to set binding values during deployment, install the file using the
administrative console application installation wizard, a wsadmin.sh
script, or a properties file
that sets the bindings.
Deploying and removing an EAR file on a stand-alone application server
To deploy and remove an EAR file on a stand-alone application server, complete the following steps:
Ensure that your server is running and that you configured the monitored directory.
Locate the monitored directory. For example, for a profile called AppSrv01
, copy your files
to the following directory:
install_root/profiles/AppSrv01/monitoredDeployableApps/servers/server1
Copy the EAR application to the monitored directory.
Verify that the application was successfully deployed and started in the SystemOut.log
file.
You can also verify that the application is available in the administrative console from the Applications > Application Types > WebSphere enterprise applications view.
Invoke the application using a URL in a browser.
After you deploy the application, note that the application still exists in the monitored directory. If you overwrite this file with a new file, the application is updated with your changes. However, the file must have the same name.
To uninstall the application from the server using the monitored directory, remove the
EAR file from the monitored directory. This removal triggers the monitoring service,
and the application is uninstalled. Inspect the SystemOut.log
file for information about the
application status.
Deploying an EAR file on a federated node
To install and remove an application on a federated node, you can use the same procedure as was described previously in "Deploying and removing an EAR file on a stand-alone application server". However, you use the deployment manager monitored directory instead of the stand-alone server monitored directory.
After configuring the monitored directory in deployment manager, copy the file to one of the following directories:
The directory to deploy the application on all servers named server1
dmgr_profile_root/monitoredDeployableApps/servers/server1
The directory to deploy the application only on server1
on node01
.
dmgr_profile_root/monitoredDeployableApps/nodes/node01/servers/server1
[6/4/13 6:05:53:024 EDT] 00000025 WatchService I CWLDD0007I: Event id 871388484-1. Start of processing. Event type: Added, File path: /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/monitoredDeployableApps/nodes/exampleNode01/servers/server1/DeliveryTargetPlantsByWebSphere.ear. [6/4/13 6:05:53:246 EDT] 00000025 AppManagement I CWLDD0028I: Event id 871388484-1. The target of the current operation is [WebSphere:cell=test317Cell01,node=exampleNode01,server=server1]. [6/4/13 6:05:53:266 EDT] 00000025 AppManagement I CWLDD0014I: Event id 871388484-1. Installing application PlantsByWebSphere... [6/4/13 6:05:57:324 EDT] 00000026 webcontainer I com.ibm.ws.webcontainer.internal.WebContainer addExtensionFactory SRVE0239I: Extension Factory [class com.ibm.ws.soa.sca.web.extension.SCAWebExtensionFactory] was registered successfully. [6/4/13 6:05:57:326 EDT] 00000026 webcontainer I com.ibm.ws.webcontainer.internal.WebContainer addExtensionFactory SRVE0240I: Extension Factory [class com.ibm.ws.soa.sca.web.extension.SCAWebExtensionFactory] has been associated with patterns [""]. [6/4/13 6:05:57:459 EDT] 00000026 WebSphereSCAS I Added Servlet mapping: /dojo [6/4/13 6:05:57:465 EDT] 00000026 WebSphereSCAS I Added Servlet mapping: /dojo [6/4/13 6:05:57:466 EDT] 00000026 WebSphereSCAS I Added Servlet mapping: /tuscany [6/4/13 6:05:57:467 EDT] 00000026 WebSphereSCAS I Added Servlet mapping: /tuscany [6/4/13 6:05:58:557 EDT] 00000026 InstallSchedu I ADMA5013I: Application PlantsByWebSphere installed successfully. [6/4/13 6:05:59:122 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ibm_ejbext.properties is created. [6/4/13 6:05:59:131 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/PlantsByWebSphere.ear is created. [6/4/13 6:05:59:142 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/cus/PlantsByWebSphere/cver/BASE/cu.xml is created. [6/4/13 6:05:59:145 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/web.xml is created. [6/4/13 6:05:59:146 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-webservicesclient-bnd.xmi is created. [6/4/13 6:05:59:146 EDT] 00000027 SystemOut O PLGC0051I: Plug-in configuration file generation started for the Web server. test317Cell01.exampleNode01.webserver1. [6/4/13 6:05:59:152 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/wsdl/FrontGate.wsdl is created. [6/4/13 6:05:59:165 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/META-INF/MANIFEST.MF is created. [6/4/13 6:05:59:168 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/blas/PlantsByWebSphere/bver/BASE/bla.xml is created. [6/4/13 6:05:59:175 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/META-INF/was.policy is created. [6/4/13 6:05:59:179 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ibm-ejb-jar-bnd.xmi is created. [6/4/13 6:05:59:191 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/META-INF/ibm-application-bnd.xmi is created. [6/4/13 6:05:59:192 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/META-INF/application.xml is created. [6/4/13 6:05:59:208 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/META-INF/ibm-application-runtime.props is created. [6/4/13 6:05:59:209 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-web-ext.xmi is created. [6/4/13 6:05:59:220 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsGallery.war/WEB-INF/web.xml is created. [6/4/13 6:05:59:233 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/cus/PlantsByWebSphere/cver/BASE/controlOpDefs.xml is created. [6/4/13 6:05:59:258 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/cus/PlantsByWebSphere/cver/BASE/cu-ref.xml is created. [6/4/13 6:05:59:264 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ibm-ejb-jar-ext.xmi is created. [6/4/13 6:05:59:265 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/META-INF/ibm-application-ext.xmi is created. [6/4/13 6:05:59:265 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-webservicesclient-ext.xmi is created. [6/4/13 6:05:59:268 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deltas/PlantsByWebSphere/delta-1370340356416 is created. [6/4/13 6:05:59:269 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/Table.ddl is created. [6/4/13 6:05:59:272 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-web-bnd.xmi is created. [6/4/13 6:05:59:278 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsGallery.war/META-INF/MANIFEST.MF is created. [6/4/13 6:05:59:278 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/deployment.xml is created. [6/4/13 6:05:59:281 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/META-INF/MANIFEST.MF is created. [6/4/13 6:05:59:283 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/MANIFEST.MF is created. [6/4/13 6:05:59:284 EDT] 00000025 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/PlantsByWebSphere.ear/deployments/PlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ejb-jar.xml is created. [6/4/13 6:05:59:285 EDT] 00000025 FileRepositor A ADMR0010I: Document cells/test317Cell01/nodes/exampleNode01/serverindex.xml is modified. [6/4/13 6:05:59:683 EDT] 00000025 AppManagement I CWLDD0042I: Event id 871388484-1. Synchronizing application PlantsByWebSphere to target nodes... [6/4/13 6:05:59:822 EDT] 00000025 AppManagement I CWLDD0037I: Event id 871388484-1. Synchronizing application PlantsByWebSphere to node exampleNode01. [6/4/13 6:06:00:080 EDT] 00000027 SystemOut O PLGC0060E: No applications are mapped to the Web server. [6/4/13 6:06:01:768 EDT] 0000002b AppBinaryProc I ADMA7021I: Distribution of application PlantsByWebSphere completed successfully. [6/4/13 6:06:03:346 EDT] 00000027 FileRepositor A ADMR0010I: Document cells/test317Cell01/nodes/exampleNode01/servers/webserver1/plugin-cfg.xml is modified. [6/4/13 6:06:03:358 EDT] 00000027 SystemOut O PLGC0005I: Plug-in configuration file = /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/exampleNode01/servers/webserver1/plugin-cfg.xml [6/4/13 6:06:03:359 EDT] 00000027 SystemOut O PLGC0052I: Plug-in configuration file generation is complete for the Web server. test317Cell01.exampleNode01.webserver1. [6/4/13 6:06:03:360 EDT] 00000027 SystemOut O PLGC0052I: Plug-in configuration file generation is complete for the Web server. test317Cell01.exampleNode01.webserver1. [6/4/13 6:06:03:866 EDT] 00000018 SystemOut O PLGC0062I: The plug-in configuration file is propagated from /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/test317Cell01/nodes/exampleNode01/servers/webserver1/plugin-cfg.xml to /opt/IBM/HTTPServer/Plugins/config/webserver1/plugin-cfg.xml on the Web server computer. [6/4/13 6:06:03:910 EDT] 00000018 SystemOut O PLGC0048I: The propagation of the plug-in configuration file is complete for the Web server. test317Cell01.exampleNode01.webserver1. [6/4/13 6:06:03:991 EDT] 00000025 AppManagement I CWLDD0040I: Event id 871388484-1. Application PlantsByWebSphere is synchronized to the node exampleNode01 successfully. [6/4/13 6:06:03:992 EDT] 00000025 AppManagement I CWLDD0044I: Event id 871388484-1. Application PlantsByWebSphere is synchronized to nodes successfully. [6/4/13 6:06:03:994 EDT] 00000025 AppManagement I CWLDD0047I: Event id 871388484-1. Check if application PlantsByWebSphere is ready on nodes... [6/4/13 6:06:04:602 EDT] 00000018 AppManagement I CWLDD0048I: Event id 871388484-1. Application PlantsByWebSphere is distributed completely. [6/4/13 6:06:05:028 EDT] 00000025 AppManagement I CWLDD0015I: Event id 871388484-1. Application PlantsByWebSphere is installed successfully. [6/4/13 6:06:05:035 EDT] 00000025 AppManagement I CWLDD0020I: Event id 871388484-1. Starting application PlantsByWebSphere... [6/4/13 6:06:05:080 EDT] 00000025 AdminHelper A ADMN1009I: An attempt is made to start the PlantsByWebSphere application.
Deploying an EAR file on a cluster
To install an application on a cluster, use the cluster directory in the deployment manager
monitored directory. For example, if your cluster name is cluster01
, to deploy an application to
this cluster, copy the application to the following directory:
dmgr_profile_root/monitoredDeployableApps/clusters/cluster01
To update the application, overwrite it with a new EAR file with the same name. To remove the application from cluster, delete it from the monitored directory.
Note that if a server is a member of a cluster, you cannot deploy an application by copying it to its directory.
Deploying applications and adding properties files to a monitored directory
Installing applications by copying them to a monitored directory does not change any bindings or JNDI configurations that the applications might use. To configure application resources and deploy an application using a monitored directory, use the properties file.
The monitoring service scans both the server directory and the property directory (deploymentProperties
).
If it finds a valid property file, it runs a the wsadmin.sh applyConfigProperties
command.
test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/monitoredDeployableApps # ls -al
total 24
drwxrwxrwx 6 root root 4096 Jun 4 06:04 .
drwxr-xr-x 24 root root 4096 Jun 3 17:43 ..
drwxr-xr-x 2 root root 4096 Jun 4 06:04 clusters
drwxr-xr-x 2 root root 4096 Jun 4 06:04 deploymentProperties
drwxrwxrwx 3 root root 4096 Jun 3 17:45 nodes
drwxrwxrwx 3 root root 4096 Jun 3 17:46 servers
As an example, to install an application on cluster using a property file, complete the following steps:
Create the property file that defines the deployment task that you want to complete. Sample
install_DeliveryTargetPlantsByWebSphere.properties
file:
# # Header # ResourceType=Application ImplementingResourceType=Application # Properties Name=DeliveryTargetPlantsByWebSphere TargetServer=!{serverName} TargetNode=!{nodeName} EarFileLocation=/tmp/DeliveryTargetPlantsByWebSphere.ear #TargetCluster=cluster1 EnvironmentVariablesSection # # #Environment Variables # cellName=myCell nodeName=exampleNode01 serverName=server1
test317:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01 # ls -l /tmp/*ear -rw-r--r-- 1 ilcbuild users 7649183 Nov 27 2012 /tmp/DeliveryTargetPlantsByWebSphere.ear
Ensure that the target server or cluster is running and that the monitored service is enabled and configured.
Copy the properties file to the deploymentProperties
directory in the monitored directory.
test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01 # cd monitoredDeployableApps/deploymentProperties/ test317:/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/monitoredDeployableApps/deploymentProperties # ls -l total 4 -rw-r--r-- 1 root root 350 Jun 5 17:44 install_DeliveryTargetPlantsByWebSphere.properties
WebSphere Application Server reads the property file and executes its tasks against its runtime environment. It then installs and configures the application.
[6/5/13 18:16:29:510 EDT] 00000035 WatchService I CWLDD0007I: Event id 607476514-4. Start of processing. Event type: Added, File path: /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/monitoredDeployableApps/deploymentProperties/install_DeliveryTargetPlantsByWebSphere.properties. [6/5/13 18:16:29:518 EDT] 00000035 AppManagement I CWLDD0028I: Event id 607476514-4. The target of the current operation is [WebSphere:cell=test317Cell01,node=exampleNode01 ,server=server1]. [6/5/13 18:16:29:519 EDT] 00000035 AppManagement I CWLDD0014I: Event id 607476514-4. Installing application DeliveryTargetPlantsByWebSphere... [6/5/13 18:16:29:519 EDT] 00000035 AppManagement I CWLDD0058I: Event id 607476514-4. Invoking ApplyConfigProperties command ... [6/5/13 18:16:29:538 EDT] 00000035 ConfigPropert A ADMG0820I: Start applying properties from file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/monitoredDeployableApps/deploymentProperties/install_DeliveryTargetPlantsByWebSphere.properties [6/5/13 18:16:30:267 EDT] 00000053 InstallSchedu I ADMA5013I: Application DeliveryTargetPlantsByWebSphere installed successfully. [6/5/13 18:16:30:269 EDT] 00000035 ConfigPropert A ADMG0821I: End applying properties from file /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/monitoredDeployableApps/deploymentProperties/install_DeliveryTargetPlantsByWebSphere.properties. [6/5/13 18:16:30:519 EDT] 00000038 SystemOut O PLGC0051I: Plug-in configuration file generation started for the Web server. test317Cell01.exampleNode01.webserver1. [6/5/13 18:16:30:527 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/web.xml is created. [6/5/13 18:16:30:527 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ejb-jar.xml is created. [6/5/13 18:16:30:528 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-webservicesclient-bnd.xmi is created. [6/5/13 18:16:30:571 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/cus/DeliveryTargetPlantsByWebSphere/cver/BASE/cu.xml is created. [6/5/13 18:16:30:571 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/Table.ddl is created. [6/5/13 18:16:30:572 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/META-INF/ibm-application-runtime.props is created. [6/5/13 18:16:30:572 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/META-INF/MANIFEST.MF is created. [6/5/13 18:16:30:572 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deltas/DeliveryTargetPlantsByWebSphere/delta-1370470590188 is created. [6/5/13 18:16:30:587 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-webservicesclient-ext.xmi is created. [6/5/13 18:16:30:588 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/META-INF/MANIFEST.MF is created. [6/5/13 18:16:30:588 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ibm-ejb-jar-bnd.xmi is created. [6/5/13 18:16:30:588 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsGallery.war/WEB-INF/web.xml is created. [6/5/13 18:16:30:589 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-web-bnd.xmi is created. [6/5/13 18:16:30:589 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/META-INF/application.xml is created. [6/5/13 18:16:30:590 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/META-INF/was.policy is created. [6/5/13 18:16:30:590 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/blas/DeliveryTargetPlantsByWebSphere/bver/BASE/bla.xml is created. [6/5/13 18:16:30:590 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsGallery.war/META-INF/MANIFEST.MF is created. [6/5/13 18:16:30:591 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/META-INF/ibm-application-ext.xmi is created. [6/5/13 18:16:30:591 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/MANIFEST.MF is created. [6/5/13 18:16:30:592 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ibm_ejbext.properties is created. [6/5/13 18:16:30:592 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/deployment.xml is created. [6/5/13 18:16:30:615 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/cus/DeliveryTargetPlantsByWebSphere/cver/BASE/controlOpDefs.xml is created. [6/5/13 18:16:30:616 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/wsdl/FrontGate.wsdl is created. [6/5/13 18:16:30:616 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphere.war/WEB-INF/ibm-web-ext.xmi is created. [6/5/13 18:16:30:617 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/META-INF/ibm-application-bnd.xmi is created. [6/5/13 18:16:30:617 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/deployments/DeliveryTargetPlantsByWebSphere/PlantsByWebSphereEJB.jar/META-INF/ibm-ejb-jar-ext.xmi is created. [6/5/13 18:16:30:617 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/cus/DeliveryTargetPlantsByWebSphere/cver/BASE/cu-ref.xml is created. [6/5/13 18:16:30:619 EDT] 00000035 FileRepositor A ADMR0009I: Document cells/test317Cell01/applications/DeliveryTargetPlantsByWebSphere.ear/DeliveryTargetPlantsByWebSphere.ear is created. [6/5/13 18:16:30:624 EDT] 00000035 FileRepositor A ADMR0010I: Document cells/test317Cell01/nodes/exampleNode01/serverindex.xml is modified. [6/5/13 18:16:30:688 EDT] 00000035 AppManagement I CWLDD0042I: Event id 607476514-4. Synchronizing application DeliveryTargetPlantsByWebSphere to target nodes... [6/5/13 18:16:30:728 EDT] 00000035 AppManagement I CWLDD0037I: Event id 607476514-4. Synchronizing application DeliveryTargetPlantsByWebSphere to node exampleNode01 . [6/5/13 18:16:30:736 EDT] 00000035 AppManagement I CWLDD0039W: Event id 607476514-4. Unable to synchronize application DeliveryTargetPlantsByWebSphere to node exampleNode01 because the node agent is not running. [6/5/13 18:16:30:737 EDT] 00000035 AppManagement I CWLDD0045I: Event id 607476514-4. Failed to synchronize application DeliveryTargetPlantsByWebSphere. [6/5/13 18:16:30:738 EDT] 00000035 AppManagement I CWLDD0047I: Event id 607476514-4. Check if application DeliveryTargetPlantsByWebSphere is ready on nodes... [6/5/13 18:16:30:790 EDT] 00000038 SystemOut O PLGC0060E: No applications are mapped to the Web server. [6/5/13 18:16:30:932 EDT] 00000057 AppBinaryProc I ADMA7021I: Distribution of application DeliveryTargetPlantsByWebSphere completed successfully. [6/5/13 18:16:31:008 EDT] 00000045 AppManagement I CWLDD0048I: Event id 607476514-4. Application DeliveryTargetPlantsByWebSphere is distributed completely. [6/5/13 18:16:31:058 EDT] 00000038 FileRepositor A ADMR0010I: Document cells/test317Cell01/nodes/exampleNode01/servers/webserver1/plugin-cfg.xml is modified. [6/5/13 18:16:31:059 EDT] 00000038 SystemOut O PLGC0005I: Plug-in configuration file = /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/test317Cell01/nodes/exampleNode01/servers/webserver1/plugin-cfg.xml [6/5/13 18:16:31:061 EDT] 00000038 SystemOut O PLGC0052I: Plug-in configuration file generation is complete for the Web server. test317Cell01.exampleNode01.webserver1. [6/5/13 18:16:31:062 EDT] 00000038 SystemOut O PLGC0052I: Plug-in configuration file generation is complete for the Web server. test317Cell01.exampleNode01.webserver1. [6/5/13 18:16:31:753 EDT] 00000035 AppManagement I CWLDD0020I: Event id 607476514-4. Starting application DeliveryTargetPlantsByWebSphere... [6/5/13 18:16:31:753 EDT] 00000035 AppManagement I CWLDD0035W: Event id 607476514-4. Unable to start application DeliveryTargetPlantsByWebSphere on target server: server1 because the node agent exampleNode01 is not running. [6/5/13 18:16:31:753 EDT] 00000035 AdminHelper A ADMN1009I: An attempt is made to start the DeliveryTargetPlantsByWebSphere application.
Note that if you remove the property file from the monitored directory, the monitoring service notices this event but will not uninstall the application.
To update an application, you can copy the property file and overwrite an existing property file (if not deleted). This action triggers the monitoring service to reinstall the application.
You have to uninstall an application manually or prepare a property file with uninstallation instructions.
![]() ![]() ![]() |