For some process activities it is possible to configure custom process messages.

Basic IWS modules are offering interface i_tws_msg, which can alter process message according to your needs.

Custom messages can be placed to xml dictionary twaz_custom_dictionary.xml, which is located in directory etc/dictionaries.

File twaz_custom_dictionary.xml can be edited by any XML enabled editor.

1. In file twaz_custom_dictionary add new element di. Set id attribute to unique key. To child element en add your text in English language, to child element de add your text in German language.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dictionary SYSTEM "dictionary.dtd">
<dictionary languages="en;de" update="2008-07-31">
<dis>
<di id="SAMPLE-Message">
  		<en>Sample message for IWS handover.</en>
  		<de>Beispielnachricht für IWS handover</de>
</di>
</dis>
</dictionary>

Find in PHP process definition interface i_tws_msg in your target task. Example:

'input' => array (
     'i_tws_msg' => 'msg="CompletedStep", 
                    msg_translate=true, 
                   msg_type="message"' 
              ),

Change the msg property of interface i_tws_msg to match the id attribute from step 1.

'input' => array (
     'i_tws_msg' => 'msg="SAMPLE-Message", 
                    msg_translate=true, 
                   msg_type="message"' 
              ),

It is possible the dialog, in which user specifies the criteria for searching for AD applications.

In app_sec in INIT section that corresponds with the process specify the properties for input.

Example 1: Process IWSZ_NEW settings that sets input for Owner ID to readonly and hide input for Owner description

USER IWSZ1
   CLIENT=*+ROLE=*+LOGON=*+REQUEST= IWSZ_NEW
BEGIN
    INIT        
       *^T0140^T_TWS_AD_APPL_NEW_MODIFY_01^ADSEL.ADSL001.OWNERID_TXT      readonly=true 
        *^T0140^T_TWS_AD_APPL_NEW_MODIFY_01^ADSEL.ADSL001.OWNERDESC_TXT  hidden=true disabled=true
END
END

The resulting dialog

It is possible to use in APP_SEC HWM Variables from process definition.

In app_sec is used syntax {}%(parameter_name).{}

Example 2: – use of value HWM variable TL to set value to input Application ID

 T^T0110^CPOPSEL.SELECT_FORM.APPLID_TXT value="_%(TL)._"

When creating app_sec it is very useful to use Options->Show Elements IDs->All

For ProcMan 4.0.11. and later you can put restrictions to the AD list to individual users or ProcMan groups. The (key) settings are always connected to three parameters:

ProcMan Client, Process name, Limit setting (a flag or string in process configurations and tws_sec table).

Limit setting can be specified in modules m_tws_ad_appl_sel and m_tws_ad_appl_load.

In module m_tws_ad_appl_sel it is configured in interface i_tws_ad_appl_sel.

In module m_tws_ad_appl_load it is used in interfaces for selections: i_tws_ad_appl_sel_mod, i_tws_ad_appl_sel_del.

Interface i_tws_ad_appl_sel_mod is used to select AD for modification and copy.

Interface i_tws_ad_appl_sel_del is used for selection AD for delete.

Example setting in process config, sel setting is used for modification and copy, del setting is used for delete

'name' => 't0140',
        'type' => 'task',
        'module' => 'm_tws_ad_appl_load',
          'input' => array (
             'i_environment' => '',
             'i_tws_ad_appl_sel_mod' => 'tws_target_system="source",
                 interrupt=false, limit="sel"',
             'i_tws_ad_appl_sel_del' => 'tws_target_system="source",
                 interrupt=false, limit="del"',
             'i_tws_ad_appl_mod' => 'interrupt=true',
             'i_tws_ad_appl_ins' => '',
             'i_tws_ad_appl_del' => 'interrupt=false',
             'i_tws_ad_oper_load'=> 'silent=false',
   ),

In the bin directory of ProcMan is commandline utility tws_sec. This utility can import or export settings from csv file.

Columns in csv file

• Role – ProcMan role

• User – ProcMan Account (login user)

• Adid – IWS Application ID

• Adowner – IWS Owner ID

• Adgroupid – IWS Authority group ID

• Jobname – jobname, this column can be used in ProcMan 5.0.3 and higher

For all setting you can use wildcards:

• wildcard represents zero, one or multiple characters

% wildcard represents exactly one character

Example hos_sec.csv file with settings,

role,user,adid,adowner,adgroupid

role,user,adid,adowner,adgroupid
D*,P370V,%V*,,
D*,P370V,T*,,
D*,P371B,%P*,,
D*,P371B,T*,,
D*,P3*,TE*,P*,

For all setting you can use parameters from ProcMan process with the expression %(<parameter name>).

Example for security using ProcMan parameter ADHOC_APP loaded from ProcMan process

role,user,adid,adowner,adgroupid
D*,P370J,%%%(ADHOC_APP).*,,

Conditions in one line are connected with logical AND operator – role D* AND user P370V AND application ID is %V*.

More lines with identical user and role are connected with logical OR operator, in our example for role D* and user P370V the applications ID can be %V* or T*.

