If you decide to compile your EWD applications for use with WebLink, the configuration is somewhat different to the other technologies, because EWD will create Caché routines instead of files.

To configure EWD for use with WebLink, you use the command-line API method:

   write $$configureWebLink^%zewdAPI(webserver,mode,alias,path)
where:

To quickly configure EWD for use with WebLink,start up a Caché terminal session and change to the namespace that you have configured for EWD. Then run, for example:

   USER zn "EWD"
   EWD> write $$configureWebLink^%zewdAPI("iis",,,"c:\InetPub\wwwroot")

    or...

   EWD> write $$configureWebLink^%zewdAPI("apache",,,"c:\Program Files\
        Apache Group\Apache2\htdocs")

Adjust the path according your requirements. If you used the IIS example above and compiled an application named Personnel, then EWD would create the ewdScripts.js and ewd.css files in the path:

   c:\InetPub\wwwroot\Personnel

If you need to manually adjust the WebLink configuration, it can be done by adjusting the contents of the global ^zewd, eg:

^zewd("config","RootURL","wl")= the url prefix string for your WebLink configuration (eg /scripts/mgwms32.dll)

You are now ready to use EWD with WebLink!

Note: If you need to re-install or re-configure WebLink, you may find our Quick Installation Guide useful.