Chapter 8. Transcoding Technology 249
Figure 8-3 XML Configuration management steps
For an example of how to use these commands, see “Preparation steps” on
page 252.
8.3 Request Viewer
Request Viewer is a very useful visual tool for monitoring the traffic going through
Transcoding Technology. The Request Viewer is included in the Everyplace
Toolkit for use in debugging your annotation files and styesheets. You can use
Request Viewer to view the configuration and status information of the registered
transcoding plug-ins within Transcoding Technology.
Request Viewer is particularly handy as a debugging tool, because it enables
you to examine the flow of requests and responses through the server and
observe which plug-ins are triggered and when they are triggered. For each
transaction, Request Viewer also displays the header and content information as
they are manipulated by the transcoding plug-ins.
The primary window of Request Viewer consists of these parts:
1. Menu bar: Provides access to the application options for Files, Actions,
Requests and Help. Menu options can be disabled when the action is not
available.
2. View options: Two tabs, each of which specifies a particular view selection.
One is for the Server Configuration and the other is the Request Processing
view. When either of these views is selected, the associated content is
displayed in the main window. The Server Configuration view provides the
transcoding server information, including the transcoders registered,
XMLConfig
Command
ExportResources
Transcoding
Technology
WTPResources.xml
(Config File)
WTPResources.xml
(Config File Modified)
1. Read
2. Create
(As Input)
4. Write
3. Modify
XMLConfig
Command
ImportResources
250 IBM WebSphere Everyplace Access V5, Volume II: Application Development
preference profiles, and so on. The Request Processing view shows the flow
of the request through the server.
3. The Server Configuration view (shown in Figure 8-4) subdivides the window
into three parts:
a. Server Configuration: A list view of the contents of this configuration
(including sublayers and transcoding plug-ins). This is found in the top-left
pane.
b. Details: Displays the details of an item within the configuration. Content is
displayed in this pane when an item is selected in the Server Configuration
tree view. This is found in the top-right pane, across from the Server
Configuration.
c. Output Messages: Displays messages generated at execution time. This is
found across the bottom of the window, below the Server Config and
Details panes.
Figure 8-4 Request Viewer server configuration
Chapter 8. Transcoding Technology 251
4. The Request Processing view (shown in Figure 8-5) subdivides the window
into three parts:
a. Request Processing: A tree view of the flow of requests through
Transcoding Technology (in the top-left pane).
b. Transaction Header: Displays the contents of the HTTP header. The
content is displayed in this pane when an item is selected in the Request
Processing tree view. This is found in the top-right pane, across from
Request processing.
c. Transaction Content: Displays a particular transcoder’s input or output
(below the Transaction Header).
Figure 8-5 Request Viewer request processing
For more details on the Request Viewer, see the WebSphere Transcoding
Publisher Developer Guide V4.0 found at:
http://www.ibm.com/software/webservers/transcoding/library.html
252 IBM WebSphere Everyplace Access V5, Volume II: Application Development
8.3.1 How to start Request Viewer
The Request Viewer is now included in the Everyplace Toolkit, which is a plug-in
for the WebSphere Studio offering (currently WebSphere Studio Site Developer
and WebSphere Studio Application Developer products). We are using
WebSphere Studio Site Developer with the Everyplace Toolkit installed.
Preparation steps
Prior to starting Request Viewer in WebSphere Studio, you must perform these
steps on the Everyplace Access server:
1. Use the Services to stop the IBM WebSphere Application Server and the IBM
Everyplace Sync Server.
2. Start a DOS prompt and change the working directory to the directory where
Transcoding Technology is installed. In our case it was installed in the default
directory of C:\WebSphere\PortalServer\IBMTrans.
3. You must change the transcoding configuration to enable RMI registry and
enable two of the transcoding plug-ins, DatabaseWatcherPlugin and
ViewerServerPlugin. To do this, perform the remaining steps.
4. Run the ExportResources command to export the resources that must be
modified. The specific command is:
ExportResources -rt setup -rt
plugin,DatabaseWatcherPlugin,ViewerServerPlugin
5. A WTPResources.xml file is placed in the transcoding directory (IBMTrans).
Open this file for editing and make the following changes:
a. For both the DatabaseWatcherPlugin and the ViewerServerPlugin plug-ins
(which are defined as <Plugin> elements) add the statement shown in
Example 8-1 before the </Plugin> tag, to enable the plug-ins.
Example 8-1 Enable the plug-ins
<Plugin>
.............
<Enable>true</Enable>
</Plugin>
b. Enable the RMI Registry, which is the <RMIRegistry> element, as shown
in Example 8-2.
Example 8-2 Enable RMI Registry
<RMIRegistry>
.....
<Enable>true</Enable>

Get IBM WebSphere Everyplace Access V5 Handbook for Developers and Administrators Volume II: Application Development now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.