Below are directions for starting Warehouse Server 1, Catalog Server 1, and the client daemon
on the first machine.
- Configure Bean Extender and start Network Deployment servers. Run the Bean
Extender Configuration from the command line as follows:
java com.ibm.beans.util.Configure.
- Set Bean Extender working directory. Select the Working tab and
specify a subdirectory to be used as the Bean Extender
working directory. It must be included in the CLASSPATH.
- Check Network Deployment settings. The default Network Deployment
settings should be sufficient. Depending on your machine setup, you may have
to provide the host name and domain name for the servers and daemons. Check the
Client, Catalog, and Warehouse tabs and fill in the correct
host name and domain name of your machine, if necessary.
- Start servers. Start the RMI Registry and all local Network Deployment
servers and daemons configured.
To do this, select the Start tab in the Configure utility and press the Start
Network Deployment servers and daemons button. This will bring up the
Warehouse Server and Catalog Server windows.
Once all of the servers have been started, you can exit
the Bean Extender Configure utility.
- Configure the warehouse. If the Server Status window indicates that the
server is running, press the Stop Server button. Configure the warehouse
as follows:
- Check warehouse host and domain names. In the Warehouse Controller window,
you may need to provide the correct host name and domain name for the server machine.
- Add Peer. Click on the Peers tab and specify the host name and
domain name for the machine to be used as Warehouse Server 2. Specify an RMI
registry port number of 1099. Specify a server name of
com.ibm.beans.netdeploy.warehouse.WarehouseServer. To add the peer, press
the Add button.
- Apply Settings. Click on the the Server Settings tab and press
the Apply Settings button so that server is ready to start.
- Start the Server. Press the Start Server button to start the Server.
You should see the "Running.." message in Server Status window.
(For additional information about Warehouse Server Configuration
and Usage, refer to the Warehouse Server
Configuration and Usage.)
- Configure the catalog. If the Server Status window indicates that the
server is running, press the Stop server button. Configure the catalog
as follows:
- Check catalog host and domain names. In the Server connection information
section under the Status tab,
you may need to provide the correct host name and domain name for the server machine.
- Add Peer. Click on the Catalogs tab and specify the host name and
domain name for the machine to be used as Warehouse Server 2. Specify an RMI
registry port number of 1099. Specify a server name of
com.ibm.beans.netdeploy.warehouse.WarehouseServer. To add the peer, press
the Add catalog to list button.
- Start the Server. Press the Start Server button to start the Server.
You should see the "Running" message in Server Status window.
(For additional information about Catalog Server Configuration and Usage,
refer to
Catalog Server Configuration and Usage.)
Below are directions for starting Warehouse Server 2 and the client daemon
on the second machine.
- Add jar files to class path. Assuming Bean Extender was installed in
x:\product, add the following jar files to the CLASSPATH:
- x:\product\jars\Travel.jar
- x:\product\jars\controls.jar
- x:\product\jars\media.jar
- x:\product\jars\calendar.jar
- x:\product\jars\awidgets.jar
- Configure Bean Extender and start Network Deployment servers. Run the Bean
Extender Configuration from the command line as follows:
java com.ibm.beans.util.Configure.
- Set Bean Extender working directory. Select the Working tab and
specify a subdirectory to be used as the Bean Extender
working directory. It must be included in the CLASSPATH.
- Check Network Deployment settings. The default Network Deployment
warehouse and client daemon
settings should be sufficient. Depending on your machine setup, you may have
to provide the host name and domain name for the servers and daemons. Check the
Client and Warehouse tabs and fill in the correct
host name and domain name of your machine, if necessary.
Under the Catalog tab, set the host name and domain name for the machine
on which Catalog 1 is running.
- Start servers. Start the RMI Registry and all local Network Deployment
servers and daemons configured.
To do this, select the Start tab in the Configure utility and press the Start
Network Deployment servers and daemons button. This will bring up the
Warehouse Server window. Since a remote catalog was specified, there will be
no Catalog Server window.
Once all of the servers have been started, you can exit
the Bean Extender Configure utility.
- Configure the warehouse. If the Server Status window indicates that the
server is running, press the Stop Server button. Configure the warehouse
as follows:
- Check warehouse host and domain names. In the Warehouse Controller window,
you may need to provide the correct host name and domain name for the server machine.
- Add Peer. Click on the Peers tab and specify the host name and
domain name for the machine to be used as Warehouse Server 2. Specify an RMI
registry port number of 1099. Specify a server name of
com.ibm.beans.netdeploy.warehouse.WarehouseServer. To add the peer, press
the Add button.
- Apply Settings. Click on the the Server Settings tab and press
the Apply Settings button so that server is ready to start.
- Start the Server. Press the Start Server button to start the Server.
You should see the "Running.." message in Server Status window.
(For additional information about Warehouse Server Configuration
and Usage, refer to the Warehouse Server
Configuration and Usage.)
Below are directions for starting the client daemon on the third machine.
- Add jar files to class path. Assuming Bean Extender was installed in
x:\product, add the following jar files to the CLASSPATH:
- x:\product\jars\Travel.jar
- x:\product\jars\controls.jar
- x:\product\jars\media.jar
- x:\product\jars\calendar.jar
- x:\product\jars\awidgets.jar
- Configure Bean Extender and start Network Deployment client daemon. Run the Bean
Extender Configuration from the command line as follows:
java com.ibm.beans.util.Configure.
- Set Bean Extender working directory. Select the Working tab and
specify a subdirectory to be used as the Bean Extender
working directory. It must be included in the CLASSPATH.
- Check Network Deployment settings. The default Network Deployment
client daemon settings should be sufficient. You may have
to provide the host name and domain name for the and client daemon. Check the
Client tab and fill in the correct host name and domain name of your machine,
if necessary.
Under the Warehouse tab, set the host name and domain name for the machine
on which Warehouse 2 is running.
Under the Catalog tab, set the host name and domain name for the machine
on which Catalog 1 is running.
- Start servers. Start the RMI Registry and all local Network Deployment
servers and daemons configured.
To do this, select the Start tab in the Configure utility and press the Start
Network Deployment servers and daemons button.
Since a remote catalog and warehouse were specified, there will be
no Warehouse Server or Catalog Server window.
Once the client daemon has been started, you can exit
the Bean Extender Configure utility.
In this section, Developer 1 stocks the FlightInfoDap bean in FlightInfo.jar to
Warehouse Server 1 and lists it on the Catalog Server 1. He then stocks
the FlightSelector bean to Warehouse Server 1, and adds a catalog item for it on Catalog
Server 1.
For the purposes of this demo a version of FlightInfo.jar has been provided.
Since it will be overwritten with a newer version later on, copy the file to a temporary
location, for example d:\tmp. Assuming Bean Extender is stored in
x:\product, copy x:\product\jars\FlightInfo.jar to d:\tmp.
To stock FlightInfo.jar to the warehouse, perform the following steps:
- Start the Client standalone GUI by typing,
java com.ibm.beans.netdeploy.client.ClientMain in a command line window.
- Select Stock Warehouse Content and click on the Next button .
- Assuming you copied FlightInfo.jar into d:\tmp, enter
d:\tmp\FileInfo.jar into the Pathname of content field.
and click on the Next button.
- You can skip the Externally visible classnames of content panel
by clicking on the Next button (Note: this panel is used to specify
all class names that might be referenced externally so that classes comprising
the warehouse item being being added can be located and dynamically downloaded with
com.ibm.beans.netdeploy.client.NetworkClassLoader.)
- FlightInfo.jar has no dependecies, so you can skip this
Dependency panel by clicking on the Next button.
- Finally, select Commit Current Content & perform Operation
and click on the Next button to stock the content on the Warehouse Server.
When the operation is complete, you will advance to the next panel.
- This panel displays the results of the operation. Press the Next button
to return to the main panel.
Now, add a catalog item for the FlightInfoDap bean to Catalog Server 1
by performing the following steps:
- In the Stock/Restock/Order operations panel,
select Stock Catalog Content and click on the Next button.
- Click on the Browse Navigator button to bring up the Client Path Dialog
window.
- Enter travel.flight.dap in the Path Node Name field.
You can enter any title and the description. Click on the OK button
to close the window.
- Now, enter "FlightInfoDap Bean" in the Title field and
enter some description. Click on the Next button when you are done.
- In this step, the new catalog item will be associated with the FileInfoDap bean.
Click on the Browse Client Registry button to display the
Warehouse Table Entry Viewer dialog. From this dialog, select
the warehouse content which is to be associated with this catalog item.
Select the entry for FlightInfo.jar. Press the Done button to close it
and return to the original panel. With this association now created,
the catalog item, once added, can be used to order FlightInfo.jar.
Click on the Next button to continue to the next panel.
- In this step, optionally enter any attribute/value pairs desired.
Attributes can be used to restrict catalog queries to catalog entries
with specified attribute values. For example, since this catalog item
represents a Java bean, you could specify PLAT=ALL since your bean
will run on all platforms. There are no predefined attributes.
Click on the "Add" button to add each attribute and value.
When all desired attribute/value pairs have been entered, click on the
Next button to continue to the next panel.
- Next, enter any relevant keywords which might help users to locate this
catalog item in catalog searches.
When all desired keywords have been entered, click on the
Next button to continue to the next panel.
- Catalog items can contain references to other catalog items. The
"Specify References for the Catalog Item" panel is used to add such references.
However, this feature is not yet exploited by the Network Deployment client.
Press the Next button to skip to the next panel.
- Next select Commit Current Content & Perform Operation and click on
the Next button to list the FlightInfoDap bean in the Catalog. When the
operation is complete you will advance to the next panel.
- This panel displays the results of the operation. Press the Next button
to return to the main panel.
The steps required to stock FlightSelector.jar to the warehouse will be very similar to the
steps taken
to stock FlightInfo.jar. To stock FlightSelector.jar to the warehouse,
use the Client standalone GUI to perform the following steps:
- Select Stock Warehouse Content and click on the Next button .
- Enter the fully-qualified pathname to the content next to "Pathname of content"
label. Assuming Bean Extender is stored in x:\product, enter
x:\product\jars\FlightSelector.jar and click on the Next button.
- As before, you can skip the Externally visible classnames of content panel
by clicking on the Next button.
- Since the FlightSelector bean is dependent on the FlightInfoDap bean, FlightInfo.jar
must be listed as a dependency. Click the Browse Client Registry to
display the Warehouse Table Entry Viewer window. From there, select the entry for
FileInfo.jar and press the Done button. Press the Next button to
continue to the next panel.
- Finally, select Commit Current Content & perform Operation
and click on the Next button to stock the content to the Warehouse Server.
When the operation is complete, you will advance to the next panel.
- This panel displays the results of the operation. Press the Next button
to return to the main panel.
Adding a catalog item for the FlightSelector bean will be very similar to the steps taken
to add a catalog item for the FlightInfoDap bean.
To add a catalog item for the FlightSelector bean to Catalog Server 1,
perform the following steps:
- Select Stock Catalog Content and click on the Next button
- Click on the Browse Navigator button to bring up the Client Path Dialog
window.
- Enter travel.flight.dap.viewer in the Path Node Name field.
Enter a title and description. Click the OK button
to record the data and close the window.
- Now enter "FlightSelector" in the Title field and
enter a description. Click on the Next button when you are done.
- In this step, the new catalog item will be associated with the FileSelector bean.
Click on the Browse Client Registry button to display the
Warehouse Table Entry Viewer dialog. From this dialog, select
the warehouse content which is to be associated with this catalog item.
In the case, select the entry for FlightInfo.jar.
Press the Done button to close it
and return to the original panel. With this association now created,
the catalog item, once added, can be used to order FlightSelector.jar.
Click on the Next button to continue to the next panel.
- As with the FlightInfoDap bean, enter any attribute/value pairs desired, such
as PLAT=ALL. Click on the "Add" button to add it. When all desired attribute values
have been added, press the Next button.
- Again, as with the FlightInfoDap bean, add any relevant keywords
and press the Next button.
- As before, press the Next button to skip the
Specify References for the Catalog Item panel.
- Next select Commit Current Content & Perform Operation and click on
the Next button to list this FlightSelector bean on the Catalog Server.
When the operation is complete, you will advance to the next panel.
- This panel displays the results of the operation. Press the Next button
to return to the main panel.
In this section, Developer 2 in this scenario is going to build Travel Demo consisting of
FlightSelector bean (in FlightSelector.jar), the FlightInfoDap bean (in FlightInfo.jar),
the Itinerary bean (Travel.jar). Itinerary depends on the following jar files at
runtime: controls.jar, media.jar, calendar.jar, and awidgets.jar.
It is assumed that Developer 2 already has Travel.jar, controls.jar, media.jar, and
calendar.jar, and that they are not available on any warehouse.
Make sure these jar files are in your CLASSPATH, as described in the section
Start Warehouse Server 2 and the Client Daemon on the second machine.
- Start the Assembly Surface. Enter
java com.ibm.beans.tools.assembly.AssemblySurfaceMain
to start the Assembly Surface.
- Open FlightSelector.jar as a Network Repository. In the Repositories
panel under the Beans tab, press the Add network repository button. This
brings up the Network Deployment Catalog window. In this window, open the catalog
top-level folder. Under inside that folder, you will find a travel folder. Open
it and the demo folder inside it. You will then find the two entries: dap
and viewer. Click on view, and the Open network repository button will
then be enabled. Press the Open network repository button. A viewer
repository is created with a tab of the same name.
- Open FlightInfo.jar as a Network Repository. In the Repositories
panel under the Beans tab, press the Add network repository button. Peform
the same actions as with FlightSelector.jar above, but this time, select the icon
labled dap under the demo folder. As before, a new repository is added
to the Assembly Surface.
- Create the TravelDemo bean.
!!!!! ADD ASSEMBLY SURFACE DIRECTIONS HERE !!!!!!!
- Stock the TravelDemo bean to the warehouse.. This step is very similar to
step Developer 1 followed to stock jar files to the warehouse, except in this case, much
of the data is already filled out for you. In particular, note that dependencies available
as warehouse items are already listed.
- Add a catalog listing for the TravelDemo bean to the warehouse..
In this section, the end user, on machine 3, runs the standalone Network Deployment client GUI
to browse the catalog and order the TravelDemo bean.
To order the TravelDemo bean, perform the following steps:
- Start the Client standalone GUI by typing,
java com.ibm.beans.netdeploy.client.ClientMain in a command line window.
- Select Place Order and click on the Next button to proceed to the
next panel.
- Press the Browse Navigator button to diplay the Client Navigator Dialog
window. In this window, open the catalog top-level folder. Under inside that folder,
you will find a travel folder. Open it and the demo folder inside it.
You will then find the an entry labeled traveldemo.
Select it by clicking on it. The title and description for the
TravelDemo bean's catalog item should appear. Also, the OK button will
then be enabled. Press the OK button to return to the original panel.
Once back in the Client GUI panel, press the Next button to proceed to the next
panel.
- Enter the pathname to the subdirectory into which you want to download the TravelDemo bean
on your machine. The subdirectory specified should be in your CLASSPATH. Press the
Next button to proceed to the next panel.
- You can choose to request a one-time order or a subscription. A one-time order
can always be updated with the latest version with manual initiation. A subscription
will cause your Network Deployment client daemon to daily check the warehouse for
updated content, and update your machine with any updated content. Choose either
option and press Next to proceed to the next panel.
- In this panel, click the checkbox to indicate that you want to go through with the order.
Press Next to begin processing. After processing is complete, you will advance
to the next panel.
- At this point the order is complete. This panel displays the order results. Press
Next to return to the main client panel.
Since the TravelDemo bean has runtime dependencies that are not stored on any warehouse,
we will assume that she has obtained these dependencies according to the instructions
posted in the TravelDemo bean catalog entry and added the jar files to her CLASSPATH.
Dependencies which reside on a warehouse, such as FileInfo.jar, are downloaded automatically
and extracted (if a jar or zip file) into the order directory, which should be in the CLASSPATH.
As mentioned in Start the Client Daemon on the third machine,
the jar files Travel.jar, controls.jar, media.jar, calendar.jar,
and awidgets.jar must be included in your CLASSPATH.
To run the TravelDemo bean, perform the following steps:
- From a command line window, type the following command:
java com.ibm.beans.tools.BeanLauncher com.ibm.beans.demos.TravelDemo
In this section, Developer 1 has made a modification to the FlightInfoDap code and wants
to restock the warehouse with this new version of FlightInfo.jar. As before, his
Network Deployment client is connected to Warehouse Server 1 and Catalog Server 1.
The modification to FlightInfoDap has already been made for you for the purposes of this
demo. In this scenario, the FlightInfoDap code was changed to fix a bug that prevented
some flights from being displayed. The newer version will display more flights.
Assuming that you copied FlightInfo.jar to the temporary directory d:\tmp as
described in
Stock and list the FlightInfoDap and FlightSelector beans,
copy x:\product\src\com\ibm/beans\demos\travel\flight\modified\FlightInfo.jar to
d:\tmp.
To restock FlightInfo.jar to the warehouse, perform the following steps:
- Start the Client standalone GUI by typing,
java com.ibm.beans.netdeploy.client.ClientMain in a command line window.
- Select Restock Warehouse Content and click on the Next button .
- Press the Browse Client Registry button
to view the list of warsehouse items that have been stocked from or ordered by
your client. Select the entry for FlightInfo.jar and press the Done button.
Then press the Next button to continue to the next panel.
- Since, no changes to any subsequent panels are necessary, continue to press
Next until you reach the Perform Current Operation panel.
- Finally, select Commit Current Content & perform Operation
and click on the Next button to restock the Warehouse with the newer content.
When the operation is complete, you will advance to the next panel.
- This panel displays the results of the operation. Press the Next button
to return to the main panel.
For the purposes of this demo, we will assume that no update to the FlightInfoDap bean's
catalog item is necessary.
In this section, the end user will refresh her TraveDemo order. An order refresh causes
updated warehouse items associated with the order to be downloaded to the client, including
dependencies. Content is not downloaded again if it has not changed. If the end user has
subscribed to the TravelDemo bean, the order will be refreshed for her periodically.
In any case, she can manually initiate an order refresh at any time. In this scenario,
she will manually initiate the order refresh.
To refresh the TravelDemo order, perform the following steps:
- Start the Client standalone GUI by typing,
java com.ibm.beans.netdeploy.client.ClientMain in a command line window.
- Select Refresh Order and click on the Next button .
- Press the Browse Client Registry button to view a list of orders that have
placed by the user. Select the entry for TravelDemo and press the Done button.
Then press the Next button to continue to the next panel.
- Select Commit Current Content & perform Operation
and click on the Next button to start the order refresh. You will advance to
the next panel when the refresh is complete.
- This panel displays the results of the operation. Press the Next button
to return to the main panel.
Now, run the TravelDemo bean as described above.
[ Top of Page | Previous Page | Table of Contents | Documentation
Homepage ]