Fuse ESB Enterprise - Cloud Computing with Fabric - Initialize Your Local Container

Prerequisites

This tutorial assumes you have a fresh installation of Fuse ESB Enterprise on your local machine (see Installation Guide). If you have previously experimented with the local container instance, it might be a good idea to perform a cold start before you proceed.

Forcing a cold start

(Optional) If you are not sure what state your local container is in or if you have previously used your local container in the context of a fabric, it is a good idea to force a cold start before you continue. This ensures that your container is in a known state (a plain, unmanaged container) and makes it more likely that you will be able to follow the tutorial steps without any problems.

To force a cold start, perform the following steps:

If the container is currently running, shut it down by entering the following console command:

karaf@root> shutdown -f

	Note
	If your container has any child instances running, you must also shut the child instances down. On *NIX systems, you could use the command `ps -ef \| grep karaf` to discover any child instances.

Delete the ESBInstallDir/data/ directory.

	Warning
	This will completely wipe the state of the container (apart from the configuration settings stored under `ESBInstallDir/etc/`).

	Note
	If your container has any child instances, you must also delete the `ESBInstallDir/instances/` directory, which contains the data for the child instances.

Start the container by entering the following commands:
```
cd ESBInstallDir/bin
./fuseesb
```

Initializing the local container

After a cold start, the container does not have the required cloud commands installed by default. To enable support for accessing and administering the AWS EC2 provider, install the requisite Karaf features, as follows:

karaf@root> features:install jclouds-aws-ec2 fabric-jclouds fabric-commands