admin.jar Usage

In this section we'll cover the purpose, location, common usage, and syntax for the admin.jar utility.

Purpose

Used to manage J2EE application deployments to OC4J Standalone Edition. It can be used to deploy, bind, or undeploy applications. It is also used to stop and start the OC4J server.

Location

Located in the OC4J standalone $ORACLE_HOME/j2ee/home directory.

Common Usages

Common usages for admin.jar are shown in the following sections.

Application deployment

 $ java -jar admin.jar ormi://192.168.1.11:11888 admin tigerpassword -deploy -file petstore.ear -deploymentName petstore 

Binding application to URI

 $ java -jar admin.jar ormi://192.168.1.11:11888 admin tigerpassword -bindWebApp petstore petstore http-web-site /petstore 

Undeployment

 $ java -jar admin.jar ormi://192.168.1.11:11888 admin tigerpassword -undeploy petstore 

Starting server

 $ java -jar oc4j.jar -config $ORACLE_HOME/j2ee/home/config/server.xml -verbosity 10 -err $ORACLE_HOME/j2ee/home/log/err.log 

Stopping server

 $ java -jar admin.jar ormi://mike.wessler.name:11888 admin tigerpassword -shutdown 

Syntax

To get a list of available arguments, issue java -jar admin.jar help , as follows :

 $ java -jar admin.jar -help Usage: java -jar admin.jar [-help] - print out this usage java -jar admin.jar ormi://host.domain.com<:port> username password [command] Commands are: -shutdown [forceordinary] [reason] - shuts the entire server down -restart [reason] - restarts the entire server -deploy [subswitches] - (re)deploys an application. Sub-switches are:    -file [filename] - Enterprise Archive to deploy    -deploymentName [name] - Name of the application deployment    -targetPath [path] - The path on the remote OS to place the archive at. If not specified the applications directory is used    -parent [name] - Specifying parent application of this application,  the default is the global ('default') application    -deploymentDirectory [path] - Root of the deployment configurations, "[NONE]" to place them inside the .ear    -cluster - Signals that the deployment should be propagated to other live cluster nodes if part of a cluster    -iiopClientJar - the path on the local OS to place the jar file containing the application client stubs -undeploy [application name] - remove a previously deployed application -site [subswitches] - configures a site. Sub-switches are:    -add - adds a site       -host [host] - host/IP of this site       -port [port] - port of this site       -display-name [display-name] - display name of this site       -virtual-hosts [virtual-hosts] - virtual hosts of this site       -secure [secure] - true if this site is secure; otherwise false       -factory [factory] - name of SSLServerSocketFactory implementation if not using JSSE       -keystore [keystore] - the relative/absolute path to a keystore used by this site       -storepass [storepass] - keystore password       -provider  [provider] - the provider used if not using JSSE       -needs-client-auth [needs-client-auth] - true if needs client auth;  otherwise false    -remove - removes a site       -host [host] - host/IP of the site to be removed       -port [port] - port of the site to be removed    -test - tests a site       -host [host] - host/IP of the site to be tested       -port [port] - port of the site to be tested    -list - lists all sites    -update - updates a site       -oldHost [host] - old host/IP of this site       -oldPort [port] - old port of this site       -newHost [host] - new host/IP of this site       -newPort [port] - new port of this site       -display-name [display-name] - display name of this site       -virtual-hosts [virtual-hosts] - virtual hosts of this site       -secure [secure] - true if this site is secure; otherwise false       -factory [factory] - name of SSLServerSocketFactory implementation if not using JSSE       -keystore [keystore] - the relative/absolute path to a keystore used by this site       -storepass [storepass] - keystore password       -provider [provider] - the provider used if not using JSSE       -needs-client-auth [needs-client-auth] - true if needs client auth; otherwise false -bindWebApp [application deployment name] [web-app name] [web-site name]  [context root] - binds a web app to the specified site + root -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 enabled and a file has been touched    -addUser [username] [password] - adds a user to the application    -listDataSource - lists the installed datasources    -removeDataSource - removes an existing datasource, arguments are:       -location [location] - the namespace location for the source, for instance jdbc/DefaultDS    -testDataSource - tests an existing datasource, arguments are:       -location [location] - the namespace location for the source, for instance jdbc/DefaultDS       -username [username] - the username to login       -password [password] - the password to login    -installDataSource - installs a new datasource, arguments are:       -jar [path] - path to a jar file to add to the server's library       -url [url] - the JDBC database URL       -location [location] - the namespace location for the raw source, for instance jdbc/DefaultRawDS       -pooledLocation [pooledLocation] - the namespace location for the pooled source, for instance jdbc/DefaultPooledDS       -xaLocation [xaLocation] - the namespace location for the XA source, for instance jdbc/xa/DefaultXADS       -ejbLocation [ejbLocation] - the namespace location for the EJB source, for instance jdbc/DefaultEJBDS - this is the source usually used by applications       -username [username] - the username to login       -password [password] - the password to login       -connectionDriver [drivername] - the JDBC database driver class, for instance com.mydb.Driver       -className [className] - the datasource class name, for instance com.evermind.sql.DriverManagerDataSource       -sourceLocation [sourceLocation] - the underlying data source of this specialized data source       -xaSourceLocation [xaSourceLocation] - the underlying XADataSource of this specialized data source    -updateDataSource - updates an existing datasource, arguments are:       -oldLocation [oldLocation] - the old namespace location for the source, for instance jdbc/DefaultDS       -newLocation [newLocation] - the new namespace location for the source, for instance jdbc/DefaultDS       -jar [path] - path to a jar file to add to the server's library       -url [url] - the JDBC database URL       -pooledLocation [pooledLocation] - the namespace location for the pooled source, for instance jdbc/DefaultPooledDS       -xaLocation [xaLocation] - the namespace location for the XA source, for instance jdbc/xa/DefaultXADS       -ejbLocation [ejbLocation] - the namespace location for the EJB source, for instance jdbc/DefaultEJBDS - this is the source usually used by applications       -username [username] - the username to login       -password [password] - the password to login       -connectionDriver [drivername] - the JDBC database driver class, for instance com.mydb.Driver       -className [className] - the datasource class name, for instance com.evermind.sql.DriverManagerDataSource       -sourceLocation [sourceLocation] - the underlying data source of this specialized data source       -xaSourceLocation [xaSourceLocation] - the underlying XADataSource of this specialized data source -deployconnector - deploy a Connector Architecture compliant resource adapter (RAR), arguments are:    -file [path] - path to the Resource Adapter Archive to deploy    -name [name] - name of the resource adapter deployment    -nativeLibPath [path] - path to the native libraries within the RAR archive    -grantAllPermissions - grant all runtime permissions requested by the RAR -undeployconnector - undeploy a Connector Architecture compliant resource adapter (RAR), arguments are:    -name [name] - name of the resource adapter deployment -updateConfig - trigger oc4j server to check the configuration file changes $ 


Oracle Application Server 10g. J2EE Deployment and Administration
Oracle Application Server 10g: J2EE Deployment and Administration
ISBN: 1590592352
EAN: 2147483647
Year: 2004
Pages: 150

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net