In this recipe, we will deploy the GateIn management CLI to a GateIn instance, and then verify that the deployment was successful.
To deploy the GateIn management CLI:
- Go to https://repository.jboss.org/nexus/content/groups/public/org/gatein/management/gatein-management-cli/1.0.1-GA/ and download
gatein-management-cli-1.0.1-GA.war. - Copy it into the
standalone/deploymentsfolder of the GateIn installation and start the server. - Open an SSH connection to the CLI by entering the following command:
> ssh -p 2000 root@localhost - Enter the password for root when requested. With the standard GateIn install, the password is gtn.
- The initial output from the CLI shell will be similar to the following screenshot:
- At the shell prompt, enter the following to connect to the management console:
> mgmt connect - Enter the password for root user again.
- At the shell prompt, enter the following to list all the nodes at the current location:
> ls - The CLI shell will be similar to the following screenshot:
Step 6 connects the user to the management CLI of portal, which is the default portal container on GateIn. If you wanted to connect to a different portal deployed to GateIn, just pass the name of the portal as a -c argument in the mgmt connect command.
Step 8 demonstrates one of the commands available from the portal CLI. In this case, ls will list all the management extension components
that are present in the portal. If ls were executed from within the mop folder, the result would be a list of JCR nodes at that level.
Now we show you how to build the CLI with the latest source available.
To take advantage of the latest updates to the GateIn management component CLI, it may sometimes be necessary to build it from source.
There are two options for retrieving the source for building:
- Use a GIT client to clone the repository at git://github.com/gatein/gatein-management.git
- Download the latest source as a ZIP from https://github.com/gatein/gatein-management/zipball/master
Building the source is then a matter of either going to the location where GIT cloned the repository to, or where the source ZIP was unpacked, and entering the following command on a command line:
> mvn clean install
Note
For Maven to find any JBoss dependencies that are required to build gatein-management, follow the instructions on https://community.jboss.org/wiki/MavenSettings to add the JBoss repository.
The
WAR file required to be deployed is then located in the cli/target folder.