**Updates:**

**Version 1.5 Changes\...**

**1)** Default Priority for the transmitted message to the highest level
( usage change: call to distributeProduct now uses a A-p 2\" switch).

**Update instructions for v1.5:**

The typical location for the program and files is:
**/awips/dev/localapps/text_admin**

Save a copy of your **text_admin.cfg** file (just in case you accidently
overwrite it)

Rename **text_admin.tcl** to **text_admin.tcl.old**

Move the **meetme.tar** file into a temporary directory, such as
**/tmp**

**De-Tar** the **meetme.tar** file **(tar --xvf meetme.tar**)

Copy the new version of **text_admin.tcl** to the location of your
working program.

**Version 1.4 Changes\...**

**1)** CWSU Support: CWSU=s are now also listed. A product addressed to
a CWSU will contain

the CWSU ID in the message, but will be sent through the hosting WFO.

**1a)** Additional file required: **cwsus.txt**

**Version 1.2 Changes\...**

**1)** \"Right‑Clicking\" on an office ID brings a small popup window up
with

the corresponding name.

**2)** A button has been added below the \"Select WFO\'s\" list called
\"View List

of Names\". Clicking this will pop up a window with the complete list of

office ID with their corresponding names.

**3)** Added a label containing the Leader passcode.

**3a)** Added one line to the configuration file, containing the leader
passcode

\##########################################################################

**Background**

AT&T=s Blastup teleconferencing contract expired on Dec. 6th, 2001. MCI

was awarded the new contract and MCI will be offering different

teleconferencing

capabilities.

Under AT&T\'s Blastup teleconferencing contract, offices which were
invited

to a teleconference automatically received a telephone call which placed

them into the teleconference call. Under MCI\'s teleconferencing
contract,

each office which is invited to the teleconference must call into the

teleconference. The MCI teleconferencing contract does not provide

information about the scheduled teleconference to the offices that are

invited to the

teleconference.

Due to the urgency and timeliness required by some conference calls,
unique

alerts and notification methods have also been developed so that receipt
of

the message containing the conference call does not go unnoticed. A
solution

to informing each office about the MCI teleconference is to use the
AWIPS

system to deliver the invitation to the conference call. Invited

participants in the conference call will now receive a message over the

AWIPS WAN. The message will indicate the following items:

‑ which office originated the message

‑ the date and time of the call

‑ which offices have been invited to the conference call

‑ the phone number and passcode to access the conference call

A set of AWIPS scripts has been developed to support the notification of
the

MCI teleconference calls. At the office which originates the
teleconference,

the AWIPS system transmits the telephone notification message to one or
more

sites in such a manner that only the offices who were selected to

participate receive the message. At the offices which were invited to
the

teleconference, the AWIPS system displays a Red Banner Message informing

each office about the teleconference. The Red Banner Message directs the

invited office to a product which contains additional information about
the

teleconference.

Over the past week, the field offices appear to have settled upon the

WSHNIMNAT PIL as the PIL which will be used to inform invited offices
about

the teleconference call. My preference would be to store the NIMNAT PIL
under

the CCC node identifier of the receiving office. However, since some
offices

have already configured this software for the WSHNIMNAT PIL, this
documentation will adhere to the WSHNIMNAT convention. The WSHNIMNAT PIL
is issued under the NXXX80 KNCF WMO header.

**Meet‑Me Instant Meeting Notification Software**

The Meet‑Me Instant Meeting Notification Software consists of **4** new
files:

**adminmsg.csh**

**text_admin.tcl**

**text_admin.cfg**

**office_ids.txt**

**cwsus.txt**

The adminmsg.csh script runs on the AWIPS systems of those offices who
are

invited to the conference call. The adminmsg.csh script generates a Red

Banner Message on all D2Ds. The Red Banner Message informs the invited

office about the teleconference call and directs the invited office to
the

**WSHNIMNAT** product for information about the conference call. The
Informix

fxatext database triggers should be configured to execute the
adminmsg.csh

script upon receipt of the WSHNIMNAT product.

The text_admin.tcl script and text_admin.cfg configuration file are used
by

the office which originates the conference call to transmit the
WSHNIMNAT

product to the invited offices.

