Wednesday, April 3, 2013

Setting up WebLogic as a Windows Service

A common requirement when dealing with any application server install on Windows is to set it up as a Windows service.  It's a bad idea to rely on the command line for running the server as it makes it far harder to administer.

For WebLogic the steps to do this are available on Oracle's website:
http://docs.oracle.com/cd/E11035_01/wls100/server_start/winservice.html

A useful diagnostic if the service doesn't appear to be working is to try and invoke the service using the beasvc command.  See the section "Verifying the Setup" in the above link for more information.  More times than not if your service isn't starting then there was an error in the script you used to create the service in the first place (e.g. JVM argument).

Friday, March 1, 2013

JS Libraries

Below is a list of libraries I've come across which in all my reading and investigation recently into HTML5 / JS which should come in handy.  More of a "remember these for later" post:

  • http://underscorejs.org/
  • http://modernizr.com/
  • http://angularjs.org/
  • http://qunitjs.com/
  • http://momentjs.com/
  • http://requirejs.org/ (and http://requirejs.org/docs/api.html#text)
  • http://html5boilerplate.com/
  • http://fortawesome.github.com/Font-Awesome/
  • http://blueimp.github.com/jQuery-File-Upload/
For more popular projects GitHub's starred repository list is a good place to start (gives an idea of highly active/popular projects):
  • https://github.com/popular/forked
  • https://github.com/popular/starred

Monday, January 14, 2013

Vertical clustering in LiveCycle ES3

Quick note for future reference: the document for ES2 (http://help.adobe.com/en_US/livecycle/9.0/clustering_jboss.pdf) explains how to change the necessary ports in order to get a vertical JBoss cluster up and running.  In ES3 (and therefore JBoss 5) the paths for a number of the ports has changed:

JBoss 4:
jboss-service.xml file located in [appserver root]\server\[profile]\conf

JBoss 5:
bindings-jboss-beans.xml file located in [appserver root]\server\[profile]\conf\bindingservice.beans\META-INF