In cmdline you can import this csv file to ProcMan client HORIZONT and process IWSZ_TEST with command

tws_sec -f hos_sec.csv -c HORIZONT -p IWSZ_TEST -l sel -o import

to get the syntax enter tws_sec without parameter or with -h:

tws_sec -h 

script for export and import of security data for ProcMan -IWSz
  -h  Show this help menu
  -o  Option for manipulation -  import, export, delete, show
  -f  Filename for command output or input
  -c  ProcMan  client name
  -p  ProcMan  process name
  -l  ProcMan  setting limit in process config
  -m  file export mode, w - overwrite existing file, a - append existing file
example usage:
 tws_sec -o show
  - shows summary of all security data
 tws_sec -f sec1.csv -c HORIZONT -p IWSZ_ADHOC -l sel -o import
  - import data from file sec1.csv to ProcMan  process IWSZ_ADHOC,
     client HORIZONT, limit setting sel
 tws_sec -f sec2.csv -c HORIZONT -p IWSZ_ADHOC -l sel -m w -o export
  - export data to file sec2.csv from ProcMan  process IWSZ_ADHOC,
     client HORIZONT, limit setting sel
 tws_sec -c HORIZONT -p IWSZ_ADHOC -l sel -o delete
  - delete data from ProcMan  process IWSZ_ADHOC, client HORIZONT,
      limit setting sel

The security setting always apply only one combination of role and user that has the best match for the current user.

In our example when user P370V log in process IWSZ_TEST then settings for user P370V and role D* are applied, the general setting for user P3* and D* is ignored.

In our example when user P370C log in process IWSZ_TEST then settings for user P3* and D* are applied, all specific settings for users P370V and P371B are ignored.

Alternative to csv file it is possible to insert data directly to database table twaz_hos_sec by SQL INSERT.

Columns in Table procman.TWAZ_HOS_SEC (all varchar):

• FLAG,

• CLIENT_NAME,

• PROCESS_NAME,

• ROLE_NAME,

• USER_NAME,

• ADID_COND,

• ADOWNER_COND,

• ADGROUPID_COND,

• JOBNAME_COND

Sample Insert, to allow user P370V to select in process IWSZ_TEST applications T* only:

 
INSERT INTO procman.TWAZ_HOS_SEC VALUES (      
   'sel',                                      
   'HORIZONT',                                 
   'IWSZ_TEST',                          
   'D*',                                       
   'P370V',                                    
   'T*',                           
   '',                                         
   '',
   ''                                          
   );                                          

It is possible to configure the behavior of pickers that are used in dialog that edit tws application. This pickers are showing possible values for some fields in IWS dialog.

Example of picker list that displays possible values for authority group id

The following picker lists can be customized:

• Owner ID

• Authority group id

• Calendar id

• Group definition

One way how to customize picker is to use app_sec that has inside values for picker list. This method is preferred when you are using list of values that are not frequently change during time.

The following app_sec setting

Will change the picker list to show 4 predefined values for calendar

This chapter describes the topic of parallel modifications of one IWS application in more than one PMN process. By default, the modification of IWS application in more PMN processes is denied and the PMN user get the the following error message.

To enable the parallel modification in IWS process you have to change the process configuration. For the modify operation that use the button ‘Start Modify AD’ you have to add configuration option parallel_mod=true to interface i_tws_ad_appl_sel_mod in module m_tws_ad_appl_load. In case when the process is using cloning with cloning module m_tws_ad_appl_clone, add to it the interface i_tws_ad_appl_sel with the setting parallel_mod=true.

For the copy operation that use the button ‘Start Copy AD’ the modifications of IWS applications are by default enabled.

Example process config for cloning process with parallel modifications:

array(
        'name' => 't0140',
        'type' => 'task',
        'module' => 'm_tws_ad_appl_load',
        'input' => array(
                'i_environment' => '',
                'i_jcl_approved_files' => '',
                'i_tws_ad_appl_ins' => '',
                'i_tws_ad_appl_load' => 'show_current=true, empty_source=true, tws_update=false, cancel=false',
                'i_tws_ad_appl_sel_mod' => 'tws_target_system="source", interrupt=true,parallel_mod=true',
                'i_tws_ad_appl_del' => 'interrupt=false',
                'i_tws_ad_oper_load' => 'silent=false',
                
        ),
        'output' => array(
                'i_goto' => '',
                'i_environment' => '',
                'i_tws_ad_selection' => ''
        )
),
array(
        'name' => 't0155',
        'type' => 'task',
        'module' => 'm_tws_ad_appl_clone',
        'input' => array(
                'i_goto' => 'cancel="t0140",list="t0140"',
                'i_environment' => '',
                'i_tws_ad_appl_sel' => 'parallel_mod=true',
                'i_tws_ad_copy_all_appl' => 'same_adid_act="mod"',
                'i_tws_ad_clone' => 'conf=['.
                '[type="clone", addata_prefix=["DEV", "TEST", "PROD"]],'.
                '[type="tws", rule="rule_defaults"],'.
                ']'
        ),
        'output' => array(
                'i_environment' => '',
                'i_goto' => ''
        )
),

