Setting up your Plex model for CA Plex v5.0 and v5.1

Contents

• Introduction
• Add Websydian Pattern Libraries to the Group Model
• Extract Definitions from Websydian Library Models
• Specify Pre-built Library and Header Files
  • iSeries
  • Windows
  • Java
• Model Configuration for the Websydian Library Models
• Generate and Build Library Objects
• Runtime Objects
  • iSeries
  • Windows
  • Java

Introduction

This section explains how to set up CA Plex local model to work with the Websydian pattern libraries. This document applies to CA Plex versions 5.0, and 5.1.

The actions described in this document must be performed the first time you use the Websydian patterns in an CA Plex model.

Add Websydian Pattern Libraries to the Group Model

The first thing to do is to add the relevant Websydian library models to the host group model of your application. This action is performed once per group model in the same way as adding any other library models to a host model.

The Websydian library models may be added during creation of a group model together with the CA Plex Pattern libraries and other library models needed by the model, or they can be added to an existing CA Plex group model.

Extract Definitions from Websydian Library Models

Once the Websydian library models have been added to the group model and a local model has been defined, the objects in the Websydian library models must be extracted to the local model.

Specify Pre-built Library and Header Files

When a local model with the relevant Websydian libraries extracted has been created, the developer is required to setup a number of pre-built C++ library files and header directories for Windows and a number of user class libraries for Java.

Depending on the language selected by the variant of WSYBASE the required files differ.

iSeries

This section applies to local models where the variant for WSYBASE has been set to DWA - iSeries or iSeries web server.

The table below (table 1) indicates which pre-built C++ library files to include. It is recommended to add all of the listed library files.

To setup the pre-built C++ library files in the CA Plex group model follow the steps below:

1. Open the "System Definitions" dialog located under the "Generate and Build Options".
2. In the "32-bit C++ Build" section activate "Use pre-built libraries".
3. Add each of the library files listed in the table above (table 1) to the "Libraries" field. Make sure to add the full path of each library file and delimiting each library file by a semicolon (;).
4. Add the Websydian header folder "<Websydian Install Folder>\development\include" to the field Header Directories.

Examples

Libraries

c:\Websydian\development\lib\Plex5.0\websyd.lib

Header Directories

c:\Websydian\development\include

Windows

This section applies to local models where the variant for WSYBASE has been set to DWA - Windows or PC web server.

The table below (table 1) indicates which pre-built C++ library files to include. It is recommended to add all of the listed library files.

1. Open the "System Definitions" dialog located under the "Generate and Build Options".
2. In the "32-bit C++ Build" section activate "Use pre-built libraries".
3. Add each of the library files listed in the table above (table 1) to the "Libraries" field. Make sure to add the full path of each library file and delimit each library file by a semicolon (;).
4. Add the Websydian header folder "<Websydian Install Folder>\development\include\VC 6.0" to the field Header Directories.

Examples

Libraries

c:\Websydian\development\lib\Plex5.0\websyd.lib;
c:\Websydian\development\lib\Plex5.0\wsydxml11.lib;
c:\Websydian\development\lib\Plex5.0\wsydxml11_dll.lib;
c:\Websydian\development\lib\Plex5.0\wsyhttp400.lib;
wininet.lib;ws2_32.lib;c:\plex\plex 5.0\class500\patternlibs\obpt32.lib

Header Directories

c:\Websydian\development\include

Java

When using DWA for Java (variant for WSYBASE set to DWA - Java), a number of JAR files should be specified as user classes; see table below (table 2).

To setup the user classes in the CA Plex model follow these steps:

1. Open the "System Properties" dialog located under the "Generate and Build Options".
2. Select the "Java Build" section.
3. Add each of the JAR-files listed in the table above (table 2) to the "User classes" input field. Make sure to add the full path of each JAR-file and delimit each JAR-file by a semicolon (;).
4. Make sure that the input field "Nmake directory" refers to the directory where the Nmake application is located.
5. Make sure that the input field "Compiler" refers to the java compiler (javac.exe). Default location is in the bin directory of the Java SDK.

Example

The JAR-file list to insert in the 'User classes' field could look similar to the example below:

c:\Websydian\development\jars\WsydDwa21.jar;
c:\Websydian\development\jars\WsydUtil.jar;
c:\Websydian\development\jars\WsydXml11.jar;
C:\Plex\Plex5.0\Class500\PatternLibs\Obptjava.jar

Model Configuration for the Websydian Library Models

In the model configuration for the host group model the Websydian WSYBASE library must have its variant set according to the chosen target platform:

The variant of WsyHttp, SDString, and WsyDom should be set according to the language of the variant of WsyBase.

The version/level for each of the Websydian group models should be set to the newest.

The table below shows the newest version/level to use for each of the Websydian group models:

Generate and Build Library Objects

Most Websydian library models include a number of objects that are used directly by other pattern objects. These objects must be generated and built. In Websydian, these objects are included in an appropriately named subject area, e.g. AuditObjectsToGenAndBuild.

The following library models include objects that must be generated and built.

Runtime objects

When deploying a Websydian application, either for testing or production, various Websydian runtime objects are required for the application to run properly.

The runtime objects are located in the folder <Websydian Install Folder>\Deployment. Please consult the section that is relevant for your deployment environment.

iSeries

The table below shows the objects that must be restored when deploying a Websydian application on an iSeries.

For more detailed instructions on how to install the Websydian iSeries runtime objects please refer to this document.

Windows

The table below shows the DLLs that must be deployed with a Websydian application on the Windows platform.

The DLLs can either be deployed in the same folder as the application DLLs or in a folder specified in the system path.

Java

The table below shows the jar files that must be specified in the classpath when launching a Websydian Java application. For more details on setting up the classpath please refer to this section.