-->

Adsense Right Sidebar

Iklan

Problem with publishing WC application

Recently I was stuck with a chicken and Egg problem with publishing WC application on my toolkit test server, essentially it was throwing following error at publish

com.ibm.websphere.management.exception.AdminException: A composition unit with name WC already exists. Select a different application name. 


I was able to find this tech link which provides steps to overcome this issue, but this tech. note is not complete and in this blog I will compliment it with few additional steps.


Step 1
Stop the test server

Step 2
Backup and remove following directories, I just did a "Delete" instead of "Shift + delete" this way I can restore these files from my trash

- WCDE_installdir/wasprofile/config/cells/localhost/cus
- WCDE_installdir/wasprofile/config/cells/localhost/blas
- WCDE_installdir/wasprofile/wstemp
- WCDE_installdir/wasprofile/temp
- WCDE_installdir/wasprofile/config/temp


Step 3


Start the server and publish again, this step will only publish WC application, the technote does not talk about how to restore WAS admin console and cachemonitor application.
Step 4 is in addition to tech note.


Step 4


After completing Step 4 you will be able to launch WC application, you have two options to restore the WAS admin console application and Cachemonitor.

Step 4.a

Follow these steps to Uninstall/re-install WAS admin console


If you get an error which indicates isclite is already installed as follows then uninstall it first as shown in next before re-installing.



*sys-package-mgr*: processing new jar, 'C:\IBM\SDP\runtimes\base_v7\deploytool\i
tp\plugins\com.ibm.etools.ejbdeploy\runtime\ejbmapvalidate.jar'
WASX7209I: Connected to process "server1" on node localhost using SOAP connector
;  The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are
 available as arguments that are stored in the argv variable: "[install]"
Installing Admin Console...
Deploying isclite.ear
Admin console is already installed.
Skipping Config Save

C:\IBM\WCDE_ENT70\wasprofile\bin>wsadmin.bat -f deployConsole.py remove
WASX7209I: Connected to process "server1" on node localhost using SOAP connector
;  The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are
 available as arguments that are stored in the argv variable: "[remove]"
Removing Admin Console...
ADMA5017I: Uninstallation of isclite started.
ADMA5104I: The server index entry for WebSphere:cell=localhost,node=localhost is
 updated successfully.
ADMA5102I: The configuration data for isclite from the configuration repository
is deleted successfully.
ADMA5011I: The cleanup of the temp directory for application isclite is complete
.
ADMA5106I: Application isclite uninstalled successfully.

Do a clean and publish from test server to restore the newly deployed application and you should be able to access WAS admin console now.


Now Deploy cache monitor by following instructions from my previous post

You would notice following error while starting cache monitor, uninstall and re-install cache monitor based on the steps from my previous blog

http://techhari.blogspot.com/2010/08/monitor-wcs-cache_30.html



Step 4.b

An alternate to step 4.a is to restore all of the folder which were deleted in Step 2, this will restore the previous configuration.
BERIKAN KOMENTAR ()
 
wisata tradisi game kuliner