AppBuilder

Extract the . zip file you obtained from the WebSphere sMash AppBuilder tool into a fresh directory on your test server.

You could hand edit the file yourself, but this example uses the dependencies page of the AppBuilder.

Once you've started up AppBuilder, you should see a message in your command window that says something similar to that shown in Figure 2.

You can do this on the Dependency tab from within the WebSphere sMash browser-based AppBuilder interactive development environment.

To do that, click Create new application to create the sample application in the left panel of the AppBuilder.

The next step is to go to the console view of the AppBuilder and run the zero task for running a database script.

The AppBuilder provides tools for adding dependencies from your local or remote repository.

The Package option is accessible from the main AppBuilder screen; the mouse arrow is pointing to the Package icon in Figure 2.

Click the Start link that appears beside the green arrow icon in the upper right corner of the AppBuilder (Figure 16).

At the top right of the App Builder window there is a green Start button.

The WebSphere sMash AppBuilder has a console view where you can enter commands.

In the M2 version, if you only type appbuilder, you'll see a list of parameters which you can pass to the script (Figure 1).

From the command line run the appbuilder command.

Figure 10 shows the AppBuilder launched within Firefox.

This happens only the first time you run the AppBuilder.

You should now see a listing of all the applications you have created or brought into the AppBuilder.

To launch the AppBuilder, go to a command prompt and issue a command.

You can then open the application using the App Builder.

Regardless of the method, the command that gets issued is zero model sync and the output is the same. Using the AppBuilder