[trilcejf]

Hello there, i have a problem starting WAS 6.0 from Server’s view of MyEclipse IDE 5.1.1.
My configuration:
Websphere home dir: C:\Archivos de programa\IBM\WebSphere
Profile root dir: C:\Archivos de programa\IBM\WebSphere\AppServer\profiles\MyEclipse
Node name: MyEclipseNode
Cell name: trilcejfNode01Cell
Server name: server1
DB2J System dir: C:\Archivos de programa\IBM\WebSphere\AppServer\cloudscape
[i think here is the problem] ITP dir: C:\Archivos de programa\IBM\WebSphere\AppServer\bin[i think here is the problem]
Security policy: C:\Archivos de programa\IBM\WebSphere\AppServer\profiles\MyEclipse\properties\server.policy
Security conf: C:\Archivos de programa\IBM\WebSphere\AppServer\profiles\MyEclipse\properties\wsjaas.conf
Output encoding: console

Error message: “A configuration error ocurred during startup. Please verify the preferences field with the prompt: Specified working directory: C:\Archivos de programa\IBM\WebSphere\AppServer\bin”
I have tried:
ITP dir: C:\Archivos de Programa\IBM\WebSphere\AppServer\profiles\MyEclipse\bin
but it doesnt run

When i start the server alone without Myeclipse IDE it runs ok

Thanks in advance. Any suggestion will be wellcome

[Scott Anderson]

Have you had a look at our tutorial on configuring WebSphere 6? I think it has the information you’re looking for to get you up and running. It’s available here: http://www.myeclipseide.com/images/tutorials/quickstarts/websphere6/

[trilcejf]

Hello, i have read documentation. My conf is based in it, but the server doesnt startup. I am using Websphere Application Server with Network Deployment. Could this issue affect??
Thanks in advance

[Scott Anderson]

I’m not familiar with the “Network Deployment” version but that could be the issue. It may simply need different startup parameters than the “plain” WebSphere 6.0. However, before we dig deeper, please compare your configuration to this one from the FAQ: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-13944.html and ensure you’re using the JDK shipped with WebSphere 6.0 to start it on the WebSphere 6 > JDK preference page since it definately won’t start with a non-IBM JDK.

If those are all OK, I think we can still figure out how to do it. To find out exactly what is being used to start WebSphere 6.0, you can create a launch configuration and compare it to what the startup script is using.

To generate the launch configuration, navigate to Window > Preferences > MyEclipse > Application Servers > WebSphere 6 > Launch. Press the ‘Create Launch Configuration’ button. When the dialog comes up, set the name of the configuration and save it.

To generate a script that launches your instance of WebSphere from the commandline, go to an external command prompt (shell window). Before generating script, turn on debugging in the domain by starting from the commandline and using the console. Verify debugging is on by checking the profile in profiles\default\config\cells\[your cell name]Node01Cell\nodes\[your node name]Node01\servers\server1\server.xml
and look for the jvmEntries line – the debugMode entry should be set to true and have a similar debugArgs setup:
<jvmEntries xmi:id=”JavaVirtualMachine_1099753628812″ … debugMode=”true” debugArgs=”-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777″ …/>

Generate the script to start the server using something like:
startServer.bat server1 -script startDefault.bat -profileName default

Now, you can compare the settings in the launch configuration (Under Run > Debug… ) that you created earlier with the settings in the script you just created. Pay particular attention to any additional jar files on the classpath as this is likely the difference.

[Author]

Posts