[jheadley]

I’m am having two issues using MyEclipse to deploy and run a project on WebLogic 9 (latest version released this week). MyEclipse starts the server just fine, but won’t stop it. I get the message that it can’t find this file:

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Problem invoking WLST - java.io.FileNotFoundException: C:\bea\user_projects\domains\base_domain\shutdown.py (The system cannot find the file specified)

That file shutdown.py doesn’t exist anywhere under C:\bea.

My second issue is that it deploys to the applications folder and WL 9 doesn’t seem to recognize it being there. It seems to deploy it when I move what MyEclipse created to the autodeploy folder.

Thanks,
Jeff

What operating system and version are you running? Windows 2000

What Eclipse version and build id are you using? (Help > About Eclipse Platform) Version: 3.1.0
Build id: I20050627-1435

– Was Eclipse freshly installed for MyEclipse? Yes

– Are any other external plugins installed? Subclipse

– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.* 9

What MyEclipse version are you using? (Help > About Eclipse Platform > Features) Version: 3.9.211
Build id: 20050627-4.0-Milestone-2

What JDK version are you using to run Eclipse? (java -version) 1.5
What JDK version are you using to launch your application server? 1.5

What steps did you take that resulted in the issue? Configured WL 9

[Scott Anderson]

Jeff,

To correct the shutdown issue, you’ll need to start and stop your weblogic domain one time using BEA’s commandline tools that were installed in the bin subdirectory under your domain when you created it. Just run startWebLogic.cmd and after startup run stopWebLogic.cmd. This initial execution and shutdown will create the shutdown.py file that is needed for the MyEclipse connector to work from that point forward.

My second issue is that it deploys to the applications folder and WL 9 doesn’t seem to recognize it being there.

This is caused by a change between the final beta of WLS9 and the final release. We’ve corrected the problem internally already and it will be part of the 4.0M3 build. As a workaround, you can simply use a “Custom Location” as the deployment target and specify the autodeploy folder instead of the one the connector wants to use (which worked in the beta but is now wrong).

[jheadley]

That took care of both issues. Thanks for the quick reply.

[Author]

Posts