**Installing and Configuring the Meet‑Me Instant Meeting Notification
Software**

**on the ds1 and ds2 servers**

At the time that this document was written, there was no consensus on
how to

database the NIMNAT PIL. The Meet‑Me Instant Meeting Software is hard

coded to use the WSHNIMNAT PIL. However, if it is determined that the

NIMNAT PIL should store under a different CCC node identifier, the
Meet‑Me

Instant Meeting Software will need to be updated to reflect the new PIL.

To install the Meet‑Me software on the ds1 and ds2 servers, perform the

following steps.

1 ‑ Log into the ds1 server as the root user.

2 ‑ Switch user accounts from root to fxa by entering the command:

**su ‑ fxa**

3 ‑ Create a directory called Atext_admin@ under /awips/dev/localapps.
To

create the /awips/dev/localapps/text_admin directory, enter the
following commands:

**cd /awips/dev**

**mkdir localapps**

**chmod 775 localapps**

**cd localapps**

**mkdir text_admin**

**chmod 775 text_admin**

**cd text_admin**

4 ‑ Retrieve the Ameetme.tar@ file from the Local Applications Database
(LAD).

LAD Website is at: http://205.156.54.206/tdl/awips/general_info.htm

5 - Copy the tar file to the directory created above,
/awips/dev/localapps/text_admin/

6 ‑ Untar the meetme.tar file by entering the command:

**tar ‑xvf meetme.tar**

The following 4 files will be unpacked:

**text_admin.tcl**

**text_admin.cfg**

**adminmsg.csh**

**office_ids.txt**

**cwsus.txt**

7 ‑ Using the editor of your choice, edit the

**/awips/dev/localapps/text_admin/text_admin.cfg** configuration file.
The text_admin.cfg file is a configuration file utilized by the
/awips/dev/localapps/text_admin/text_admin.tcl script

to create the WSHNIMNAT product and transmit the WSHNIMNAT product

directly to selected offices. The following variables are templates for
the

WSHNIMNAT product. The variables highlighted in blue are the variables
which

must be changed by each site to meet local specifications.

The ccc_name, nnn_name and xxx_name variables must be set to WSH, NIM
and

NAT respectively in order to match the WSHNIMNAT NXXX80 KNCF entry which

will be added to the /awips/fxa/data/afos2awips.txt file.

The awips_id variable must be set to NCF in order to match the WSHNIMNAT
NXXX80 KNCF entry which will be added to the
/awips/fxa/data/afos2awips.txt file.

**set ccc_name \"WSH\"**

**set nnn_name \"NIM\"**

**set xxx_name \"NAT\"**

**set awips_id \"NCF**\" (must be set to NCF )

**set station_name \"WFO Eastern North Dakota\"**

**set location_name \"Grand Forks, ND\"**

**set meet_me_phone_number \"1‑800‑111‑2222\"** ( the number other sites
call in on )

**set meet_me_password \"123321\"** ( the passcode used by other sites )

**set meet_me_leader_code A123456\"** (The passcode use by
[your]{.underline} office)

**set local_list {abr bis dlh fgf msp}** ( sites commonly included in
your conference calls )

Here is a sample WSHNIMNAT product created by the site specific
variables

defined above. I have highlighted the variables in blue to demonstrate
how

the variables defined in the text_admin.cfg file are utilized by the

text_admin.tcl script.

NXXX80 KNCF 051916

NIMNAT

Alert Administrative Message

WFO Eastern North Dakota / Grand Forks, ND

1915 GMT Wed Dec 05 2001

\*\*\*\*\*\*\*\*\*\*\*TEST\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Due to Severe Weather Potential, A Meet‑Me Conference call has been

scheduled for 19:30 GMT on December 05 for the following offices:

ABR BIS DLH MSP

Phone number for conference is: 1‑800‑111‑2222

Password for call is: 123321

\*\*\*\*\*\*\*\*\*\*TEST\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

The WSHNIMNAT product is transmitted via the AWIPS WAN from the issuing

office to the invited offices. The WSHNIMNAT product is not transmitted
to

the NCF for SBN uplinking. Only the invited offices receive the
WSHNIMNAT

product.

7 ‑ Using the editor of your choice, edit the adminmsg.csh script and
modify

