Weblogic workshop

1)Weblogic workshop debug flags:


Two ways to enable more logging for IDE:

a) Workshop.exe internally invokes workshop.cfg file, which is present in the {BEAHOME}\weblogic81\workshop directory. This file by default uses javaw, which suppresses the command window for the IDE process. Modifying this to use java instead causes the command window to appear. This window enables users to take a thread dump of the IDE process. This can be done by hitting Ctrl - Break on the command window.

b) Another option is to enable logging for the IDE. This can be done by adding the following entry to the workshop.cfg file.
-Dworkshop.enablelogging=true
sample workshop.cfg file

D:\bea\8platsp2\weblogic81\workshop
D:\bea\8platsp2\jdk141_05\jre\bin\java.exe
-XX:-UseThreadPriorities -Xmx256m -Xms64m -Xss256k -Dworkshop.enablelogging=true -client -Dsun.java2d.noddraw=true -Dsun.java2d.d3d=false - Djava.system.class.loader="workshop.core.AppClassLoader" -cp "D:\bea\8platsp2\weblogic81\workshop\wlw-ide.jar" workshop.core.Workshop

2) Process to take thread dumps on Workshop:

By default the Workshop.cfg file, which is used by the Workshop.exe file in the //workshop directory, uses javaw.exe to start the IDE process.

Changing this to java.exe will open an additional shell window along with the IDE itself, which will show the debug messages generated by the process.

Pressing a Ctrl-Break on this shell window on Windows, or doing a 'kill -3' for the IDE process on Linux, will throw a thread dump for the process on the shell window.

3) Steps to initialize all the plugins in Weblogic Workshop:

Step1: Stop the workshop (if it running)

Step2: Go to command prompt

Step3: Move to %workshopHome% directory where you find workshop.exe file

Step4: Run the following command

>Workshop.exe –clean –initialize

Step5: Start the workshop

>Workshop.exe