Tools Overview

Orion comes with a number of tools. This article describe which these are and how they are started.



1 Introduction

    This article describes the tools distributed with the Orion Application Server.

2 Reference table

    The tools distributed with the Orion Application Server can be found in the table below:

    Tool exectuableDescriptionUsage/Parameters
    orion.jarMain server-install installs the server, activates the admin account and rewrites text fi les to match the OS linefeed
    -quiet surpress standard output
    -userThreads enables context lookup support from user-created threads
    -config specifies a location to server.xml
    -console launches the admin console in-process
    -validateXML valides (strictly) the XML files when reading them.
    -out [file] specifies a file to route standard output to
    -err [file] specifies a file to route error output to
    -version Prints the version and exits.
    -? -help prints help message
    orionconsole.jarOrion management console
    taglibassembler.jarThe graphical tool for assembling tag extension librariesOptional path to taglib
    webappassembler.jarThe graphical tool for assembling Web applicationsOptional path to web-application
    ejbassembler.jarThe graphical tool for assembling EJB JarsOptional path to EJB module
    clientassembler.jarThe graphical tool for assembling application clientsOptional path to application client
    earassembler.jarThe graphical tool for assembling J2EE applicationsOptional path to j2ee application
    ejbmaker.jarGraphical CMP EJB creation tool
    applicationlauncher.jarLaucher for remote (or local) application clientsApplicationlauncher.jar ormi://rmi.thehost.com/application/clientApplicationName username password
    assemblerlauncher.jarPath to module/application to assemble
    loadbalancer.jarLoad balancer, See clustering-config path to the load-balancer.xml config file, the default is config/load- balancer.xml
    -host host/address to listen to for HTTP connections
    -port port to listen to for HTTP connections
    -dontUseSessionID specifies the balancer not to scan for Servlet session IDs as a means of identifying clients (useful when for instance balancing SSL sites)
    -dontUseIP specifies the balancer not to route connections based on IP if no session exists/is scanned for
    -dontUseKeepAlives specifies the balancer not to maintain keep-alives. This is useful if number of open sockets/used threads is a problem on the balancer but it will increase network traffic and CPU usage (and slow down client requests).
    -minimumIsland the minimum island to add to alive servers list, useful when using several balancer instances
    -maximumIsland the maximum island to add to alive servers list, useful when using several balancer instances
    -selectiontype how to select servers, the default is random, options are: 'random', 'first'
    admin.jarAdministration tooladmin.jar ormi://host.domain.com<:port> username password [command]
    Commands are:
    -shutdown shuts the entire server down
    -restart restarts the entire server
    -deploy (re)deploys an application. Sub-switches are:
    -file Enterprise Archive to deploy
    -deploymentName Name of the application deployment
    -targetPath The path on the remote OS to place the archive at. If not speciied the applications directory is used
    -bindWebApp [application deployment name] [web-app name] [web-site name] [contex t root] binds a web app to the specified site + root
    -installDataSource Installs a new datasource, arguments are:
    -jar path to a jar file containing the driver to add to the server's library
    -url the JDBC database URL
    -location the namespace location for the raw source, for instance jdbc/Defa ultRawDS
    -pooledLocation the namespace location for the pooled source, for instance jdbc/DefaultPooledDS
    -xaLocation the namespace location for the XA source, for instance jdbc/xa/ DefaultXADS
    -cmtLocation the namespace location for the CMT source, for instance jdbc/DefaultDS - this is the source usually used by applications
    -username the username to log in with
    -password the password to log in with
    -application the application to install the source in, the default is the gobal application
    -connectionDriver the JDBC database driver class, for instance 'com.mydb.Driver'
    -application [name] [command] application specific command, subcommands includes:
    -dataSourceInfo gets info about the installed datasources
    -restart restarts the application, this will trigger auto-deployment if ena bled and a file has been touched
    -addUser [username] [password] adds a user to the application
    Table 1: The tools distributed with the Orion Application Server

Copyright 2003 IronFlare AB