Q:How can I use JavaScript and run submit event? I know that I can have the webspeed/e-framework engine place variables such as h_token in forms stored in HTM files on the fly. Can I have this
engine place the h_token else where in the HTM file such as with in a javascript?
It displayed HTM file, but it doesn't work...

A: 1) Define the javascript function new_link() in htm file before form (maybe
after head tag).
<script language="JavaScript">
<!--
//
// Try to submit this form when user pressed a link in a WDM compliant
kind of way.
//-->

function new_link(action)
{
document.main.h_link_action.value=action;
document.main.submit();
} // new_link
</script>

2) The <a href...> tags need to use new_link.
Here's what a link needs to look like:
<b><a onClick="javascript:new_link('Sales Order Entry');">
Sales Order Entry
</a>


3) Define h_link_action in the web object as other session variables like
h_token.
The field "h_link_action" must be defined in htm file as
<input type=hidden name=h_link_action>
and also .w file as m-token or h_status variables are defined.


4) The form must be named.
The form itself must be named. The links will refer to the form's name.
<form action=menucs.w method=POST name=main >

5) Event 'Sales Order Entry' must be define in event master.

/* Standard List Definitions */

Q: Where is setting up system default passwords?

A: Under Security Maintenance Menu, there are Default password maintenance.
It is connected to Preference Master Maint.
When creating a new user without entering a password this password is
defaulted to a value in a pf_mstr record.

pf_us_id = "SYSTEM"
pf_group = "USER_MAINTENANCE"
pf_attr = "DEFAULT_INITIAL_PASSWORD"
pf_value = Default Password

A: You can use Search Propath function to check your propath.

Q: Can you tell me how to make FILE button work? we noticed the following error on selecting "Files" in the WOG.

" Content-type: text/html n** "/local1/mfg85f/us/src" was not found.(293) "

A: About File System Navigator(File from WOG), if you update Preference
Master(pf_mstr) as following for the user id you used to login, the error
message "local1/mfg85f/us/src" should be gone. You can update pf_mstr using
Preference Maintenance.
Now your pf_mstr should have Value(pf_value) of "local1/mfg85f/us/src".

you can upate this as following...

User ID(pf_ud_id): user id used to login
Group(pf_group): File System Navigator
Attribute(pf_attr): Run-time User Preferences
Value(pf_value): ./ (priod and slash)
and leave other field as default.

Also can you go to Event Master and find event b_help for wog00.htm and see if the following data exists?

Form Name: wog00.htm

Event Name:b_help

Action: wdmhelp0.p

Input Parameter: ./efw/woghelp.htm

Order:0

API Event: UIE

Q:How can I implement unixmail.p in my program? I want to implement unixmail. p in my program. Could you tell me how it is implemented generally?

A: Ok Usually E-mail Recipients data is stored in pf_mstr. You can create unique pf_mstr data for the recipients if it does not exist. or you can even hard code the list of recipients in your program.

and before you run unixmail.p, you can find for the pf_mstr.
v-email-list = pf_chr1.
you can also hard code the recipients list in the program.

vc-from = "isshelpdesk". vc-subject = "Hello from ISS Helpdesk".

do i = 1 to num-entries(vc-mail-list):
vc-mailTo = entry(i,vc-mail-list).
run unixmail.p
( input vc-mailTo ,
input vc-from,

input vc-subject,
input vc-tempFile, <-can be file or message body here.
input "fromfile" ).
end.

---------------------------------------------
run unixmail.p (input send-to,
input send-from,
input subject,
input message body,
input flags).
where
send-to - email to address
send-from - sender address or name
subject - title of your e-mail
message body - you can create temp file for message or chr(13) delimited line.
flags - use "fromfile" if temp file is specified in message body.

use "chr13-delimited" if calling procedure is using chr(13) delimited line
use "" (blank) for just message line.

The supported tables are: token_mstr, pf_mstr, and msgd_det.

For token_mstr...

1) Token master records that are more than [days] old.

2) Any associated ov_mstr records.

3) Any associated wog files.

For pf_mstr...

any pf_mstr data for which no user exists.

For msgd_det ....

1) msgd_det records that are more than [days] old..

2) Any associated msgh_mstr records

-param table_name=days:table_name=days....

where

table_name : Name of the table to purge.

days : The age of the records to purge in days.

If you are purging only token_mstr, then don't worry about the second table and days.

You should have wdmpurge.sh which is the script to run wdmpurge.p.
You have to modify this script to fit for your environment.
Here is the line from the script..
$DLC/bin/mpro $TPTHOME/db/wdm -p $TPTHOME/wdm/src/wdmpurge.p -param
$1 -b

DLC and TPTHOME must be set for your environment.
$1 is the parameter you pass to the script for the tablename and date, but
you could type this line instead of running the script.

A: Under Security Maintenance Menu, there are Default password maintenance.
It is connected to Preference Master Maint.
When creating a new user without entering a password this password is
defaulted to a value in a pf_mstr record.

