WebSphere Process Server serviceDeploy debug options

You can debug the serviceDeploy utility which comes with WebSphere Process Server (or WebSphere Integration Developer). Unfortunately I could not find what we should give in options file.

servicedeploy -help

serviceDeploy inputArchive [options]

Options:
-workingDirectory dir A directory in which to generate temporary files. Default=.
-outputApplication app.ear The path and name of the deployed ear. Default=[inputArchive]App.ear
-noJ2eeDeploy Whether the j2ee deployers, including ejbdeploy, should be skipped. Default=false
-noJavaSource Whether the Java source files should be excluded from the generated ear. Default=false
-freeform Whether a j2ee subdirectory in the service jar should be free-form enabled. Default=false
-cleanStagingModules Whether the staging modules in an input ear file should be deleted and recreated during deploy. Default=false
-keep Whether the temporary workspace in the working directory should be preserved after deploy. Default=false
-ignoreErrors Whether an ear file should be exported despite compile or validation errors. Default=false
-classpath x.jar;y.rar A list of jars and rars required on the classpath
-uniqueCellID Unique ID in the context of the cell that is used to create a unique instance of the application.
-progressMonitor type Whether and how progress should be monitored. Type may be one of [none|meter|message]. Default=none
-fileEncoding encoding The default file encoding for the workspace root. Default is unspecified.
-debug optionsFile An options file that enables eclipse trace.
-javaDebug Whether all debug information should be included in generated class files.

After long hours on google, I found it's documented in IBM Education: component deployment with ServiceDeploy (link).

You can try below as your options file; Of course, best is to get assistance from IBM service, and use the options at your own risk.

org.eclipse.jdt.core/debug=true
org.eclipse.jdt.core/debug/builder=true
org.eclipse.jdt.core/debug/trace=true
com.ibm.ws.sca.rapiddeploy.style/debug=true
com.ibm.ws.sca.rapiddeploy.style/debug/trace=true
com.ibm.ws.sca.rapiddeploy.style/debug/event=true
com.ibm.ws.sca.rapiddeploy.style/debug/info=true
com.ibm.ws.sca.rapiddeploy.headless/debug=true
com.ibm.ws.sca.rapiddeploy.headless/debug/trace=true
com.ibm.ws.sca.rapiddeploy.headless/debug/event=true
com.ibm.ws.sca.rapiddeploy.headless/debug/info=true
com.ibm.ws.artifact.locator/debug=true
com.ibm.ws.artifact.locator/debug/trace=true
com.ibm.ws.artifact.locator/debug/event=true
com.ibm.ws.artifact.locator/debug/info=true
com.ibm.ws.artifact.locator/debug/dump=true
com.ibm.ws.sca.rapiddeploy.headless.HeadlessServiceDeploy/debug=true
com.ibm.ws.sca.rapiddeploy.headless.HeadlessServiceDeploy/debug/trace=true
com.ibm.ws.sca.rapiddeploy.headless.HeadlessServiceDeploy/debug/event=true
com.ibm.ws.sca.rapiddeploy.headless.HeadlessServiceDeploy/debug/info=true

Ex:
serviceDeploy InputArchive.zip -keep -debug options.txt

Eclipse unsatisfied link error on AIX when configuring WebSphere Process Server 6.2 using firststeps

Today I was getting below exception when attempting to configure WPS 6.2 on AIX 5.3

!SESSION 2009-08-20 09:18:24.624 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223ifx-20090225 (JIT enabled)
J9VM - 20090224_30451_bHdSMr
JIT - 20081112_1511ifx1_r8
GC - 200811_07
BootLoader constants: OS=aix, ARCH=ppc, WS=motif, NL=en_US
Framework arguments: -jar startup.jar
Command-line arguments: -jar startup.jar -os aix -ws motif -arch ppc -clean

!ENTRY org.eclipse.osgi 4 0 2009-08-20 09:18:27.796
!MESSAGE Application error
!STACK 1
java.lang.UnsatisfiedLinkError: /shome/wasadmin/PMT/workspace/configuration/org.eclipse.osgi/bundles/24/1/.cp/libswt-motif-3236.a ( 0509-022 Cannot load m
odule /shome/wasadmin/PMT/workspace/configuration/org.eclipse.osgi/bundles/24/1/.cp/libswt-motif-3236.a.
0509-150 Dependent module libXtst.a(shr.o) could not be loaded.
0509-022 Cannot load module libXtst.a(shr.o).
0509-026 System error: A file or directory in the path name does not exist.
0509-022 Cannot load module /shome/wasadmin/PMT/workspace/configuration/org.eclipse.osgi/bundles/24/1/.cp/libswt-motif-3236.a.
0509-150 Dependent module /shome/wasadmin/PMT/workspace/confi)
at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:986)
at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:946)
at java.lang.System.loadLibrary(System.java:453)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:123)


It turn out to be missing package on AIX server... Installing X11.add.lib might resolve the issue



lslpp -f X11.adt.lib
Fileset File
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
X11.adt.lib 5.3.0.0 /usr/lib/libttf.a -> /usr/lpp/X11/lib/libttf.a
X11.adt.lib 5.3.0.0 /usr/lpp/X11/lib/libxkbfile.a
/usr/lib/libxkbfile.a -> /usr/lpp/X11/lib/libxkbfile.a
/usr/lpp/X11/lib/R6/libXtst.a
/usr/lpp/X11/lib/libXdmcp.a
/usr/lpp/X11/lib/libXau.a
/usr/lib/libkap.a -> /usr/lpp/X11/lib/libkap.a
/usr/lpp/X11/lib/libttf.a
/usr/lpp/X11/lib/R6
/usr/lib/libXtst.a -> /usr/lpp/X11/lib/R6/libXtst.a
/usr/lib/libXau.a -> /usr/lpp/X11/lib/libXau.a
/usr/lib/libXdmcp.a -> /usr/lpp/X11/lib/libXdmcp.a
/usr/lpp/X11/lib/libkap.a

WID 6.0.2 custom mediaiton premitive and migration to WID 6.2

I have used custom mediation primitive in WID 6.0.2 with implementation "invoke". When moved the code to WID 6.2 custome mediation primitive has only two types of implementations 1) Visual and 2) java. Previously coded custom mediation primitives are converted to simple java implementation with service lookup and service.invoke("operationName", argument)

At this moment, this may fail on runtime with argument smo.getBody(); not all times this may work. In such case use service invoke primitive which is introduced in WID 6.2