the **CCCNNNXXX** word to **WSHNIMNAT**. Here is an example of the
modified line:

**/awips/fxa/bin/fxaAnnounce \"Meet‑Me Conference Call has been
scheduled. See**

**WSHNIMNAT for details. \" SYSTEM URGENT
/awips/fxa/data/sounds/tinkle.au**

8 ‑ Make the text_admin.tcl and adminmsg.csh scripts executable by
entering

the following commands:

**chmod 755 text_admin.tcl**

**chmod 755 adminmsg.csh**

9 ‑ Move adminmsg.csh script to the /awips/fxa/bin directory on ds1 and
ds2

by entering the following commands. The adminmsg.csh script must reside

on both ds1 and ds2 because when the Informix fxatext database triggers

invoke the adminmsg.csh script, either ds1 or ds2 may be the active data

server.

**mv adminmsg.csh /awips/fxa/bin/adminmsg.csh**

**rcp ‑p /awips/fxa/bin/adminmsg.csh ds2**:/awips/fxa/bin

10 ‑ Set up the Informix fxatext database trigger. First save a copy of
your

original siteTrigger.template file by entering the commands where yymmdd
is

today\'s date:

cd /data/fxa/siteConfig/textApps

cp ‑p siteTrigger.template siteTrigger.template.yymmdd

Using the editor of your choice, edit the siteTrigger.template file and
add

the following line:

**WSHNIMNAT /awips/fxa/bin/adminmsg.csh WSHNIMNAT**

Run mainScript.csh localization script to activate the new set of
Informix

fxatext database triggers by entering the commands:

**cd /awips/fxa/data/localization/scripts**

**. /mainScript.csh ‑trigger**

This completes the installation and configuration of the Meet‑Me Instant

Meeting Notification Software on the ds1 and ds2 servers.

**Installing and Configuring the Meet‑Me Instant Meeting Notification
Software**

**on the HP workstations**

1 ‑ Log into an HP workstation as the fxa account.

2 ‑ Using the editor of your choice, edit the
/awips/fxa/data/afos2awips.txt

file and insert the following line in the correct alphanumeric location:

**WSHNIMNAT NXXX80 KNCF**

3 ‑ Copy the /awips/fxa/data/afos2awips.txt file to the remaining

workstations and servers.

4 ‑ Log into an HP workstation as the awipsusr account.

5 ‑ Save a copy of the current dtwmrc file by entering the commands
(where

yymmdd is the current date):

**cd /awips/fxa/awipsusr/.dt**

**cp ‑p dtwmrc dtwmrc.yymmdd**

6 ‑ Using the editor of your choice, edit the dtwmrc file. Look for the
menu

section used for 2 displays with 1 mouse and 0 keypads then beneath it

search for the Local Applications subpanel menu description. It should
look like

the following example. Although this section will vary from site to site

based upon the local applications running at each site, the line
highlighted in blue is

the entry which adds the Meet‑Me software to the menu.

Note: If there is no local apps subpanel menu, you may need to add the

entire example, shown below, under the WFO Background applications
subpanel

menu description in the dtwmrc file.

**\###**

**\#**

**\# Local apps subpanel menu description**

**\#**

**\###**

**Menu localapps**

**{**

**\"Local Applications Menu\" f.title**

**no‑label f.separator**

**\"Meet‑Me Conference Call\" f.exec
\"/awips/dev/localapps/text_admin/text_admin.tcl\"**

**}**

7 ‑ Reset the Desk Top Window Manager on the workstation by:

‑ using the mouse, right click on the background wallpaper of a D2D
monitor

‑ select **Desktop**

‑ select **Restart Dtwm**\... from the System Control Menu

8 ‑ When the monitors are finished refreshing, test the text_admin.tcl

script by:

‑ using the mouse, right click on the background wall paper of a D2D
monitor

‑ select **Local Applications Menu**

‑ select **Meet‑Me Conference Call** from the System Control Menu

The Conference Call Message Creation GUI should pop open.

If the text_admin.tcl script starts from the Desk Top Window Manager
Menu,

then **copy the /awips/fxa/awipsusr/.dt/dtwmrc file to the remaining**