To disable the parallel modification in IWS process you have to change process config for Copy operation. Add to interface i_tws_ad_appl_copy in module m_tws_ad_appl_load setting create_mods=false. For modify operation the parallel modification is by default disabled.

This configuration will enable to load data for picker list from dataset. Advantage of this approach is that it allows to manage regularly the values in pickers.

Prepare csv file picker.csv with data for pickers, it should be list of values in which all rows are ended with comma.

ALLDAY,
BAYERN,
BERLIN,
DEFAULT,

Copy file picker.csv to bin directory of ProcMan . Load the values from file using command line utility tws_rules_lut.cmd . Run command

Tws_rules_lut – o import –i picker –f=“picker.csv“  

You should see message

imported 4 rows to lookup table

To PHP process config file to module m_tws_ad_appl_load interface i_tws_ad_appl_mod add the option picker_conf. The setting picker conf is list (associative array). Array key is name PIF name of field in AD picker (possible key values adcal,adgrpdef,adgroup,adowner) , array value is name of tws rules lookup in database. To enable lookup with id picker to calendar picker list add

picker_conf=[adcal="picker"]

When your press modify button it in the activity with module m_tws_ad_appl_load you should see following dialog.

It is possible to customize user used to update or read IWSz data with settings from ProcMan environment.

In ProcMan environment is possible to setup in ProcMan activity setting iwsz_tech_user, this setting overwrites the settings set in “IWS systems administration and settings”.

Setting iwsz_tech_user is on first level divided to IWS system, symbol * apply to all IWS systems or exactly name od IWS system.

Inside setting for IWS system are three settings: user, pwd, actions.

Setting user is username of technical user.

Setting pwd is encrypted password of technical user.

Setting actions is array of update actions, symbol * means any action, value ad_upd means update of AD record to z/OS, value cp_read means read of CP records from z/OS, value cp_upd means update of CP records to z/OS

Example ProcMan environment setting that uses technical user T567A for update of AD records to IWS system OPIT

'iwsz_tech_user'=>array (
  'OPIT' => array (               
	'user' => 'T567A',             
	'pwd'  => '==F5j3wR6Jcw3ddXYSWEEHiBN6T1HcdD5liPrPskL1PPFonJwKVOlTcw==',
'actions' => array ('ad_upd' => true),
     ),
   )

Example ProcMan environment setting that uses technical user T568B for update of CP records to any IWS system

'iwsz_tech_user'=>array (
  '*' => array (               
	'user' => 'T568B',             
	'pwd'  => '==F5j3wR6Jcw3ddXYSWEEHiAM6T1HcdD5liPrPskL1PPFonJwKVOlTcw==',
	'actions' => array ('cp_upd' => true),
     ),
   )

In process definition it is possible to configure parameters. These parameters are entered by user at process start and can be later used for IWS system selection.

Process definition parameter can directly contain IWS system name and this value is then used by IWSz process environment.

For example we have two IWS systems IWSA and IWSB. To process definition we define parameter IWSYS with two possible values IWSA and IWSB. To process environment for ProcMan activity we define usage of parameter IWSYS this way:

activity' => array (
     'TWS_MODULAR_TEST' => array (
         'environment' => array (
             '!Test environment 1' => array (
                 'task' => array (
                     '*' => array (
                         'tws_source_system'  => array ('%(IWS_SYSTEM).')
                     )
                 )
             )
         )
     )

Process definition parameter can be used indirectly as key to IWS systems list. This approach is reasonable for configuration with more IWS systems and more ProcMan activities. In process environment are used two settings tws_source_system_selected_index and tws_target_system_selected_index.

For example we have four IWS systems IWSA, IWSB, IWSC, IWSD. One process definition parameter GROUP has values TEST1 and TEST2. In process environment we specify usage of IWS system workflow:

• data from IWS system IWSA are copied to IWS system IWSC

• data from IWS system IWSB are copied to IWS system IWSD

'IWS_AUTOEXEC_1' => array (
   environment' => array (
      '!Test environment 1' => array (
           'task' => array (
               't0130' => array (
                   'tws_source_system'  => array ('IWSR'),
                   'tws_target_system'  => array (
                                                  'TEST1'=>'IWSA',
                                                  'TEST2'=>'IWSB'
                   ),
                   'tws_target_system_selected_index' =>'%(GROUP).'
               ),
               't0230' => array (
                   'tws_source_system' => array(
                           'TEST1' => 'IWSA',
                           'TEST2' => 'IWSB'
                   ),
                   'tws_source_system_selected_index' => '%(GROUP).',
                                   'tws_target_system'  => array (
                                               'TEST1'=>'IWSC',
                                               'TEST2'=>'IWSD'
                                   ),
                   'tws_target_system_selected_index' =>'%(GROUP).'
                ),
           )
        )
    )
),