From scm-return-46845-apmail-geronimo-scm-archive=geronimo.apache.org@geronimo.apache.org Tue Jul 19 03:33:41 2011 Return-Path: X-Original-To: apmail-geronimo-scm-archive@www.apache.org Delivered-To: apmail-geronimo-scm-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3DD746308 for ; Tue, 19 Jul 2011 03:33:41 +0000 (UTC) Received: (qmail 56607 invoked by uid 500); 19 Jul 2011 03:33:40 -0000 Delivered-To: apmail-geronimo-scm-archive@geronimo.apache.org Received: (qmail 56449 invoked by uid 500); 19 Jul 2011 03:33:31 -0000 Mailing-List: contact scm-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list scm@geronimo.apache.org Received: (qmail 56435 invoked by uid 99); 19 Jul 2011 03:33:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2011 03:33:24 +0000 X-ASF-Spam-Status: No, hits=-1994.3 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_HTML_ONLY X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2011 03:33:21 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p6J3X0Q4016627 for ; Tue, 19 Jul 2011 03:33:00 GMT Date: Mon, 18 Jul 2011 23:33:00 -0400 (EDT) From: confluence@apache.org To: scm@geronimo.apache.org Message-ID: <3346985.8560.1311046380332.JavaMail.confluence@thor> Subject: [CONF] Apache Geronimo v3.0 > gogo commands for Geronimo MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Auto-Submitted: auto-generated

gogo commands for Geronimo

Page edited by Runhua Chi


Changes (15)

