VistApedia - User contributions [en]

EWD Components

2012-09-30T11:35:00Z

Kirt: in progress

EWD Components
The following is a functional description of the moving parts of EWD so the user/developer has a good idea of how the parts fit together and how they work or don't work. I will describe the variant which is Open Source and specifically the back end GTM and front end JavaScript and mainly custom tag sets invoking extJS Framework and Sencha Touch for touch-based smart phones and tablet devices. Other variants are available in the full MGateway products, but are ignored for simplicity here.

An EWD system consists of a server system accessed by browser clients.

The Server may run Apache or a Node-js Server (or both to be strictly correct). As such it must have a domain-name or IP address on the LAN or the Internet.

Usually an EWD-based system will operate securely using https:// protocol and therefore use SSH as a component of the server. See details of how it uses port 443 typically to encrypt messages transmitted between client browser and server over what my be the public Internet or a private (hospital) Intranet (LAN - local area network plus or minus wireless linkages. See [[EWD Network and SSH]].

An Apache web server can be a complex topic in itself because of the multitude of features and modes available in this amazing open source product. Once configured, however, it just works and need not worry the developer after a system is set up and configured. Getting there is managed in the [[dEWDrop]] Virtual Machine or by AstroVistA debian-type installer.

Instead of apache, a Node js Web Server may be used as a component of EWD.

M_Gateway is a component which runs on the server and maps the incoming URLs to GTM as special EWD references instead of other web-requests to the server. It is analogous to older CGI requests which were mapped in early web systems to be interpreted by the Apache to create html pages from databases with 'variable' data instead of being fixed web html pages. EWD references by the browser take the form:

https://192.168.197.129/vista/MyApp/MyPage.ewd

Where
https is the protocol used to invoke SSH secure transmission for the request to the EWD server.
192.168.1.150 is a typical LAN IP address of the EWD server (in lieu of a domain name).
vista/ is a specific string - a code to invoke the EWD system to process the rest of the URL.
See [[M_Gateway]].
MyApp/ represents an [[EWD-App/EWD Application]] - a set of EWD code pages working together, compiled by EWD.
MyPage.ewd has the specific extension .ewd and is a container page or Starting page of the EWD subsystem

The M_Gateway component is a low-level extension of the Apache server which triggers Run-time EWD.
The "vista" here in the URL triggers EWD-Runtime with the rest of the URL at the back end of Apache.

An [[EWD-App]] (or Application) is a set of [[EWD-page]]s stored in a single folder whose Folder-name determines the App Name used in the EWD URLs.

EWD Pages are simple text files which have the file-extension *.ewd are high level tag-based code which are Compiled by EWD into functioning Mumps Routines ([[MRoutines]]) which are executed by the runtime portions of EWD.

EWD Pages may include html code and include or invoke JavaScript programming. More commonly now, however, EWD tags refer to components of a FrameWork like extJS which provide complex GUI functionality for the EWD system and actual HTML is, in practice, not used much.

EWD does this via [[Custom-Tags]] which are logical extensions of EWD. Rob Tweed developed the set of custom-tags which invoke extJS and Sencha Touch, but any developer can similarly develop custom-tags for other Frameworks or special Functions such as DOJo or to link directly with VistA on the backend.

EWD pages are compiled in a series of transformations, first from custom tags to more detailed tags, then into html and JavaScript. These are compiled into MUMPS code which generally writes the html out to the browser via apache when invoked by the EWD-URL request. Actually, ewd is compiled to MUMPS and the MUMPS source code is compiled by GTM into Run-time GTM Object files. Object files are linked into the Linux process which runs the mumps program. "Compiled" thus has several meanings for the EWD developer.

The EWD Compiler is written in MUMPS and thus is invoked as a MUMPS Routine, for example by the M Command:
D compilePage^%zewdAPI("MyApp","MyPage")

The EWD Compiler uses the NameSpace ^%zewd*. GTM source MRoutines are files _zewd*.m and GTM Object MRoutines are _zewd*.o. Note the % within MUMPS MRoutine Names is transformed to Underscore in Linux (which does not allow the % character in its filenames). GTM source files, the MUMPS source code are plain text files with extension *.m and GTM compiles these to corresponding files *.o which are invoked at GTM Runtime into running Linux processes composed of a number of MRoutines which reference each other. The fileName is the MUMPS RoutineName.

These files are scattered among a number of Linux Folders/Directories and this configuration of folders may be a source of confusion for the EWD Developer and are discussed in [[EWD Folders and Files]].

EWD manages a number of otherwise sticky problems with web-based multiuser interactions between client browser and EWD server with the gtm mumps backend database. These include:
Creating a logical user-state in the server and browser in a stateless network at the TCP/IP level.
Encrypting internal page references to prevent illegitimate entrance by unauthorized clients.

EWD Components

2012-09-30T03:39:42Z

Kirt: Components Overview of EWD - new page

=== EWD Components
The following is a functional description of the moving parts of EWD so the user/developer has a good idea of how the parts fit together and how they work or don't work. I will describe the variant which is Open Source and specifically the back end GTM and front end JavaScript and mainly custom tag sets invoking extJS Framework and Sencha Touch for touch-based smart phones and tablet devices. Other variants are available in the full MGateway products, but are ignored for simplicity here.

An EWD system consists of a server system accessed by browser clients.

The Server may run Apache or a Node-js Server (or both to be strictly correct). As such it must have a domain-name or IP address on the LAN or the Internet.

Usually an EWD-based system will operate securely using https:// protocol and therefore use SSH as a component of the server. See details of how it uses port 443 typically to encrypt messages transmitted between client browser and server over what my be the public Internet or a private (hospital) Intranet (LAN - local area network plus or minus wireless linkages. See [[EWD Network and SSH]].

An Apache web server can be a complex topic in itself because of the multitude of features and modes available in this amazing open source product. Once configured, however, it just works and need not worry the developer after a system is set up and configured. Getting there is managed in the [[dEWDrop]] Virtual Machine or by AstroVistA debian-type installer.

EWD

2012-09-30T03:21:11Z

Kirt: Basis for EWD Section Enhancements

= Introduction =
EWD or Enterprise Web Developer is an Open Source Product on GT.M and Linux which is a complete system for developing Web-Based Systems which combine MUMPS in the background Database and Logical Structure with Browser-based Client GUI Interfaces. Systems developed with EWD separate the GUI Design of the User Interface and the Database and MUMPS programming logic of the system to provide the efficient development and modeling of complex data that has always characterized MUMPS systems, but now, finally with the GUI power of JavaScript and JavaScript Frameworks (open source too) of extJS and Sencha Touch and YUI on the front end.

