Archive

Archive for January, 2012

Starting Coherence servers using Node Manager

January 30, 2012 Leave a comment

Once you have created the Coherence servers in your domain, you should be able to manage their lifecycle using the Node Manager, just like with Weblogic managed servers. Of course, for this to work a Coherence server must be assigned to a machine within the Weblogic domain. The Coherence servers can then be started:

  • from the Administration console, by navigating to the “Control” tab and clicking “Start” for the selected servers
  • from WLST, by the following command:

nmConnect(‘weblogic’,’welcome1′,’localhost’,’5556′,’FMW_XPS’,’/shared/oracle/FMW_Home/user_projects/domains/FMW_XPS’,’plain’)

nmStart(‘coh_server1′,serverType=’Coherence’)

Read more…

Advertisements

WebLogic AdminServer startup and shutdown scripts

January 15, 2012 Leave a comment

Right after creating a WebLogic domain, you can navigate to the domain directory and start the administration server using the startWebLogic.sh script. However, for easier control over the administration server of your domain, you can create some WLST startup and shutdown scripts that manage your admin server via the Node Manager.

The solution below describes two WLST scripts (startAdmin.jy and stopAdmin.jy ) and two platform dependent scripts that you use to call the Jython ones. (startAdmin.sh and stopAdmin.sh for Unix or startAdmin.bat and stopAdmin.bat for Windows)

Read more…

Cannot connect to Node Manager. : Access to domain for user ‘weblogic’ denied

January 15, 2012 2 comments

If you’ve hit this error you are probably trying to control your Weblogic servers via WLST, but you are unable to connect to the Node Manager.

nmConnect(‘weblogic’,’welcome1′,’localhost’,’5556′,’FMW_XPS’,’/shared/oracle/FMW_Home/user_projects/domains/FMW_XPS’,’plain’)
Connecting to Node Manager …
Traceback (innermost last):
File “”, line 1, in ?
File “”, line 123, in nmConnect
File “”, line 648, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Access to domain ‘FMW_XPS’ for user ‘weblogic’ denied.
Use dumpStack() to view the full stacktrace

Assuming you’ve already made sure all the parameters in the nmConnect command are correct and the NM process is up and running, there is actually one more thing to check: has your domain been set up in Production Mode? If so, then the Node Manager credentials have been generated by the Configuration Wizard at domain creation time. While the AdminServer will be aware of these credentials by default (you are able to connect to the NM via de admin console, after all), you will not be able to connect via WLST since you have to provide this random username and password. The solution is to reset the credentials in the Administration Console.

Read more…

Node Manager as Linux service and Weblogic server autorestart

January 5, 2012 5 comments

In order to have Node Manager start automatically it must be configured as a daemon. In order to do that, edit the below script to reflect your Weblogic installation path, then save it under /etc/init.d/nodemgr and run ‘chkconfig –add nodemgr’ as root.

Read more…

Sending emails via command line

January 5, 2012 Leave a comment

If you are trying to set up email notification in Weblogic and your emails are not getting through to your inbox, it might be nothing wrong with your application server configurations, but rather a problem with the email server itself. To test if a regular mail is being sent without having to configure a mail client with that server, you can use the steps below to send an email via command line: Read more…