**workstations**. After the dtwmrc file is updated on each workstation,
repeat

step 7 and step 8 to activate and test the new dtwmrc file on that

workstation.

This completes the installation and configuration of the Meet‑Me Instant

Meeting Notification Software on the HP workstations.

**Troubleshooting, where the log files are**

Log files at on the issuing office\'s AWIPS system

When the text_admin.tcl script is run on a workstation to create and

transmit the WSHNIMNAT product to other offices, the

/awips/fxa/awipsusr/text_admin.log file is created on the workstation
where

the text_admin.tcl script is run. A sample entry from the text_admin.log

contains the following information about which offices the WSHNIMNAT
product

was sent to:

**text_admin.tcl v1.2**

**19:17:51 GMT 12/05/2001**

**Product WSHNIMNAT sent to: FGF**

**Command Line /awips/fxa/bin/distributeProduct ‑s WSHNIMNAT ‑a FGF ‑c**

**AFOS_STORE_TEXTDB KNCFNIMNAT /var/tmp/temp_admin**

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑

When the text_admin.tcl script invokes the distributeProduct executable
to

transmit the WSHNIMNAT product, distributeProduct creates a log file in
the

daily log file directory on that workstation. The distributeProduct log

files on a workstation are stored in the

/data/logs/fxa/display/ws#‑xxx:0.0/yyyymmdd/ or the

/data/logs/fxa/display/ws#‑xxx:0.1/yyyymmdd/ directory where \# is the

workstation number and xxx is the site id. A sample entry from the

distributeProduct log file contains the following information about
which

offices the WSHNIMNAT product was sent to:

**LOG‑STATUS: Log file opened on host ws3‑abr at Wed Dec 5 19:17:51
2001**

**distributeProduct 188 1007579871.718194 19:17:51.718 EVENT: Product
request**

**(KNCFNIMNAT) was successfully**

**submitted to the MHS request server for distribution.**

**Message Attributes:**

**Request ID: ABR‑224289**

**To: FGF**

**Priority: 0**

**Type: Routine**

**Subject: WSHNIMNAT**

**Handling Action: 129**

**distributeProduct 188 1007579871.754688 19:17:51.754 EVENT:
ABR‑224289**

When the Message Handling Software transmits the WSHNIMNAT product from
the

issuing office directly to the receiving offices, the following entry is

added to the /awips/ops/logs/ds1‑xxx/x400sc.log file on the ds1 server

(where xxx is the AWIPS site identifier of the issuing office):

Wed Dec 5 19:17:51 2001 \<x400sc: 246\> MTA submit OK

ABR‑224289: Routine to=FGF, from=ABR, pri=0 code=129 enc=1 len=212

ABR‑224289: NXXX80 KNCF 051917 NIMNAT (/data/x400/msgtbl/ABR‑224289.msg)

**Log files at on the receiving office\'s AWIPS system**

When the Message Handling Software receives the WSHNIMNAT product from
the

issuing office, the following entry is added to the

/awips/ops/logs/ds1‑xxx/x400rd.log file on the ds1 server (where xxx is
the

AWIPS site identifier of the issuing office):

**Wed Dec 5 19:18:00 2001 \<x400rd:13655\> receive message OK**

**ABR‑224289: Routine to=FGF, from=ABR, pri=0 code=129 enc=1 len=212**

**dly=(0+9+0)s**

**ABR‑224289: NXXX80 KNCF 051917 NIMNAT**

**(/data/x400/rx400/output/x1800369.doc)**

The incoming WSHNIMNAT product by‑passes the text database decoders on
as2:

WarnDBDecoder and StdDBDecoder. Instead, the WSHNIMNAT

product is written directly to the Informix fxatext database using the

textdb ‑w command.

In the daily log file for the TextDB_Server ‑Write process running on
ds1,

the following type of entry should indicate that the Informix fxatext

database

trigger was invoked when the WSHNIMNAT product was stored in the fxatext

database:

**19:18:00.919 TextDB_Impl.C EVENT: Update Trigger kickoff SQLCODE: 0**

**19:18:00.981 TextDB_Server.C EVENT: NCF_STORE WSHNIMNAT Count:
5261654**

Elapsed: 0.168987