www.MGateway.com is the main source for EWD and associated documentation and Many Thanks to Rob Tweed for this open source product and for support via the Google Group [[Enterprise Web Developer Community/https://groups.google.com/forum/?fromgroups=#!forum/enterprise-web-developer-community]]

Sam Habiel has detailed one installation process on this site: [[EWD Installation Guide]].

Ignatio Valdez has created a debian installer, AstroVistA, which installs WorldVista along with EWD, GTM and Apache.

David Wicksell et. al. have created [[dEWDrop]] and made it available for download as a VMWare (or VirtualBox) Virtual Machine with Ubuntu Linux, all of VistA, EWD, GTM and other things configured and hopefully ready to run for development and training in EWD and GTM and VistA itself. It may be downloaded from www.FourthWatchSoftware.com.

[[EWD Components]] is a page that details the major working parts of EWD.

[[EWD Training Examples]] is an area of VistaPedia with multiple small examples of functioning EWD code to learn and modify for development exercises.

[[EWD Error Messages]] is a set of pages with searchable error messages which help to unravel the source of errors in EWD which can be a bit obscure to the uninitiated.

EWD Install Instructions

2012-09-30T02:57:31Z

Kirt:

Welcome to my page on installing [[EWD]]. I am doing this on Ubuntu. If you do this on a Red Hat like system, you have to adapt the instructions.

== Prerequisites ==
* Latest Version of GT.M installed
* VISTA installed

=== Install Git and download the Git Repo of EWD ===
I make my own directory called src or svn or whatever and put all the source code in it.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sudo apt-get install git-core ; Get Git
git clone git://github.com/robtweed/EWD.git ; Get EWD
</pre>

== EWD Installation Using Apache ==
This will install EWD using Apache as the web facing gateway to EWD. To install it using Node, see below.
=== Install and Set-up mgwsi ===
MGWSI is the tcp listener on GT.M that listens for apache requests. Make a routine directory that will be part of the $gtmroutines add add that directory to your $gtmroutines. (Or you could just use a directory already in the existing gtmroutines.) Here's my GT.M env set-up script, for example. I am running in UTF-8 mode, so you will see extra lines that have to do with that.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
#/bin/bash
cd ~/pocn-moh
export gtm_dist=/opt/fis-gtm/V5.4-002A/utf8/
export gtmroutines="uo(routines svn/BMX ewdroutines) $gtm_dist"
export gtmgbldir=mumps.gld
export PATH=$PATH:$gtm_dist
export gtm_chset=utf-8
export gtm_icu_version=4.2
</pre>
Copy the ZMGWSI routines from EWD's m_apache directory to your routines folder.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
cp svn/EWD/m_apache/*.m ewdroutines/
</pre>
Verify that the routines are found by GT.M:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh$ mumps -dir

GTM>d ^%RD

Routine directory
Routine: %ZM*
%ZMGWSI %ZMGWSIS
Total of 2 routines.
</pre>
Run the program now to make sure it compiles properly.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh$ mumps -r INETD^%ZMGWSIS
%GTM-I-CTRLC, CTRL_C encountered

GTM>ZSHOW
CHILD3+5^%ZMGWSIS (Direct mode)
XINETD+2^%ZMGWSIS

GTM>H
</pre>
Then make a bash script to call it:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh$ cat mgwsi-rpcproc
#!/bin/bash
cd /home/sam/pocn-moh
source ./run_utf8
date>>rpc_log.log
$gtm_dist/mumps -run INETD^%ZMGWSIS 2>> rpc_log.log
exit 0

# Make it executable
sam@sam-desktop:~/pocn-moh$ chmod +x mgwsi-rpcproc

# Run it
sam@sam-desktop:~/pocn-moh$ ./mgwsi-rpcproc

GTM>zshow
CHILD3+5^%ZMGWSIS (Direct mode)
XINETD+2^%ZMGWSIS

GTM>h
</pre>
Now we put it as a xinetd service
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
# Create the following line in configuration file: /etc/services
mgwsi 7041/tcp # Service for MGWSI clients

# Create Xined script that calls mgwsi-rpcproc
sudo cat mgwsi_pocn-moh_7041
service mgwsi-pocn-moh-7041
{
disable = no
port = 7041
socket_type = stream
protocol = tcp
user = sam
server = /bin/bash
groups = yes
server_args = /home/sam/pocn-moh/mgwsi-rpcproc
type = UNLISTED
wait = no
}
</pre>
Now we test it by putting xinetd in debug mode and then telneting to the port.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:/etc/xinetd.d$ sudo xinetd -d &
[2] 10521
...
Service configuration: mgwsi-pocn-moh-7041
id = mgwsi-pocn-moh-7041
flags = IPv4
type = UNLISTED
socket_type = stream
Protocol (name,number) = (tcp,6)
port = 7041
wait = no
user = 1000
Groups = yes
PER_SOURCE = -1
Bind = All addresses.
Server = /bin/bash
Server argv = bash /home/sam/pocn-moh/mgwsi-rpcproc
Only from: All sites
No access: No blocked sites
No logging
...
11/5/23@10:41:33: DEBUG: 10521 {cnf_start_services} Started service: mgwsi-pocn-moh-7041
...
11/5/23@10:41:33: NOTICE: 10521 {main} xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
11/5/23@10:41:33: NOTICE: 10521 {main} Started working: 8 available services
11/5/23@10:41:33: DEBUG: 10521 {main_loop} active_services = 8
telnet localhost 7041
Trying ::1...
Trying 127.0.0.1...
11/5/23@10:41:52: DEBUG: 10521 {main_loop} select returned 1
Connected to localhost.
Escape character is '^]'.
11/5/23@10:41:52: DEBUG: 10521 {server_start} Starting service mgwsi-pocn-moh-7041
11/5/23@10:41:52: DEBUG: 10521 {main_loop} active_services = 8
11/5/23@10:41:52: DEBUG: 10523 {exec_server} duping 14
^]

telnet> quit
Connection closed.
sam@sam-desktop:/etc/xinetd.d$ 11/5/23@10:41:57: DEBUG: 10521 {main_loop} active_services = 8
11/5/23@10:41:57: DEBUG: 10521 {main_loop} select returned 1
11/5/23@10:41:57: DEBUG: 10521 {check_pipe} Got signal 17 (Child exited)
11/5/23@10:41:57: DEBUG: 10521 {child_exit} waitpid returned = 10523
11/5/23@10:41:57: DEBUG: 10521 {server_end} mgwsi-pocn-moh-7041 server 10523 exited
11/5/23@10:41:57: INFO: 10521 {conn_free} freeing connection
11/5/23@10:41:57: DEBUG: 10521 {child_exit} waitpid returned = -1
11/5/23@10:41:57: DEBUG: 10521 {main_loop} active_services = 8
</pre>
Once you are sure it works, foreground your xinetd process and kill it using Ctrl-C.

=== Setting up m_apache ===
First, make sure that m_apache is the right architecture for your machine. If not, you need to compile the m_apache.c file. The compilation instructions are from the source. Also, Mike Clayton's 64 bit installers for EWD provide the m_apache22 file in 64 bit format which you can extract from the .deb file.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh/svn/EWD/m_apache$ file m_apache22.so
m_apache22.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
</pre>
Copy to the lib folder of apache modules: in Ubuntu: /usr/lib/apache2/modules
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sudo cp m_apache22.so /usr/lib/apache2/modules/
</pre>
Configure your apache so that it will route all pages in a specific location to Mumps. Make sure to get your gld file correctly. I edited my /etc/apache2/sites-available/default to have these lines:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
LoadModule m_apache_module /usr/lib/apache2/modules/m_apache22.so
<Location /ewd>
SetEnv MGWSI_PORT 7041
SetEnv MGWSI_M_UCI /home/sam/pocn-moh/mumps.gld
SetEnv MGWSI_M_FUNCTION runPage^%zewdGTMRuntime
</Location>
</pre>
Restart apache and make sure there aren't any errors.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:/etc/apache2/sites-available$ sudo service apache2 restart
* Restarting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
... waiting .apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[ OK ]
</pre>
Test M apache. In a web browser, navigate to http://localhost/ewd/index.mgwsi. You should get an EWD Error Page. If you get an apache error message, something is wrong.

=== SELinux and Apache to MGWSI ===
If you do get an apache Service Unavailable message, it could be due to SELinux.

Review <tt>/var/log/audit/audit.log</tt>. See if there is a AVC type message like this:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
type=AVC msg=audit(1317316775.606:57870): avc: denied { name_connect } for pid=15027 comm="httpd" dest=7041 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
</pre>
If you see something like this, you need to tell SELinux the following:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
semanage port -a -t http_port_t -p tcp 7041
</pre>
=== Install EWD M Files ===
Copy the EWD Mumps files to a GT.M Mumps directory. They are all in the root of the repo.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh/svn$ cp EWD/*.m ../ewdroutines/
</pre>
=== Install Resources ===
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
You need to install a bunch of files under /var/www:
# Copy iwd from the root directory to /var/www/
sudo cp -r iwd /var/www/

# Copy the resources files from the ewdMgr/resourceFiles directory to /var/www/resources (which you need to make)
sudo mkdir -p /var/www/resources
sudo chmod 777 /var/www/resources/
sudo cp ewdMgr/resourceFiles/* /var/www/resources

# Get the YUI library and install it.
wget http://yui.zenfs.com/releases/yui2/yui_2.6.0r2.zip
sudo unzip yui_2.6.0r2.zip -d /var/www/
sudo chmod 777 /var/www/yui/
</pre>
=== Install EWD [[Application~|Application]]s ===
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
# Make a directory for [[application~|Application]]s
sam@sam-desktop:~/pocn-moh$ mkdir ewdapps

# Copy the ewdMgr and iwd to that directory
cp -r ewdMgr/ ../../ewdapps/
cp -r iWDApps/ ../../ewdapps/
</pre>
=== Configure EWD for the First Run ===
There are many bugs in this area, so make sure to read below so you know what you are in for before doing any of these steps.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
GTM>KILL ^zewd

GTM>D compileAll^%zewdAPI("ewdMgr")

Installing/Configuring Enterprise Web Developer (Build 790)

Note: hit Esc to go back at any point

[[Application~|Application]] Root Path (/usr/ewdapps): /home/sam/pocn-moh/ewdapps
Routine Path (/usr/local/gtm/ewd/): /home/sam/pocn-moh/ewdroutines/
Javascript and CSS File Output Path (/var/www/resources/): /var/www/resources/
Javascript and CSS File URL Path (/resources/): /resources/

Enterprise Web Developer (Build 790) is configured and ready for use
</pre>
==== EWD First Run Bugs ====
* _zewdDocumentation2.m contains invalid Unicode characters. I cleaned it up using iconv.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
iconv -fUTF8 -tUTF8 -c _zewdDocumentation2.m -o _zewdDocumentation2.m
</pre>
* EWD expects to be able to write to /var/www/resources. I put that in the instructions for that section.
* For some reason, EWD switches the routine path the first time it connects from the web. Why??? So you have to fix it manually. AND REMEMBER TO PUT A TRAILING SLASH. THAT ONE CAUGHT ME FOR A WHILE!!!
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
S ^zewd("config","routinePath","gtm")="/home/sam/pocn-moh/ewdroutines/"
</pre>
* Issue of compiling [[application~|Application]]s with subdirectories. Where is it supposed to output? Update: Rob says ignore for now. Here's an example:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
GTM>d compileAll^%zewdAPI("iWDApps")
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/iWDExample': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/completed.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/demologin.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/details.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/newUser.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/selectApp.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/selectLocations.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/selectUser.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab1.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab2.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab3.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab4.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/userList.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/iWDMgr': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/about.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/[[application~|Application]]s.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/configuration.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/incomplete.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/login.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/mainMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/pageMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/pages.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/sessionContent.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/sessionDetails.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/sessions.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/imdb': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/attributeMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/deleteAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/deleteDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/deleteItem.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/domainMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/editAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/itemMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/login.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/newAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/newDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/newItem.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/notInitialised.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveAttributeValue.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveItem.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/iwdmdb': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDXArtist.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDXArtistList.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDXTitle.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/about.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/mainMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/selectTrack.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/mdb': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/addUser.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/addUserResponse.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/applianceAbout.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/displayDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdDocs.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/getDomains.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/initialise.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/initialiseInfo.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/login.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/loginForm.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mainmenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mdbMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mdbWelcome.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mgwsiMgr.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/security.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/showUserInfo.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/showUsers.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/timezone.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/timezoneResponse.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/userDetails.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfig.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigApache.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigArchitecture.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigExit.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigGTM.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigIP.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigKB.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigLinuxGTM.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigMGWSI.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigUsernames.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/viewer.ewd
</pre>
* I wasn't able to get YUI tags to work. The JS to load them properly in the webpage is there, but is not evaluated. I will work on that later.
=== Setting Up the Special MGWSI Functions Location ===
You need this for several cryptographic functions to work:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
<Location "/mgwsi/sys/">
# This is a reserved location used for the m_apache systems facilities invoked through:
# /mgwsi/sys/system_functions.mgwsi
Order deny,allow
Allow from all
</Location>
</pre>
=== Setting Up SSL With EWD ===
There is nothing to it. Follow the instructions here: http://wiki.centos.org/HowTos/Https then make your config file as follows (Note that I did this on CentOS):
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
LoadModule m_apache_module modules/m_apache22.so
ServerName example.com

NameVirtualHost *:443
<VirtualHost *:443>
SSLEngine on
SSLCertificateFile /etc/pki/tls/certs/ca.crt
SSLCertificateKeyFile /etc/pki/tls/private/ca.key
<Location /ewd>
SetEnv MGWSI_PORT 7041
SetEnv MGWSI_M_UCI /opt/worldvista/EHR/globals/mumps.gld
SetEnv MGWSI_M_FUNCTION runPage^%zewdGTMRuntime
</Location>
<Location "/mgwsi/sys/">
# This is a reserved location used for the m_apache systems facilities invoked through:
# /mgwsi/sys/system_functions.mgwsi
Order deny,allow
Allow from all
</Location>

</VirtualHost>

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</pre>

=== Setting up the SSL Proxy for EWD ===
There is a special case where you are trying to access external ssl connections from within EWD using the http methods in %zewdGTM. If you do so, you will need to configure a proxy on port 89 that forwards your connections from EWD to the ssl port. This is done using Apache's mod_proxy and mod_ssl. My thanks to David W and Larry L for the instructions on how to set this up and prevent it from being abused.

These instructions are for Debian systems.

First, enable the modules ssl and proxy.
<pre>
sudo a2enmod proxy
sudo a2enmod proxy_connect
sudo a2enmod proxy_ftp
sudo a2enmod proxy_http
sudo a2enmod ssl
</pre>

Set-up this config file for apache:
<pre>
Listen 89
SSLProxyEngine on
ProxyRequests on

<Proxy *>
Order deny,allow
Deny from all
Allow from localhost
</Proxy>

SSLProxyEngine on
SSLProxyVerify none

ProxyVia on
</pre>

=== Miscellaneous Stuff ===
==== Compiling m_apache ====
I am troubleshooting a bug in m_apache right now: I needed to re-compile it because I think I may have an older version. If the bug shows up again, well, I can change the source. I did this on CentOS 6; your luck may differ.

You need m_apache.c from the EWD repo, which you downloaded in step 1.

<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
yum install gcc
yum install httpd-devel
yum install openssl-devel
apxs -i -a -I/usr/include/openssl/ -n m_apache22 -o m_apache22.so -c m_apache.c
</pre>

I also figured out how to do it with plain gcc using the tips apxs gave me.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
> gcc -fPIC -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wformat-security -fno-strict-aliasing -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -pthread -I/usr/include/httpd -I/usr/include/apr-1 -I/usr/include/apr-1 -I/usr/include/openssl/ -c -o m_apache.obj m_apache.c
> gcc -shared -rdynamic -o m_apache22.so m_apache.obj
</pre>
== EWD Installation using Node.js ==
[http://nodejs.org Node.js] is a an up and coming technology that allows you to build scalable network programs. EWD works with node.js. For more information on the advantages of using node.js with EWD, look [https://github.com/robtweed/ewdGateway here].

Note that I am doing this on a different machine than above with vastly different directories. The ideas are the same though.

=== Install Node.js & NPM ===
I install node per the Node.js wiki in my home directory and then add it to my path. You may have other ideas. Note that you have to have gcc, g++ and GNU Make installed.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
# Get Node from Github
git clone --depth 1 git://github.com/joyent/node.git
sudo apt-get install libssl-dev
# Install Node
cd node # cd to the git directory you downloaded above
export JOBS=2 # optional, sets number of parallel commands.
mkdir ~/local
./configure --prefix=$HOME/local/node
make
make install
export PATH=$HOME/local/node/bin:$PATH (& put in .bashrc)

# Install NPM
sudo apt-get install curl
curl http://npmjs.org/install.sh | sh
</pre>
=== Install ewdGateway.js & Socket.io ===
Install using npm.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
npm install ewdGateway
npm install socket.io
</pre>
=== Prepare GT.M directories ===
I will assume that you already have VISTA installed on GT.M. For EWD, you need to drop the EWD routines in a directory that contains the M routines for VISTA, and you need to drop the [[application~|Application]]s in another directory.

=== Copy EWD Routines into the Routines directory ===
Copy the EWD Mumps files to a GT.M Mumps directory. They are all in the root of the repo.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~$ cd EWD
sakura@medusa:~/EWD$ cp *.m /opt/worldvista/EHR/routines/
</pre>
=== Copy Resources ===
Note that for convenience I chmodded /var/www to 777 instead of being root.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/EWD$ cp -r iwd/ /var/www/
sakura@medusa:~/EWD$ mkdir -p /var/www/resources
sakura@medusa:~/EWD$ chmod 777 /var/www/resources
sakura@medusa:~/EWD$ cp ewdMgr/resourceFiles/* /var/www/resources/
</pre>
=== Copy [[Application~|Application]]s ===
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/EWD$ cp -r ewdMgr/ /opt/worldvista/EHR/plugins/web/ewdapps/
sakura@medusa:~/EWD$ cp -r iWDApps/ /opt/worldvista/EHR/plugins/web/ewdapps/
</pre>
=== First Time EWD Configuration ===
Let me explain a few things here.
* I kill ^zewd first because my instance already has that existing and it's incorrect.
* EWD tries to install files in /var/www/resources using sudo. Remember that we already made /var/www/resources modded to 777, so we will be able to write to it. Just hit enter on the sudo prompts and the files will be written anyways.
* Ignore the mkdir Errors. These happen because there is a sub-directory under ewdMgr, and EWD does not support subdirectories in an [[application~|Application]].
* Don't forget the trailing slashes on the directories.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/EWD$ gtm

medusa>K ^zewd

medusa>d compileAll^%zewdAPI("ewdMgr")

Installing/Configuring Enterprise Web Developer (Build 887)

Note: hit Esc to go back at any point

[[Application~|Application]] Root Path (/usr/ewdapps): /opt/worldvista/EHR/plugins/web/ewdapps/
Routine Path (/usr/local/gtm/ewd/): /opt/worldvista/EHR/plugins/web/r/
Javascript and CSS File Output Path (/var/www/resources/): /var/www/resources/
Javascript and CSS File URL Path (/resources/): /resources/

Enterprise Web Developer (Build 887) is configured and ready for use

[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/about.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/applianceAbout.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compilePage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compilePageResults.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compiler.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compilerResults.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/config.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/configDaemon.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/configMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/configSettingsSaved.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/customTags.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/dataTypes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/deleteCustomTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/deleteDataType.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docParam.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docParams.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docPurpose.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docRetVal.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docTypCall.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/documentation.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/domDocumentation.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/domDocumentationDetail.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/editCustomTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/editDataType.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/errors.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdAjaxError.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdAjaxErrorRedirect.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdDocs.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdErrorRedirect.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdMgr.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/gtmHome.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/gtmMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/gtmSecurity.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/index.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/initialPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/initialSecurity.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/invalidAccess.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/invalidAccessMessage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/invalidvaaccess.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/listError.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/listPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/listSession.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/login.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/loginForm.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/logout.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/mainMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/mapacheConfig.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/mgwsiMgr.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/newCustomTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/newDataType.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/relink.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/reloadCustomTags.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/reloadDataTypes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/reloadSecurity.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/security.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/sessions.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/showCustomTagNotes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/showDataTypeNotes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/user.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfig.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigApache.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigArchitecture.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigEWD.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigExit.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigGTM.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigIP.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigKB.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigLinuxGTM.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigMGWSI.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigUsernames.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaInitialPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xref.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageFromPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageFromScript.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageFromTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageToPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageToScript.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageToTag.ewd
mkdir: cannot create directory `/ewdMgr': Permission denied
mkdir: cannot create directory `/ewdMgr/resourceFiles': No such file or directory

medusa>

</pre>
=== Last thing, launch ewdGateway ===
First, you need to make a tiny node js file. I called it launchewd.js.

<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
var ewd = require('ewdGateway');
var params = {database:'gtm', httpPort: 8080, poolSize: 3, startWebserver: true};
ewd.start(params, function(gateway) {
console.log("version = " + gateway.version());
});
</pre>

Now, go ahead and launch it. The mumps executable must be in the PATH otherwise the execution will seem successful but not really.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/node$ PATH=$gtm_dist:$PATH node launchewd.js
</pre>

Here's the output:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/node$ PATH=$gtm_dist:$PATH node launchewd.js
info - socket.io started
********************************************
*** EWD Gateway for GT.M Build 18 (14 September 2011) ***
********************************************
3 connections established to GT.M
Web server started successfully on port 8080
Trace mode is on
version = ewdGateway build 18, 14 September 2011
/ewd/so/index.ewd
incoming request for app: so; page: index
added to Queue (http): %7B%7D; queue length = 1; requestNo = 1; after 13.655 sec
processing queue: 1; queue length 1; after 13.656 seconds
Request sent to Cache using connection = 0
from GT.M on connection 0:
HTTP/1.1 200 OK

dump: :72:84:84:80:47:49:46:49:32:50:48:48:32:79:75:13:10

from GT.M on connection 0:
Content-type:

dump: :67:111:110:116:101:110:116:45:116:121:112:101:58:32

from GT.M on connection 0:
text/html

dump: :116:101:120:116:47:104:116:109:108

from GT.M on connection 0:

dump: :13:10

from GT.M on connection 0:

dump: :13:10

from GT.M on connection 0:
<html>
...
etc
...
Connection 0 reset and waiting..
Connection utilitisation:
0: 1
1: 0
2: 0
Max queue length: 1
</pre>

EWD Install Instructions

2012-09-30T02:57:02Z

Kirt:

Welcome to my page on installing [EWD]. I am doing this on Ubuntu. If you do this on a Red Hat like system, you have to adapt the instructions.

== Prerequisites ==
* Latest Version of GT.M installed
* VISTA installed

=== Install Git and download the Git Repo of EWD ===
I make my own directory called src or svn or whatever and put all the source code in it.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sudo apt-get install git-core ; Get Git
git clone git://github.com/robtweed/EWD.git ; Get EWD
</pre>

== EWD Installation Using Apache ==
This will install EWD using Apache as the web facing gateway to EWD. To install it using Node, see below.
=== Install and Set-up mgwsi ===
MGWSI is the tcp listener on GT.M that listens for apache requests. Make a routine directory that will be part of the $gtmroutines add add that directory to your $gtmroutines. (Or you could just use a directory already in the existing gtmroutines.) Here's my GT.M env set-up script, for example. I am running in UTF-8 mode, so you will see extra lines that have to do with that.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
#/bin/bash
cd ~/pocn-moh
export gtm_dist=/opt/fis-gtm/V5.4-002A/utf8/
export gtmroutines="uo(routines svn/BMX ewdroutines) $gtm_dist"
export gtmgbldir=mumps.gld
export PATH=$PATH:$gtm_dist
export gtm_chset=utf-8
export gtm_icu_version=4.2
</pre>
Copy the ZMGWSI routines from EWD's m_apache directory to your routines folder.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
cp svn/EWD/m_apache/*.m ewdroutines/
</pre>
Verify that the routines are found by GT.M:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh$ mumps -dir

GTM>d ^%RD

Routine directory
Routine: %ZM*
%ZMGWSI %ZMGWSIS
Total of 2 routines.
</pre>
Run the program now to make sure it compiles properly.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh$ mumps -r INETD^%ZMGWSIS
%GTM-I-CTRLC, CTRL_C encountered

GTM>ZSHOW
CHILD3+5^%ZMGWSIS (Direct mode)
XINETD+2^%ZMGWSIS

GTM>H
</pre>
Then make a bash script to call it:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh$ cat mgwsi-rpcproc
#!/bin/bash
cd /home/sam/pocn-moh
source ./run_utf8
date>>rpc_log.log
$gtm_dist/mumps -run INETD^%ZMGWSIS 2>> rpc_log.log
exit 0

# Make it executable
sam@sam-desktop:~/pocn-moh$ chmod +x mgwsi-rpcproc

# Run it
sam@sam-desktop:~/pocn-moh$ ./mgwsi-rpcproc

GTM>zshow
CHILD3+5^%ZMGWSIS (Direct mode)
XINETD+2^%ZMGWSIS

GTM>h
</pre>
Now we put it as a xinetd service
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
# Create the following line in configuration file: /etc/services
mgwsi 7041/tcp # Service for MGWSI clients

# Create Xined script that calls mgwsi-rpcproc
sudo cat mgwsi_pocn-moh_7041
service mgwsi-pocn-moh-7041
{
disable = no
port = 7041
socket_type = stream
protocol = tcp
user = sam
server = /bin/bash
groups = yes
server_args = /home/sam/pocn-moh/mgwsi-rpcproc
type = UNLISTED
wait = no
}
</pre>
Now we test it by putting xinetd in debug mode and then telneting to the port.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:/etc/xinetd.d$ sudo xinetd -d &
[2] 10521
...
Service configuration: mgwsi-pocn-moh-7041
id = mgwsi-pocn-moh-7041
flags = IPv4
type = UNLISTED
socket_type = stream
Protocol (name,number) = (tcp,6)
port = 7041
wait = no
user = 1000
Groups = yes
PER_SOURCE = -1
Bind = All addresses.
Server = /bin/bash
Server argv = bash /home/sam/pocn-moh/mgwsi-rpcproc
Only from: All sites
No access: No blocked sites
No logging
...
11/5/23@10:41:33: DEBUG: 10521 {cnf_start_services} Started service: mgwsi-pocn-moh-7041
...
11/5/23@10:41:33: NOTICE: 10521 {main} xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
11/5/23@10:41:33: NOTICE: 10521 {main} Started working: 8 available services
11/5/23@10:41:33: DEBUG: 10521 {main_loop} active_services = 8
telnet localhost 7041
Trying ::1...
Trying 127.0.0.1...
11/5/23@10:41:52: DEBUG: 10521 {main_loop} select returned 1
Connected to localhost.
Escape character is '^]'.
11/5/23@10:41:52: DEBUG: 10521 {server_start} Starting service mgwsi-pocn-moh-7041
11/5/23@10:41:52: DEBUG: 10521 {main_loop} active_services = 8
11/5/23@10:41:52: DEBUG: 10523 {exec_server} duping 14
^]

telnet> quit
Connection closed.
sam@sam-desktop:/etc/xinetd.d$ 11/5/23@10:41:57: DEBUG: 10521 {main_loop} active_services = 8
11/5/23@10:41:57: DEBUG: 10521 {main_loop} select returned 1
11/5/23@10:41:57: DEBUG: 10521 {check_pipe} Got signal 17 (Child exited)
11/5/23@10:41:57: DEBUG: 10521 {child_exit} waitpid returned = 10523
11/5/23@10:41:57: DEBUG: 10521 {server_end} mgwsi-pocn-moh-7041 server 10523 exited
11/5/23@10:41:57: INFO: 10521 {conn_free} freeing connection
11/5/23@10:41:57: DEBUG: 10521 {child_exit} waitpid returned = -1
11/5/23@10:41:57: DEBUG: 10521 {main_loop} active_services = 8
</pre>
Once you are sure it works, foreground your xinetd process and kill it using Ctrl-C.

=== Setting up m_apache ===
First, make sure that m_apache is the right architecture for your machine. If not, you need to compile the m_apache.c file. The compilation instructions are from the source. Also, Mike Clayton's 64 bit installers for EWD provide the m_apache22 file in 64 bit format which you can extract from the .deb file.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh/svn/EWD/m_apache$ file m_apache22.so
m_apache22.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
</pre>
Copy to the lib folder of apache modules: in Ubuntu: /usr/lib/apache2/modules
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sudo cp m_apache22.so /usr/lib/apache2/modules/
</pre>
Configure your apache so that it will route all pages in a specific location to Mumps. Make sure to get your gld file correctly. I edited my /etc/apache2/sites-available/default to have these lines:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
LoadModule m_apache_module /usr/lib/apache2/modules/m_apache22.so
<Location /ewd>
SetEnv MGWSI_PORT 7041
SetEnv MGWSI_M_UCI /home/sam/pocn-moh/mumps.gld
SetEnv MGWSI_M_FUNCTION runPage^%zewdGTMRuntime
</Location>
</pre>
Restart apache and make sure there aren't any errors.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:/etc/apache2/sites-available$ sudo service apache2 restart
* Restarting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
... waiting .apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[ OK ]
</pre>
Test M apache. In a web browser, navigate to http://localhost/ewd/index.mgwsi. You should get an EWD Error Page. If you get an apache error message, something is wrong.

=== SELinux and Apache to MGWSI ===
If you do get an apache Service Unavailable message, it could be due to SELinux.

Review <tt>/var/log/audit/audit.log</tt>. See if there is a AVC type message like this:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
type=AVC msg=audit(1317316775.606:57870): avc: denied { name_connect } for pid=15027 comm="httpd" dest=7041 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
</pre>
If you see something like this, you need to tell SELinux the following:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
semanage port -a -t http_port_t -p tcp 7041
</pre>
=== Install EWD M Files ===
Copy the EWD Mumps files to a GT.M Mumps directory. They are all in the root of the repo.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sam@sam-desktop:~/pocn-moh/svn$ cp EWD/*.m ../ewdroutines/
</pre>
=== Install Resources ===
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
You need to install a bunch of files under /var/www:
# Copy iwd from the root directory to /var/www/
sudo cp -r iwd /var/www/

# Copy the resources files from the ewdMgr/resourceFiles directory to /var/www/resources (which you need to make)
sudo mkdir -p /var/www/resources
sudo chmod 777 /var/www/resources/
sudo cp ewdMgr/resourceFiles/* /var/www/resources

# Get the YUI library and install it.
wget http://yui.zenfs.com/releases/yui2/yui_2.6.0r2.zip
sudo unzip yui_2.6.0r2.zip -d /var/www/
sudo chmod 777 /var/www/yui/
</pre>
=== Install EWD [[Application~|Application]]s ===
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
# Make a directory for [[application~|Application]]s
sam@sam-desktop:~/pocn-moh$ mkdir ewdapps

# Copy the ewdMgr and iwd to that directory
cp -r ewdMgr/ ../../ewdapps/
cp -r iWDApps/ ../../ewdapps/
</pre>
=== Configure EWD for the First Run ===
There are many bugs in this area, so make sure to read below so you know what you are in for before doing any of these steps.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
GTM>KILL ^zewd

GTM>D compileAll^%zewdAPI("ewdMgr")

Installing/Configuring Enterprise Web Developer (Build 790)

Note: hit Esc to go back at any point

[[Application~|Application]] Root Path (/usr/ewdapps): /home/sam/pocn-moh/ewdapps
Routine Path (/usr/local/gtm/ewd/): /home/sam/pocn-moh/ewdroutines/
Javascript and CSS File Output Path (/var/www/resources/): /var/www/resources/
Javascript and CSS File URL Path (/resources/): /resources/

Enterprise Web Developer (Build 790) is configured and ready for use
</pre>
==== EWD First Run Bugs ====
* _zewdDocumentation2.m contains invalid Unicode characters. I cleaned it up using iconv.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
iconv -fUTF8 -tUTF8 -c _zewdDocumentation2.m -o _zewdDocumentation2.m
</pre>
* EWD expects to be able to write to /var/www/resources. I put that in the instructions for that section.
* For some reason, EWD switches the routine path the first time it connects from the web. Why??? So you have to fix it manually. AND REMEMBER TO PUT A TRAILING SLASH. THAT ONE CAUGHT ME FOR A WHILE!!!
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
S ^zewd("config","routinePath","gtm")="/home/sam/pocn-moh/ewdroutines/"
</pre>
* Issue of compiling [[application~|Application]]s with subdirectories. Where is it supposed to output? Update: Rob says ignore for now. Here's an example:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
GTM>d compileAll^%zewdAPI("iWDApps")
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/iWDExample': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/completed.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/demologin.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/details.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/newUser.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/selectApp.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/selectLocations.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/selectUser.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab1.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab2.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab3.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/tab4.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDExample/userList.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/iWDMgr': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/about.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/[[application~|Application]]s.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/configuration.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/incomplete.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/login.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/mainMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/pageMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/pages.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/sessionContent.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/sessionDetails.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iWDMgr/sessions.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/imdb': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/attributeMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/deleteAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/deleteDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/deleteItem.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/domainMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/editAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/itemMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/login.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/newAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/newDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/newItem.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/notInitialised.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveAttribute.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveAttributeValue.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/imdb/saveItem.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/iwdmdb': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDXArtist.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDXArtistList.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/CDXTitle.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/about.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/mainMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/iwdmdb/selectTrack.ewd
mkdir: cannot create directory `/iWDApps': Permission denied
mkdir: cannot create directory `/iWDApps/mdb': No such file or directory
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/addUser.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/addUserResponse.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/applianceAbout.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/displayDomain.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdAjaxError.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdAjaxErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdDocs.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/ewdErrorRedirect.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/getDomains.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/index.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/initialise.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/initialiseInfo.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/login.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/loginForm.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mainmenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mdbMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mdbWelcome.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/mgwsiMgr.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/security.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/showUserInfo.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/showUsers.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/timezone.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/timezoneResponse.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/userDetails.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfig.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigApache.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigArchitecture.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigExit.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigGTM.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigIP.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigKB.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigLinuxGTM.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigMGWSI.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigMenu.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/vaConfigUsernames.ewd
/home/sam/pocn-moh/ewdapps/iWDApps/mdb/viewer.ewd
</pre>
* I wasn't able to get YUI tags to work. The JS to load them properly in the webpage is there, but is not evaluated. I will work on that later.
=== Setting Up the Special MGWSI Functions Location ===
You need this for several cryptographic functions to work:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
<Location "/mgwsi/sys/">
# This is a reserved location used for the m_apache systems facilities invoked through:
# /mgwsi/sys/system_functions.mgwsi
Order deny,allow
Allow from all
</Location>
</pre>
=== Setting Up SSL With EWD ===
There is nothing to it. Follow the instructions here: http://wiki.centos.org/HowTos/Https then make your config file as follows (Note that I did this on CentOS):
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
LoadModule m_apache_module modules/m_apache22.so
ServerName example.com

NameVirtualHost *:443
<VirtualHost *:443>
SSLEngine on
SSLCertificateFile /etc/pki/tls/certs/ca.crt
SSLCertificateKeyFile /etc/pki/tls/private/ca.key
<Location /ewd>
SetEnv MGWSI_PORT 7041
SetEnv MGWSI_M_UCI /opt/worldvista/EHR/globals/mumps.gld
SetEnv MGWSI_M_FUNCTION runPage^%zewdGTMRuntime
</Location>
<Location "/mgwsi/sys/">
# This is a reserved location used for the m_apache systems facilities invoked through:
# /mgwsi/sys/system_functions.mgwsi
Order deny,allow
Allow from all
</Location>

</VirtualHost>

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</pre>

=== Setting up the SSL Proxy for EWD ===
There is a special case where you are trying to access external ssl connections from within EWD using the http methods in %zewdGTM. If you do so, you will need to configure a proxy on port 89 that forwards your connections from EWD to the ssl port. This is done using Apache's mod_proxy and mod_ssl. My thanks to David W and Larry L for the instructions on how to set this up and prevent it from being abused.

These instructions are for Debian systems.

First, enable the modules ssl and proxy.
<pre>
sudo a2enmod proxy
sudo a2enmod proxy_connect
sudo a2enmod proxy_ftp
sudo a2enmod proxy_http
sudo a2enmod ssl
</pre>

Set-up this config file for apache:
<pre>
Listen 89
SSLProxyEngine on
ProxyRequests on

<Proxy *>
Order deny,allow
Deny from all
Allow from localhost
</Proxy>

SSLProxyEngine on
SSLProxyVerify none

ProxyVia on
</pre>

=== Miscellaneous Stuff ===
==== Compiling m_apache ====
I am troubleshooting a bug in m_apache right now: I needed to re-compile it because I think I may have an older version. If the bug shows up again, well, I can change the source. I did this on CentOS 6; your luck may differ.

You need m_apache.c from the EWD repo, which you downloaded in step 1.

<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
yum install gcc
yum install httpd-devel
yum install openssl-devel
apxs -i -a -I/usr/include/openssl/ -n m_apache22 -o m_apache22.so -c m_apache.c
</pre>

I also figured out how to do it with plain gcc using the tips apxs gave me.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
> gcc -fPIC -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wformat-security -fno-strict-aliasing -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -pthread -I/usr/include/httpd -I/usr/include/apr-1 -I/usr/include/apr-1 -I/usr/include/openssl/ -c -o m_apache.obj m_apache.c
> gcc -shared -rdynamic -o m_apache22.so m_apache.obj
</pre>
== EWD Installation using Node.js ==
[http://nodejs.org Node.js] is a an up and coming technology that allows you to build scalable network programs. EWD works with node.js. For more information on the advantages of using node.js with EWD, look [https://github.com/robtweed/ewdGateway here].

Note that I am doing this on a different machine than above with vastly different directories. The ideas are the same though.

=== Install Node.js & NPM ===
I install node per the Node.js wiki in my home directory and then add it to my path. You may have other ideas. Note that you have to have gcc, g++ and GNU Make installed.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
# Get Node from Github
git clone --depth 1 git://github.com/joyent/node.git
sudo apt-get install libssl-dev
# Install Node
cd node # cd to the git directory you downloaded above
export JOBS=2 # optional, sets number of parallel commands.
mkdir ~/local
./configure --prefix=$HOME/local/node
make
make install
export PATH=$HOME/local/node/bin:$PATH (& put in .bashrc)

# Install NPM
sudo apt-get install curl
curl http://npmjs.org/install.sh | sh
</pre>
=== Install ewdGateway.js & Socket.io ===
Install using npm.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
npm install ewdGateway
npm install socket.io
</pre>
=== Prepare GT.M directories ===
I will assume that you already have VISTA installed on GT.M. For EWD, you need to drop the EWD routines in a directory that contains the M routines for VISTA, and you need to drop the [[application~|Application]]s in another directory.

=== Copy EWD Routines into the Routines directory ===
Copy the EWD Mumps files to a GT.M Mumps directory. They are all in the root of the repo.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~$ cd EWD
sakura@medusa:~/EWD$ cp *.m /opt/worldvista/EHR/routines/
</pre>
=== Copy Resources ===
Note that for convenience I chmodded /var/www to 777 instead of being root.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/EWD$ cp -r iwd/ /var/www/
sakura@medusa:~/EWD$ mkdir -p /var/www/resources
sakura@medusa:~/EWD$ chmod 777 /var/www/resources
sakura@medusa:~/EWD$ cp ewdMgr/resourceFiles/* /var/www/resources/
</pre>
=== Copy [[Application~|Application]]s ===
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/EWD$ cp -r ewdMgr/ /opt/worldvista/EHR/plugins/web/ewdapps/
sakura@medusa:~/EWD$ cp -r iWDApps/ /opt/worldvista/EHR/plugins/web/ewdapps/
</pre>
=== First Time EWD Configuration ===
Let me explain a few things here.
* I kill ^zewd first because my instance already has that existing and it's incorrect.
* EWD tries to install files in /var/www/resources using sudo. Remember that we already made /var/www/resources modded to 777, so we will be able to write to it. Just hit enter on the sudo prompts and the files will be written anyways.
* Ignore the mkdir Errors. These happen because there is a sub-directory under ewdMgr, and EWD does not support subdirectories in an [[application~|Application]].
* Don't forget the trailing slashes on the directories.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/EWD$ gtm

medusa>K ^zewd

medusa>d compileAll^%zewdAPI("ewdMgr")

Installing/Configuring Enterprise Web Developer (Build 887)

Note: hit Esc to go back at any point

[[Application~|Application]] Root Path (/usr/ewdapps): /opt/worldvista/EHR/plugins/web/ewdapps/
Routine Path (/usr/local/gtm/ewd/): /opt/worldvista/EHR/plugins/web/r/
Javascript and CSS File Output Path (/var/www/resources/): /var/www/resources/
Javascript and CSS File URL Path (/resources/): /resources/

Enterprise Web Developer (Build 887) is configured and ready for use

[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
[sudo] password for sakura:
Sorry, try again.
sudo: 3 incorrect password attempts
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/about.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/applianceAbout.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compilePage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compilePageResults.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compiler.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/compilerResults.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/config.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/configDaemon.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/configMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/configSettingsSaved.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/customTags.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/dataTypes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/deleteCustomTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/deleteDataType.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docParam.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docParams.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docPurpose.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docRetVal.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/docTypCall.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/documentation.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/domDocumentation.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/domDocumentationDetail.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/editCustomTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/editDataType.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/errors.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdAjaxError.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdAjaxErrorRedirect.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdDocs.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdErrorRedirect.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/ewdMgr.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/gtmHome.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/gtmMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/gtmSecurity.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/index.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/initialPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/initialSecurity.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/invalidAccess.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/invalidAccessMessage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/invalidvaaccess.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/listError.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/listPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/listSession.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/login.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/loginForm.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/logout.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/mainMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/mapacheConfig.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/mgwsiMgr.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/newCustomTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/newDataType.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/relink.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/reloadCustomTags.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/reloadDataTypes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/reloadSecurity.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/security.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/sessions.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/showCustomTagNotes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/showDataTypeNotes.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/user.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfig.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigApache.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigArchitecture.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigEWD.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigExit.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigGTM.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigIP.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigKB.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigLinuxGTM.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigMGWSI.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigMenu.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaConfigUsernames.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/vaInitialPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xref.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageFromPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageFromScript.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageFromTag.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageToPage.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageToScript.ewd
/opt/worldvista/EHR/plugins/web/ewdapps/ewdMgr/xrefPageToTag.ewd
mkdir: cannot create directory `/ewdMgr': Permission denied
mkdir: cannot create directory `/ewdMgr/resourceFiles': No such file or directory

medusa>

</pre>
=== Last thing, launch ewdGateway ===
First, you need to make a tiny node js file. I called it launchewd.js.

<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
var ewd = require('ewdGateway');
var params = {database:'gtm', httpPort: 8080, poolSize: 3, startWebserver: true};
ewd.start(params, function(gateway) {
console.log("version = " + gateway.version());
});
</pre>

Now, go ahead and launch it. The mumps executable must be in the PATH otherwise the execution will seem successful but not really.
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/node$ PATH=$gtm_dist:$PATH node launchewd.js
</pre>

Here's the output:
<pre style="padding:1em;border:1px dashed #2f6fab;color:black;background-color:#f9f9f9;line-height:1.1em">
sakura@medusa:~/node$ PATH=$gtm_dist:$PATH node launchewd.js
info - socket.io started
********************************************
*** EWD Gateway for GT.M Build 18 (14 September 2011) ***
********************************************
3 connections established to GT.M
Web server started successfully on port 8080
Trace mode is on
version = ewdGateway build 18, 14 September 2011
/ewd/so/index.ewd
incoming request for app: so; page: index
added to Queue (http): %7B%7D; queue length = 1; requestNo = 1; after 13.655 sec
processing queue: 1; queue length 1; after 13.656 seconds
Request sent to Cache using connection = 0
from GT.M on connection 0:
HTTP/1.1 200 OK

dump: :72:84:84:80:47:49:46:49:32:50:48:48:32:79:75:13:10

from GT.M on connection 0:
Content-type:

dump: :67:111:110:116:101:110:116:45:116:121:112:101:58:32

from GT.M on connection 0:
text/html

dump: :116:101:120:116:47:104:116:109:108

from GT.M on connection 0:

dump: :13:10

from GT.M on connection 0:

dump: :13:10

from GT.M on connection 0:
<html>
...
etc
...
Connection 0 reset and waiting..
Connection utilitisation:
0: 1
1: 0
2: 0
Max queue length: 1
</pre>

User:Kirt

2012-09-30T02:38:32Z

Kirt: Created page with "See [KW]."

See [KW].