Translations:PRINT:WBS:WebSmart/2/en
Setting up the WebSmart interface
Setting the library list
The library list for users who are working with TD/OMS must include the WebSmart product library (default it is called XL_WEBLIB).
Environment Maintenance
You have to define IFS routes where the WebSmart definition files (.pdw and .phw) will be stored.
Route definitions
In Environment Maintenance (STREM) a route has to be defined for each environment. The route definition should have a "Dump source location" to be able to archive the WebSmart definition files.
Archiving for WebSmart Definitions
To activate the source archiving you must register for which type of IFS-files TD/OMS should start archiving. At least the .pdw and .phw have to be archived, this can be done by using the entering the command:
OMQCHGSR ACTC(*ADD) APPL(appl or blanks for all applications) ENVC(*NONE) ROTC(route or blanks for all Routes) KEYW('OMIFSSRCEXT ') KEYV('PDW PHW ')
For more information about archiving see the Source Concept Guide
Connection Rule Maintenance
The WebSmart definition objects (*.pdw) require that related program components are connected to the task when connecting a WebSmart definitions component. The logic is defined with the Connection Rule Maintenance function.
When connecting a IFS component of type .pdw it is required to also connect the *PGM components generated by WebSmart.
The following connection rule definitions are required to achieve this.
The WebSmart PHP definition objects (*.phw) require that related PHP IFS components are connected to the task when connecting a WebSmart PHP definitions component. A seperate connection rule must be created to achieve this:
Please keep in mind that these new rules may need to be added to other connection rules (eg the rule for PF objects).
To ensure that the connection rules are always executed when connecting a component a registry entry must be added. Adding a registry entry is done with the TD/OMS System Registry API (OMQCHGSR). The command to enforce connection rule processing is:
OMQCHGSR ACTC(*ADD) APPL(&APPL) KEYW(FORCECONNRULE) KEYV('1')
&APPL must be replaced with the code of the application that you have created.
Extended Relation Processors
The interface comes with logic to analyze the WebSmart source code. This source code is used to determine file and program dependencies. In order to activate this program, there must be two entries in the OMERP file. You can view the contents of the file with DSPPFM:
DSPPFM OMERP
Confirm that the following records exist:
*STMF PDW 0 OMX053C 0 *STMF PHW 0 OMX053C 0
If one or both of the entries are missing you have to add them manually with SQL. Perform the following SQL statements to insert the records into the "OMERP" table.
INSERT INTO OMS/OMERP VALUES('*STMF', 'PDW', '0', 'OMX053C', '0')
INSERT INTO OMS/OMERP VALUES('*STMF', 'PHW', '0', 'OMX053C', '0')
Defining WebSmart Actions
TD/OMS Ships with some Actions that will help you manage the WebSmart objects.
Update the PDW source to set the program attributes
The program attributes can be set by TD/OMS when a WebSmart source is checked out.
Create the following Action:
OMC001 Action Maintenance 20-06-23
OMC00102 Maintain Action 17:38:30
CHANGE
Action .................: Update WebSmart Program Attributes
Action command .........: STRPRCOMS
Action cluster .........: WEBSMART F4=List
Action key number ......: 12335
F3=Exit F5=Refresh F8=Selections F10=Details F12=Cancel
Define the STRPRCOMS command as follows:
Start TDOMS Action procedure (STRPRCOMS)
Type choices, press Enter.
Program . . . . . . . . . . . . > OMUSRWS02 Name
Library . . . . . . . . . . . *LIBL Name, *LIBL
TDOMS Interface level . . . . . > *V5R1M0 *V3R0M0, *V5R1M0
Set the WebSmart Path Template
To set the WebSmart path template for your environment, use the following setting.
Reuse the Update Program Attributes Action as a User Option
Create a User Option for a Solution visible on the Client and the Server and executed on the Server. This User Option lets you manually update the program attributes for WebSmart files.
Define the following User Option Command:
User Option Maintenance
OMX20203 Maintain User Option 20-06-23
Option . . . . . . . . : WR
Description . . . . . . . Update WebSmart Program Attr.
Private for User . . . . *ALL
Action Group . . . . . . _WebSmart
Authorization code . . . 2 1-3, 0=Disabled
Check entry . . . . . . . 1 0=No, 1=Yes
Entity . . . . . . . . . 04 01=Req, 02=Fix, 04=Sol, 08=Obj
Where to Activate . . . . 1 0=Client, 1=Server
Where Visible . . . . . . 2 0=Client, 1=Server, 2=Both
Pass parameters . . . . . 1 0=No, 1=Yes
Program . . . . . . . . .
Library . . . . . . . . . Name, *LIBL
Command . . . . . . . . . APYACTOMS IFSOBJ('&OBIDRC&OBIOBC') ACTION(12345)
Result:
