previous next trail start tutorial home feedback openwings.org

Other Useful Shell Tricks

The shell can be used to launch user interfaces (UIs) associated with Services or Mbeans. Here is an example of launching a UI associated with the Install Services' Mbean. The UI is launched by navigating to the appropriate place in the Openwings hierarchy and typing its name.

Openwings@root\> ls

PLATFORMS:
  pc-myhost-100.100.100.10

Openwings@root\> cd pc-myhost-100.100.100.10
Openwings@...\pc-myhost-100.100.100.10> ls

SERVICES:
  ...

MBEANS:
  ...

COMPONENTS:
  ...

PROCESSES:
  installer-c9a86136_9d2f42a7_a19f8fea_0487fea3
  jakarta-tomcat-3.2.1-fa2a3ac3_10774673_abfcb7a8_91c57bb7
  jini-1.1-61fad223_09c84c95_88f3db66_dd0a3813

Openwings@...\pc-myhost-100.100.100.10> cd installer-c9a8

You needn't bother typing the whole name of the process you wish to navigate to. If the name of the process is unique, the first few characters is all the shell needs to figure out what you mean. This command-completion feature works everywhere in the hierarchy.

Now we will navigate to the Logging MBean underneath the installer process in the hierarchy.

Openwings@...\installer-c9a86136_9d2f42a7_a19f8fea_0487fea3\> ls

SERVICES:
  net.openwings.install.Installer
  net.openwings.management.RemoteManager

MBEANS:
  com.gd.openwings.utilities.logging.LogMBean
  net.openwings.component.utilities.ComponentMBean

Openwings@...> cd com.gd.openwings.utilities.logging.LogMBean
Openwings@...\com.gd.openwings.utilities.logging.LogMBean\> ls

com.gd.openwings.utilities.logging.LogMBean contains UIs:
  com.gd.openwings.utilities.logging.LogMBeanFrameFactory

Openwings@...> com.gd.openwings.utilities.logging.LogMBeanFrameFactory

The UI is started by typing its name. Here is the LoggingMBeanUI that appears:

You can also launch service UIs from the shell. The Image Service has a user interface that you can launch from the shell as follows.

PROCESSES:
  HelloWorldProvider_im-0.1-e2bd35d5_7c0340f5_a772f092_c0757c2f
  HelloWorldUser_im-0.1-f76bfce3_8c724a13_baa2eb52_a429d73f
  Image_im-2b3d7370_b2aa425f_962ce1b6_0e51221b
  installer-93609bf1_47ca46d9_8c0e8335_0f35b9dd
  jakarta-tomcat-3.2.1-ed09ed5a_1ee1499e_82918fd7_1e8b15f3
  jini-1.1-3ca549c3_b781487b_b1dc8f84_2ff97b3e

Openwings@root\PC-39QZ101-137.162.171.83\> cd Image_im-2b3d7370_b2aa425f_962ce1b6_0e51221b
Openwings@root\PC-39QZ101-137.162.171.83\Image_im-2b3d7370_b2aa425f_962ce1b6_0e51221b\> ls

SERVICES:
  com.gd.openwings.demo.image.service.ImageService
  net.openwings.management.RemoteManager

MBEANS:
  com.gd.openwings.utilities.logging.LogMBean
  net.openwings.component.utilities.ComponentMBean

Openwings@root\PC-39QZ101-137.162.171.83\Image_im-2b3d7370_b2aa425f_962ce1b6_0e51221b\> cd com.gd.openwings.demo.image.service.ImageService
Openwings@root\PC-39QZ101-137.162.171.83\Image_im-2b3d7370_b2aa425f_962ce1b6_0e5 1221b\com.gd.openwings.demo.image.service.ImageService\> ls

com.gd.openwings.demo.image.service.ImageService contains UIs:
  com.gd.openwings.component.jini.GenericAWTFactory

Openwings@root\PC-39QZ101-137.162.171.83\Image_im-2b3d7370_b2aa425f_962ce1b6_0e5 1221b\com.gd.openwings.demo.image.service.ImageService\> com.gd.openwings.component.jini.GenericAWTFactory

The UI is started by typing its name. Here is the Image Service UI.

Back to Tutorial Trails

back to top

© Copyright 2002, General Dynamics Decision Systems. All rights reserved.

previous next trail start tutorial home feedback openwings.org