Online documentation - Websydian v6.5 |
Overview Library Deployment Operation
This white paper describes the basic steps to deploy a CWA
Websydian application on the iSeries platform using either IBM HTTP
Server or Apache HTTP Server.
Basic knowledge about the iSeries platform is required in order to
successfully complete this white paper.
Prerequisites:
Copy the Document Templates to an iSeries folder in the IFS, e.g. /WEBTUTOR.
QTEMP
WEBTUTOR
WSYD600PTF
WSYD600
PLEX500
QGPL
If needed change the user profile for the job description.
Default is YOBSYDIAN.
- If using the HFS to store the folders, the user profile used in the job description must be created in the directory entry so the Websydian application has access to the templates in the folder system. Use the command DSPDIRE to verify this.
- The user has authority to use the folder where the templates reside.
- The user has authority to use the library where the Websydian applications resides including the WSYDxxx library.
- The user has authority to use the databases used by the Websydian application.
- Make sure the user profile QTMHHTP1 has at least *USE authority to programs, and any files referenced by the Websydian application.
- Make sure the user profile QTMHHTP1 is not disabled (*DISABLED). Use the command DSPUSRPRF to verify this.
The iSeries uses the EBCDIC character set but document templates are stored in ASCII and the web server also sends and receives information from the browser using ASCII (or more correctly ISO-8859-1).
For this reason the Websydian application must be configured with relevant information about the character sets used so the correct character translation can take place.
For document templates
In Websydian 3.0 and later the character set identifier (CCSID) of the document templates should be stored in the data area IFSCCSID. Default is 01252 (Windows Latin-1).
In Websydian 2.5 and prior the character translation of the document templates are handled by the translation table ASCII2E. The default table complies with Windows Latin-1.
For input and output to the Web Server
In Websydian 3.1 the character translation of inbound and outbound URL encoded characters are handled by the data areas CGIICCSID and CGIOCCSID.
In Websydian 3.0x and prior the translation of inbound URL encoded characters are handled by the translation table WLATIN2E. The default supplied table complies with Western Latin-1.
n this white paper we will use the facility of the web server to translate all in and outbound characters and you should make sure the data areas are set to 65535 and if using Websydian 3.0 or prior use a dummy table for the WLATIN2E translation table.
The value 65535 indicates that no translation will be performed by the Websydian application.
For further information on CCSID's see the iSeries manual:
Title: iSeries
International Application Development V4R2
Document Number: SC41-5603-01
Build Date: 12/01/97 19:46:21 Build Version:
1.3.0
Book Path:
/home/publib/epubs/book/qb3aq501.boo
This white paper assumes that the Web Server and the application resides on the same iSeries machine. It is possible to have the Web Server and the application on two different iSeries machines. For more information on how to do this please consult the Websydian documentation.
Run the command WSYDCRTQ found in the library WSYD610.
The WSYDCRTQ command starts the Websydian data queues and a listener job for each. The data queues are used to pass information from the Web Server to the Websydian application. More information can be found here.
To ease any troubleshooting during development, only start one queue.
The parameters are described here. As all parameters are important it is essential that all the settings above are understood.
If using the IBM HTTP Web Server skip this section and read the previous section instead.
To use the commands described in this section you must have QSECOFR rights.
The examples in this section uses the default Apache configuration called APACHEDFT that is installed by default when installing OS/400 on the iSeries.
There are two ways to configure the Apache Web Server: Using the web administration interface or altering the configuration files manually (used in this white paper).
Use the command WRKLNK to find the file /www/apachedft/conf/httpd.conf and select option 2 (edit).
Add a script alias and directory section for servicing the Websydian application.
Add an alias and directory section for servicing images, static HTML pages, Style Sheets, etc.
Restart the Web Server using the command STRTCPSVR. Always remember to restart the Web Server when configuration files have been changed.
STRTCPSVR SERVER(*HTTP) RESTART(*HTTP) HTTPSVR(APACHEDFT)
For further information about iSeries and Websydian read this document
For further information about the Apache Web Server go the to
following sites
For additional information on the IBM HTTP Web Server please refer to the IBM manual:
Title: HTTP Server for iSeries Webmaster's Guide
V4R4
Document Number: GC41-5434-04.
In order to end the Websydian data queues use the command WSYDDLTQ. For starting the Webydian queues again call the WSYDCRTQ.