Deploying a Command in EVW and WP

3D PLM Enterprise Architecture	JDialog	Deploying a Command in EVW and WP How to deploy a command with JDialog
Use Case

Abstract

This article shows how to deploy a command with JDialog in Enovia Workplace Viewer or Websphere Portal.

What You Will Learn With This Use Case
The EVW deployment Use Case
- How to deploy a CAACommand in EVW
The WP deployment Use Case
In Short
References

What You Will Learn With This Use Case

This use case is intended to show you how to deploy a JDialog command. It presents two ways of deploying a command:

In EVW (Enovia Workplace Viewer),
in WP (Websphere Portal).

[Top]

The EVW deployment Use Case

Deploying a JDialog command in EVW allow the administrator to purpose new JDialog command to users.

[Top]

How to deploy a CAACommand in EVW

To deploy a CAA command in EVW, you will need three files:

The first one: xxx.XMLWkpLayout:

Windows	`InstallRootDirectory\intel_a\resources\workplaces\xxx.XMLWkpLayout`
Unix	`InstallRootDirectory/aix_a/resources/workplaces/xxx.XMLWkpLayout`

This file describe the workplace. It is made of a set of pages. Each page may contain at least one portlets. A portlet is a JDialog command.

The code sample bellow will present the content of a XMLkpLayout file:

/**
 * EVW deployement descriptor file 'xxx.XMLWkpLayout' .
 **/

<?xml version="1.0"?>

/**
* We define the Workplace .
**/
<Workplace>

/**
* We define all the pages and layout of each component of each page.
**/
<Page Name="CAATableTour">
<GC Name="JDialogTableTour" X="0" Y="0" W="1" H="1" />
</Page>
<Page Name="CAADebug">
<GC Name="JDialogDebug" X="0" Y="0" W="1" H="1" />
</Page>
<Page Name="CAAHookup">
<GC Name="JDialogHookupFW" X="0" Y="0" W="1" H="1" />
<GC Name="JDialogHookupModule" X="1" Y="0" W="1" H="1" />
</Page>

/**
* We define the pagegroup, who contains each Pageinst.
**/
<Pagegroup>
<Pageinst Name="CAATableTour"/>
<Pageinst Name="CAADebug"/>
<Pageinst Name="CAAHookup"/>
</Pagegroup>

</Workplace>

Sample of rendering of the header in EVW

The second one: xxx.XMLeApp:

Windows	`InstallRootDirectory\intel_a\resources\`eapplications`\xxx.XMLeApp`
Unix	`InstallRootDirectory/aix_a/resources/`eapplications`/xxx.XMLeApp`

This file describe each component of a page. It is made of a set of JDialog command and JDialog document..

The code sample bellow will present the content of the JDialogTableTour.XMLeApp file:

/**
 * Page descriptor file 'xxx.XMLeApp' .
 **/

<?xml version="1.0"?>

/**
* We define the eapp .
**/

<eapp_def>
<eapp>

/**
* The JDialog command and document to launch when this Page is selected .
**/
<command>CAATableTour</command>
<document></document>

<icon_n>I_ColorChooser</icon_n>

/**
* The size of the iframe in wich the command will be launch .
**/
<iframe_width>700</iframe_width>
<iframe_height>600</iframe_height>
<native>NO</native>

</eapp>
</eapp_def>

Sample of rendering of the Page in EVW

The third one: xxx.CATNls:

Windows	`InstallRootDirectory\intel_a\resources\xxx.CATNls`
Unix	`InstallRootDirectory/aix_a/resources/xxx.CATNls`

This file describe each component of a page. It is made of a set of JDialog command and JDialog document..

The code sample bellow will present the content of a JDialogTableTour.CATNls file:

/**
 * Page descriptor file 'xxx.CATNls' .
 **/

Title = "JDialog Table Tour";
ShortHelp = "CAA Sample of JDialog tables";
LongHelp = "";

[Top]

The WP deployment Use Case

The Websphere Portal deployment will be made by the administrator of WP.

You can refer to the product documentation.

In Short

Deploying a Command in EVW and WPS involves 4 steps:

Developing JDialog commands,
creating all the necessary files in runtimview,
testing deployment in EVW,
the WP administrator can deploy them in WP.

[Top]

References

[1]	Building and Launching a CAA V5 JDialog Use Case
[Top]

History

Version: 1 [Mai 2003]	Document created
[Top]

3D PLM Enterprise Architecture

JDialog