=20 =20
=20 =20
...
[deploy:assemble-server|#gogo= commandassembleserver]
[deploy:distribute|#gogocommanddistribute]
<= /td>
[deploy:list-modules|#gogoco= mmandlistmodules]
[deploy:new-server-instance|#gogocommandnewserverinst= ance]
[deploy:stop-module|#gogocommandstopmodule]
[eba:resolve|#gog= ocommandresolve]
[deploy:install-plugin|#gogocommandinstallplugin]
[deploy:login|#= gogocommandlogin]
[deploy:start-module|#gogocommandstartmodule]
[de= ploy:unlock-keystore|#gogocommandunlockkeystore]

{column}

...
[deploy:connect|#gogocommandc= onnect]
[deploy:encrypt|#gogocommandencrypt]
[deploy:list-modules|#gogocommandlistmodules]
[deploy:new-server-= instance|#gogocommandnewserverinstance]
[deploy:stop-module|#gogocomman= dstopmodule]
[equinox:diagnose|#gogocommanddiagnose]
{column}
=
{column:width=3D25%}
[geronimo:start-client|#gogocommandstartclient= ]
[deploy:deploy-module|#gogocommanddeploymodule]
[deploy:install-b= undle|#gogocommandinstallbundle]
[deploy:list-plugins|#gogocom= mandlistplugins]
[deploy:redeploy-module|#gogocommandredploymodule] [deploy:undeploy-module|#gogocommandundeploymodule]

[eba:resolve|#gogocommandresolve]
{column}

{column:wid= th=3D25%}
[geronimo:start-client|#gogo= commandstartclient]
[deploy:deploy-module|#gogocommanddeploymodule]
[geronimo:start-server|#gogocommandstartserver]
[deploy:disconnec= t|#gogocommanddisconnect]
[deploy:install-library|#gogo= commandinstalllibrary]
[deploy:list-targets|#gogocommandlisttargets] [deploy:restart-module|#gogocommandrestartmodule]
[deploy:unlock-keystore|#gog= ocommandunlockkeystore]

[deploy:uninstall-bundle|#gogocommanduninstallbundle]
[obr:geroni= mo-refresh|#gogocommandgeronimorefresh]
{column}
{column:width=3D25%}
[ge= ronimo:start-server|#gogocommandstartserver]
[deploy:disconnect|#gogoco= mmanddisconnect]
[deploy:install-plugin|#gogocommandinstallplugin]
= [deploy:login|#gogocommandlogin]
[deploy:start-module|#gogocommandstart= module]
[equinox:diagnose|#gogocommanddiagnose]

{column}
{section}

...
[Back to Top|#top]

<= /td>
h1.deploy:install-bundle{anchor:gogocommandinstallbundle}

The command is used to install an OSGi bundle into the server, and th= e bundle information will be recorded in {{etc/startup.properties}} file. I= t has the following syntax:
{panel:borderStyle=3Dsolid}
*install-pl= ugin* *{_}generaloptions{_}* *{_}commandoptions{_}* *<bundle file>* <= br>

where

*{_}commandoptions{_}* includes:
{indent:0}--group= Id{indent}
{indent:1}Defines a group Id for the bundle.{indent}
{in= dent:0}--startLevel{indent}
{indent:1}Specifies start level of the bund= le.{indent}
{indent:0}--start{indent}
{indent:1}Specifies whether t= o start the bundle after installation. By default, the bundle is not starte= d.{indent}
*{_}bundle file{_}* is the fully qualified name of bundle to= be installed.
{panel}

h2. install-bundle command examples Use this syntax to install an OSGi bundle.
{panel:borderStyle=3Dsolid= }
server> deploy:install-bundle --groupId myCompany --start --startL= evel 100 d:/HelloWorld-1.0.jar
{panel}
[Back to Top|#top]

= h1. deploy:uninstall-bundle{anchor:gogocommanduninstallbundle}

The= command is used to uninstall a bundle in server. It has the following synt= ax:
{panel:borderStyle=3Dsolid}
*unlinstall-bundle* *{_}generalopti= ons{_}* *{_}commandoptions{_}* *bundleId*

where

*{_}comma= ndoptions{_}* includes:
{indent:0}--secure{indent}
{indent:1}Use se= cure channel{indent}
*{_}bundleId{_}* is id of the bundle to be uninsta= lled.
{panel}

h2. uninstall-bundle command examples
Use th= is syntax to uninstall an OSGi bundle with id 361 in the server.
{panel= :borderStyle=3Dsolid}
server> deploy:uninstall-bundle 361
{panel= }
[Back to Top|#top]

h1. deploy:unlock-keystore{an= chor:gogocommandunlockkeystore}

...
{panel}
[Back to Top|#top= ]

h2. obr:geronimo-refresh{anchor:gogocommandgeronimorefresh}
=
The command is used to refresh bundle status in the repository of CE s= erver. This command is useful when you installed a new bundle in to CE serv= er and want the bundle information to be added in to the bundle repository = of the server.
{panel:borderStyle=3Dsolid}
*geronimo-refresh* *{_}g= eneraloptions{_}*
{panel}

[Back to Top|#top]

Full Content

3D""Not completed yet
<= /div>

The gogo commands for Geronimo is an extension of Apache karaf Shell to interact with Geronimo kernel. Those command = names are made up of two parts: <scope>:<name> by convention as= listed below. Click each command to learn about its usage.

To enter the karaf shell, press Enter after you start up the Gero= nimo server using geronimo run command.

geronimo:stop= -server
deploy:assem= ble-server
deploy:distribut= e
deploy:instal= l-plugin
deploy:login
deploy:start-mo= dule
deploy:unloc= k-keystore

geronimo:w= ait-for-server
deploy:connect<= br/> deploy:encrypt<= br/> deploy:list-mod= ules
deploy:ne= w-server-instance
deploy:stop-modu= le
equinox:diagnose

geronimo:sta= rt-client
deploy:deploy-= module
deploy:instal= l-bundle
deploy:list-plu= gins
deploy:redepl= oy-module
deploy:undep= loy-module
eba:resolve

=

geronimo:sta= rt-server
deploy:disconnec= t
deploy:insta= ll-library
deploy:list-tar= gets
deploy:restar= t-module
deploy:unin= stall-bundle
obr:geronim= o-refresh

Note that if the <name> portion of the command is unique, then you= only need to type it. If not, then you must either type the full <scope= >:<name> or arrange the scope search path accordingly. For example= , you can use list-modules instead of deploy:list-modules to = list all modules in the server repository.

Following options are common to those commands:

generaloptions includes:

-s or --ser= ver, --hostname

Hostname,= default localhost

-p or --por= t

Port, def= ault 1099

-u or --use= rname

Specify a= n Username to start the server

-w or --pas= sword

Specify t= he password to start the server

--help

<= /div>

Display t= his help message

geronimo= :start-server

The server can be started through Felix Shell using the geronimo:star= t-server command. It uses the following syntax:

start-server generaloptions commandoptions=

where

commandoptions includes:

-A or --jav= aagent

Use a spe= cific Java Agent, set to none to disable

-b or --bac= kground

Run the s= erver process in the background

-D or --pro= perty

Define sy= stem properties

-G or --gpr= operty

Define Ge= ronimo system properties

-H or --hom= e

Use a spe= cific Geronimo home directory

-j or --jvm=

Use a spe= cific Java Virtual Machine for server process

-J or --jav= aopt

Set a Jav= a Virtual Machine flag

-l or --log= file

Capture c= onsole output to a specified log file

-m or --mod= ules

Start up = a specific module by name

-P or --pro= file

Specify a= configuration profile

-q or --qui= te

Suppress = informative and warning messages

-t or --tim= eout

Specify t= he timeout for the server process in seconds

-v or --ver= bose

Enable ve= rbose output; specify multiple times to increase verbosity

--secure

Use secur= e channel

star= t-server command examples

Back to Top

geronimo:= stop-server

The server can be stopped using the geronimo/stop-server command. It use= s the following syntax:

stop-server generaloptions commandoptions<= /em>

Where

commandoptions includes:

--secure

Use secur= e channel

stop-= server command examples

Use this syntax to stop the server.

geronimo> geronimo:stop-server --hostname localhost -p 1099

Back to Top

geroni= mo:wait-for-server

The command is used to verify if the server has started in the given tim= e (in seconds). It uses the following syntax:

wait-for-server generaloptions commandopti= ons

Where

commandoptions includes:

-t or --tim= eout

Specify t= he time (in seconds) to wait while verifying the that the server has starte= d. 60 seconds by default

wa= it-for-server command examples

Back to Top

deploy:login

The command is used to save the username and password for the current co= nnection to a file to avoid future prompting. This command is used for remo= te connections only. It has the following syntax:

login generaloptions commandoptions

where

commandoptions includes:

--secure

Use secur= e channel

login comm= and examples

Use this syntax to save the username and password of the current connect= ion so that you will not be prompted for credentials again when you issue o= ther commands via the connection. Make sure you use deploy:connect f= irstly to connect to a remote instance, then use deploy:login to rec= ord the credential.

geronimo> deploy:login

Back to Top

deploy:encrypt=

The command is used to generates an encrypted string using org.apach= e.geronimo.util.EncryptionManager. It has the following syntax:

encrypt commandoptions string

where

commandoptions includes:

--secure

Use secur= e channel

string is a string to be encrypted

encrypt = command examples

Use this syntax to encrypt string passw0rd on an active server so that t= he encryption settings of that server will be used.

geronimo> deploy:encrypt passw0rd


Online encryption result is shown below:

String to encrypt: passw0rd
Online encryption result:
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmN= v
ZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF= 2YS9s
YW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwAAAAEG2NoqX= ONCcU
GqfK0reVCpVwdAADQUVT

Back to Top

deploy:= assemble-server

The command is used to extract a customized server assembly from the cur= rent one. It has the following syntax:

assemble-server generaloptions commandopti= ons

Where

commandoptions includes:

-a, or --ar= tifact

Specify t= he server artifact name

-f, or --fo= rmat

Specify i= f the assembly is in .zip or tar.gz format

-g, or --gr= oupId

Specify t= he group ID of the library

-t, or --pa= th

Specify t= he assembly location, where your specific plug-ins are stored. The default = location is <geronimo_home>/var/temp/

-l, or --li= st

Refresh t= he plug-in list

a= ssemble-server command examples

Use this syntax to create a custom server assembly, which is placed at <= tt><geronimo_home>/var/temp/.

geronimo> deploy:assemble-server -f zip -g group1 -a assemble1

Back to Top

geronimo= :start-client

The command is used to start a Geronimo application client. Note that be= fore starting a client, you have to deploy the application to the server. I= t has the following syntax:

start-client generaloptions commandoptions=

Where

commandoptions includes:

-A or --jav= aagent

Use a spe= cific Java Agent, set to none to disable

-b or --bac= kground

Run the s= erver process in the background

-D or --pro= perty

Define sy= stem properties

-G or --gpr= operty

Define Ge= ronimo system properties

-H or --hom= e

Use a spe= cific Geronimo home directory

-j or --jvm=

Use a spe= cific Java Virtual Machine for server process

-J or --jav= aopt

Set a Jav= a Virtual Machine flag

-l or --log= file

Capture c= onsole output to a specified log file

-P or --pro= file

Specify a= configuration profile

-t or --tim= eout

Specify t= he timeout for the server process in seconds

-v or --ver= bose

Enable ve= rbose output; specify multiple times to increase verbosity

star= t-client command examples

Back to Top

deploy:connect=

The command is used to connect to an instance of Geronimo that is alread= y running. After connected successfully, you can run a series of commands o= n the remote server. It has the following syntax:

connect generaloptions commandoptions=

Where

commandoptions includes:

--secure

Use secur= e channel

Note that you can also use ssh:ssh command provided by Karaf = shell to connect to a remote instance.

connect = command examples

Use this syntax to connect to a remote server instance:

geronimo> deploy:connect -u system -p manager -s <remote-ip>

Back to Top

deploy:disc= onnect

The command is used to close the connection to a remote Geronimo server.= Only one instance of the server can be connected at a time, no additional = options are needed to specify which server to disconnect from. If you are t= rying to connect to a second server instance, use this command to disconnec= t first. It has the following syntax:

disconnect

disco= nnect command examples

Use this syntax to disconnect a current connection.

geronimo> deploy:disconnect

Back to Top

deploy:de= ploy-module=

The command is used to deploy a module to a Geronimo server. Once deploy= ed, a module is identified by its module ID within Geronimo. It has the fol= lowing syntax:

deploy-module generaloptions commandoption= s <module> <deployment plan>

where

module is a module file, which is required for the comma= nd and can be one of the following:

    =09
  • Java EE Enterprise Application Archive (EAR) file
    =09
  • Java EE Web Application Archive (WAR) file
    =09
  • Java EE Enterprise JavaBean Archive (JAR) file
    =09
  • Java EE Java Resource Archive (RAR) file
    =09
  • OSGi Bundle
    =09
  • Web Archive Bundle(WAB) file
    =09
  • Enterprise Bundle Archive(EBA) file

deployment plan is an optional plan file for Java EE mod= ule. If the deployment plan for a Java EE archive file is not in the WEB-IN= F directory, its location must be specified after the module in th= e command. See Understanding deploym= ent plans for more details.
commandoptions includes:

--secure

Use secur= e channel

-i or --inP= lace

Add and s= tart an archive or directory to an active server, without the archive or di= rectory being copied into the server directory tree

-t or --tar= gets

Specify t= he target repository to be deployed into. See list-targets for the names of repositori= es available on the server.

dep= loy-module command examples

Use this syntax to deploy a WAR file.

deploy-module d:/HelloWorld.war

Use this syntax to deploy a WAR file whose deployment plan is located ou= tside of the WEB-INF directory.

geronimo> deploy:deploy-module d:/HelloWorld.war d:/geronimo-web.xml<= /p>

Back to Top

deplo= y:distribute-module

The command works exactly like deploy-modules except the module is not started onc= e it has been deployed into the server and is not marked to be started each= time the server starts. It has the same syntax and options as deploy-modules:

distribute-module generaloptions commandop= tions <module> <deployment plan>

distr= ibute command examples

Use this syntax to distribute a module whose deployment plan is located = outside of the WEB-INF directory.

geronimo> deploy:distribute-module d:/HelloWorld.war d:/geronimo-web.= xml

Back to Top

deploy:lis= t-targets

The command is used to list all available target repositories on the ser= ver. It has the following syntax:

list-targets generaloptions commandoptions=

where

commandoptions includes:

--secure

Use secur= e channel

list= -targets command examples

Use this syntax to list all available target repository where you can de= ploy applications to on the localhost.

geronimo> deploy:list-targets
Available Targets:
org.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car?ServiceModule= =3Dorg.apache.geronimo.framework/j2ee-system/3.0-SNAPSHOT/car,j2eeType=3DCo= nfigurationStore,name=3DLocal

Back to Top

deploy:lis= t-plugins

The command is used to list all of plugins in a certain maven repository= . It has the following syntax:

list-plugins generaloptions commandoptions=

where

commandoptions includes:

--secure

Use secur= e channel

-rr or --re= fresh-repository

refresh r= epository

-r or --rep= ository

repositor= y URL

-rl or --re= fresh-list

referensh= plugin list

list= -plugins command examples

Use this syntax to first access the list of repositories. Select a repos= itory from the list, plugins in this repository is displayed.

list-plugins

Use this syntax to display the list of plugins in the given repository u= sing secure channel.

geronimo> deploy:list-plugins --secure -r = http://geronimo.apache.org/plugins/geronimo-3.0/

Back to Top

depl= oy:new-server-instance

The command is used to create a new server instance. It has the followin= g syntax:

new-server-instance generaloptions command= options instancename

where

commandoptions includes:

--secure

Use secur= e channel

instancename is the name of the new instance.

new-server-instance command examples

Use this syntax to create a new server instance instance2.

geronimo> deploy:new-server-instance instance2

Back to Top

deploy:= redeploy-module

The command is used to deploy a newer version of a module onto a server = where the older module is already deployed. It has the following syntax:

redeploy-module generaloptions commandopti= ons <module> <deployment plan> <module id>

where

module is a module file, which is required for the comma= nd and can be one of the following:

    =09
  • Java EE Enterprise Application Archive (EAR) file
    =09
  • Java EE Web Application Archive (WAR) file
    =09
  • Java EE Enterprise JavaBean Archive (JAR) file
    =09
  • Java EE Java Resource Archive (RAR) file
    =09
  • OSGi Bundle
    =09
  • Web Archive Bundle(WAB) file

deployment plan is an optional plan file for Java EE mod= ule. If the deployment plan for a Java EE archive file is not in the WEB-IN= F directory, its location must be specified after the module in th= e command. See Understanding deploym= ent plans for more details.
module id is the configuration on the server you want to re= place. If you do not specify the module_id, the plan supplied (or plan insi= de the module) will be used to determine the actual configuration that you = wish to redeploy. Redeploying a plan with an existing module ID allows you = to modify the configuration of a running module without intermediate undepl= oyment.
commandoptions includes:

--secure

Use secur= e channel

r= edeploy-module command examples

Use this syntax to deploy a newer version of an existing module .

geronimo> deploy:redeploy-module D:/HelloWorld.war default/HelloWorld= /1.0/car

Back to Top

deploy:= undeploy-module

The command is used to properly remove a module from a server. It has th= e following syntax:

undeploy-module generaloptions commandopti= ons <module id>

where

module id is the configuration name you want to remove f= rom the server. It must be provided.
commandoptions includes:

--secure

Use secur= e channel

u= ndeploy-module command examples

Use this syntax to remove an existing module.

geronimo> deploy:undeploy-module default/HelloWorld/1.0/car

Back to Top

deploy:sta= rt-module

The command is used to start an existing module on the server which is n= ot running. It use the following syntax:

start-module generaloptions commandoptions= <module id>

where

module id is the configuration name you want to start on= the server. It must be provided.
commandoptions includes:

--secure

Use secur= e channel

star= t-module command examples

Use this syntax to start an existing module.

geronimo> deploy:start-module default/HelloWorld/1.0/car

Back to Top

deploy:stop= -module

The command is used to stop a running module on the server. It use the f= ollowing syntax:

start-module generaloptions commandoptions= <module id>

where

module id is the configuration name you want to stop on = the server. It must be provided.
commandoptions includes:

--secure

Use secur= e channel

stop-= module command examples

Use this syntax to stop a running module.

geronimo> deploy:stop-module default/HelloWorld/1.0/car

Back to Top

deploy:r= estart-module<= /a>

The command is used to restart a module on the server. It has the follow= ing syntax:

restart-module generaloptions commandoptio= ns <module id>

where

module id is the configuration name you want to restart = on the server. It must be provided.
commandoptions includes:

--secure

Use secur= e channel

re= start-module command examples

Use this syntax to restart a module.

geronimo> deploy:restart-module default/HelloWorld/1.0/car

Back to Top

deploy:lis= t-modules

The command is used to list modules in the target repository. It has the= following syntax:

list-modules generaloptions commandoptions= <targetname>

where

commandoptions includes:

--secure

Use secur= e channel

-t or --sto= pped

Show stop= ped modules only

-r or --sta= rted

Show star= ted modules only

-a or --all=

Show star= ted and stopp modules only, this one is default if you did not specify any = parameters

targetname is the name of target repository. See list-targets for more details.

list= -modules command exmaples

Use this syntax to list the started modules in the target repository.

geronimo> deploy:list-modules -r

Back to Top

deploy:i= nstall-plugin<= /a>

The command is used to install a geronimo plugin into the server. It has= the following syntax:

in= stall-plugin command examples

Use this syntax to deploy a CAR file.

geronimo> deploy:install-plugin d:/HelloWorld-1.0.car

Back to Top

deploy:= install-library

The command is used to install a geronimo library into the server. It ha= s the following syntax:

install-library generaloptions commandopti= ons <configuration archive>

where

commandoptions includes:

--secure

Use secur= e channel

-g or --gro= upId

Specify t= he group ID of the library

configuration archive is the fully qualified name of lib= rary archive.

If installed successfully, the library will be found in <geronimo= _home>/repository

i= nstall-library command examples

Use this syntax to install a geronimo library.

geronimo> deploy:install-library d:/temp/openejb-ejbd-3.2-SNAPSHOT.ja= r

Back to Top

deploy:i= nstall-bundle<= /a>

The command is used to install an OSGi bundle into the server, and the b= undle information will be recorded in etc/startup.properties file.= It has the following syntax:

install-plugin generaloptions commandoptio= ns <bundle file>

where

commandoptions includes:

--groupId

Defines a= group Id for the bundle.

--startLeve= l

Specifies= start level of the bundle.

--start

=

Specifies= whether to start the bundle after installation. By default, the bundle is = not started.

bundle file is the fully qualified name of bundle to be = installed.

in= stall-bundle command examples

Use this syntax to install an OSGi bundle.

server> deploy:install-bundle --groupId myCompany --start --startLeve= l 100 d:/HelloWorld-1.0.jar

Back to Top

deploy= :uninstall-bundle

The command is used to uninstall a bundle in server. It has the followin= g syntax:

unlinstall-bundle generaloptions commandop= tions bundleId

where

commandoptions includes:

--secure

Use secur= e channel

bundleId is id of the bundle to be uninstalled.

= uninstall-bundle command examples

Use this syntax to uninstall an OSGi bundle with id 361 in the server.

server> deploy:uninstall-bundle 361

Back to Top

deploy:= unlock-keystore

The command is used to unlock a keystore and private key in Geronimo ser= ver. It has the following syntax:

unlock-keystore generaloptions commandopti= ons <keystore>

where

commandoptions includes:

--secure

Use secur= e channel

keystore is the name of keystore or private key you want= to unlock.

u= nlock-keystore command examples

Back to Top

equinox:diag= nose

The command is used to diagnose constraints of an installed OSGi bundle = and verify if the bundle can be resolved successfully. The command is only = available in Equinox OSGi runtime.

diagnose generaloptions commandoptions <bundleIDs>

where
commandoptions includes:

-s or --sim= ple

Do not pe= rform deeper analysis of resolver problems

bundleIDs is a list of bundle IDs seperated by whitepace= s.

diagnos= e command examples

Use this syntax to diagnose the resolver problem of a bundle with Id 85.=

geronimo> diagnose 85
mvn:org.apache.geronimo.framework/geronimo-service-builder/3.0-SNAPSHOT [85= ]
No unresolved constraints.

diagnose
Back to Top

eba:resolve

The command is used to resolve constraints of an Aries applications and = create the deployment manifest application.MF for the applciation.=

resolve generaloptions commandoptions= <AppPath>

where
commandoptions includes:

-o or --out=

Specify t= he location to output the resolve application.

AppPath is location of Aries application to be resolved.=

resolve = command examples

Use this syntax to resolve an Aries application.

geronimo> eba:resolve d:/temp/myAriesApp.eba
Attempting to resolve myAriesApp application.
Application myAriesApp is now resolved.

Back to Top

obr:geron= imo-refresh<= /a>

The command is used to refresh bundle status in the repository of CE ser= ver. This command is useful when you installed a new bundle in to CE server= and want the bundle information to be added in to the bundle repository of= the server.

geronimo-refresh generaloptions

Back to Top