pf_us_id = "SYSTEM"
pf_group = "USER_MAINTENANCE"
pf_attr = "DEFAULT_INITIAL_PASSWORD"
pf_value = Default Password

Q: Password expiration, failed login disability

A: This functionality gives the system the ability to force password
change periodically and creates a level of user security.

Two new fields were added to the user maintenance screen wdmum. Expiration
and disabled.

Password expiration:
When a new user is created, a pf_mstr record is referenced to identify how
long the password will be active. The default value is 60 days.

pf_mstr:
pf_us_id = 'system' pf_group = 'security'
pf_attr = 'expire days' pf_value = '60'
pf_alt_value = '5'

You can increase or decrease this span by changing the pf_value field to any
number you choose (except 0) This value will be applied to all new users.

At the end of 60 days, or the value chosen, the password will expire. The
user will be forced to change their password. When changed, the expiration
date will be set to a date n days in the future. (The current date plus the
pf_value value.)

If you want this function disabled, after the user is created, empty the
expiration date. The user's password will not expire.

The pf_alt_value shows a reminder to the user that their password will
expire in n days. The default is 5. This value must be less than the
pf_value quantity.

Disable login:
If the user attempts to login and fails at least 3 times the system will
disable his account.

The system administrator must go to the User maintenance screen, wdmum, and
enable his account. (uncheck the disabled check box.)

Q: Can you restrict a user from accessing other interfaces? Currently menu level security is turned on but we do not even want the user to see the menu.

A: Absolutely! You simply need to create a preference master for the user that will force them at login to one interface. The format of the preference master is below:

User: [the user id that you wish to restrict]

Group: INTERFACE-HANDLERS

Attrib: DEFAULT-INTERFACE

Value: [The interface that the user is restricted to]

A: 1) Define the javascript function new_link() in htm file before form (maybe
after head tag).
<script language="JavaScript">
<!--
//
// Try to submit this form when user pressed a link in a WDM compliant
kind of way.
//-->

function new_link(action)
{
document.main.h_link_action.value=action;
document.main.submit();
} // new_link
</script>

2) The <a href...> tags need to use new_link.
Here's what a link needs to look like:
<b><a onClick="javascript:new_link('Sales Order Entry');">
Sales Order Entry
</a>


3) Define h_link_action in the web object as other session variables like
h_token.
The field "h_link_action" must be defined in htm file as
<input type=hidden name=h_link_action>
and also .w file as m-token or h_status variables are defined.


4) The form must be named.
The form itself must be named. The links will refer to the form's name.
<form action=menucs.w method=POST name=main >

5) Event 'Sales Order Entry' must be define in event master.

PROGRESS

*** Value -12354879564854 can not be displayed using 9999999999. (74)

*** Unable to open file ??????????.wog. Error=9. (98)

*** Unable to open file ??????????.wog. Error=9. (98)

A:This error is displaying becaue etime value is overflow and has minus value.

To reset etime, run the following code..

{src/web/method/wrap-cgi.i}
output-content-type(" text/html").
{&out} etime(yes).

$DLC/wtbman -name "name of agent" -start

to stop

$DLC/wtbman -name "name of agent" -stop

You can check if the agent is running …

$DLC/wtbman -name "name of agent" -query

{src/web/method/wrap-cgi.i}
output-content-type(" text/html").
{&out} etime(yes).

[UBroker.WS.wdm20]

appserviceNameList: Specifies a list of servers that the unified broker supports. Set to broker name.

autoStart: Specifies whether the Admin Server automatically starts this broker when the
Admin Server is started. Possible values: 0 - no auto start; 1 - auto start Set to 1.

brokerLogFile: Specifies the name of the broker's log file. Set to .broker.log

controllingNameServer: Specifies the name of the controlling NameServer. The broker registers its
location and the application services it supports with the specified NameServer. Set it NS1, the default nameserver.

portNumber: If the location property is set to local, specifies the UDD port at which the
NameServer listens to receive requests. If the location property is set to remote, specifies the UDD port that any broker which has specified this NameServer as its controllingNameServer uses to send registration requests. Use the Webspeed 3.1 Administration Utility (on the host server) to find an
available port.

srvrLogFile: Specifies the name of the NameServer log file.

srvrMaxPort: Specifies the maximum port number available to the server. Use the Webspeed 3.1 Administration Utility (on the host server) to find an available port.

srvrMinPort Specifies the minimum port number available to the server. Use the Webspeed 3.1 Administration Utility (on the host server) to find an available port.

srvrStartupParam: Specifies the startup parameters the WebSpeed server uses when starting WebSpeed
Agents.

uuid: Specifies a universally unique identifier for this broker. This value is used by
the NameServer referred to by the controllingNameServer property to uniquely identify this broker from all other brokers registered with that NameServer.

To generate a new uuid execute: $DLC/bin/genuuid Cut and paste the value.

WorkDir: Specifies the directory where the Broker starts. Set this to your $TPTHOME/wdm/agents directory.