ClientServer README.TXT Contents: 1. Client Folder 2. Server Folder 1. Client Folder ================ 1.1. Com Folder --------------- Remote Studio, or RStudio, is a collection of classes which enable developers to communicate with Omnis Studio remotely. The COM version is for use on the Windows platform where COM is supported (C#, Visual Basic, C++ etc..). 1.2. Java Folder ---------------- Remote Studio, or RStudio, is a collection of classes which enable developers to communicate with Omnis Studio remotely. The JAR version is for use in Java, and can be used in any environment which supports Java development. 1.3. Omnis Folder ----------------- For each platform this folder contains the default Webclient installer for supported browsers. These installers contain the complete set of Webclient files. 1.3.1. Auto Installers (Win32 Only) Automatic Installers for Webclient (Windows Only). Automatic Installers allow web users to install Omnis Webclient automatically. Installation is initiated by simply visiting a web page, which contains Webclient content. These installers are currently only available for the windows platform and for Internet Explorer and Netscape 6 browsers. Configuring your Omnis Web Server to support Automatic Installers. To take advantage of Automatic Installers, you should use the new html template file called "template.htm" in your Omnis html directory. Any html generated as the result of local testing will be enabled for Automatic Installation. If you have existing html that you wish to update, you will need to copy the Netscape JavaScript function downloadNow() from the template and place it at an appropriate point in your html page. If your page supports ActiveX controls, you will also need to modify your ActiveX plugin declarations to specify a codebase. By default, the "template.htm" template uses default URLs to point to Automatic installers which reside on the Omnis Server. If you wish to store these on your own server, you should copy the appropriate files from the installation CD and then update "template.htm" to point to your preferred URLs. The installer files are as follows:- omwebie.cab Internet Explorer ActiveX Component Installer. omwebff.xpi Firefox Component Installer 1.3.2. Plugin folder This folder contains all files and components that are used by the Webclient within Microsoft Internet Explorer. These are provided to enable developers to create custom Webclient Installers if required. 1.3.3. Netscape Folder This folder contains all files and components that are used by the Webclient within supported browsers. These are provided to enable developers to create custom Webclient Installers if required. It should be noted the files np_orfc.so and ORFC.class within the Linux created installer should be placed in the plugins folder of the browser and that a folder called 'omnis' should be created to contain the remaining Webclient components. 2. Server Folder ================ This folder contains all of the files that might be required to enable configuration of the Webclient server. The mod_omnis.so provides support for Apache 1.x webservers. Omnislsp provides functionality for enabling a pool a Omnis server processes, running on one or more machines, to serve clients. Servermgmt.lbs provides tools and utilities to monitor connections to the webclient server, including an event log and server usage. 2.1. Omnis NT Service (Win32 only) --------------------------------- If you did not set up Omnis as an NT service during installation of the webclient server version you can register it now by running the following from the command line: NTSERV -install. To remove Omnis as a service run the following from the command line: NTSERV -remove. To run Omnis as console application for debugging run the following from the command line: NTSERV -debug It is important that whenever you use the NTSERV.exe that the file is in the same folder as the Omnis.exe that you are using. 2.2. CGI Folder Typically a Web server will have a place to store all executable code accessible via HTTP over the Internet. This is often the /cgi-bin folder, but it need not be. You will need to place the nph-omniscgi.exe in this folder and ensure that the web server is set up correctly to enable it to be executed. Finally you will need to add the nph-omniscgi.exe path as the WebServerScript parameter in your html files, for example WebServerScript=/cgi-bin/nph-omniscgi.exe 2.3. ISAPI Folder This folder contains the ISAPI or Internet Server API module. This can be used with web servers that support the ISAPI interface. Typically a Web server will have a place to store all executable code accessible via HTTP over the Internet. This is often the /cgi-bin folder, but it need not be. You will need to place the omnisapi.dll in this folder and ensure that the web server is set up correctly to enable it to be executed. Finally you will need to add the omnisapi.dll path as the WebServerScript parameter in your html files, for example WebServerScript=/cgi-bin/omnisapi.dll. 2.4. Servlet Folder To install the servlet on the Tomcat webserver this whole folder needs to be placed in the Webapps folder within the Tomcat installation. The folder called servlet above can then be renamed to anything that the user chooses. When accessing a remote form though this servlet the forms corresponding html page must have the following parameters specified. - WebServerUrl = This must be the URL to the tomcat webserver - WebServerScript = "/servlet/%servletname%" Note: If the user renames the servlet folder then the new name should appear in the WebServerScript parameter instead of servlet. The default value for %servletname% is 'rdtaservlet'. The user can modify this or add others by modifying the web.xml file. The following xml can be added to the element in the document to add a new servlet alias name. For example RdtaServ /%servletname% You will need to restart the webserver in order for the servlet to be loaded. 2.5. Apache2 Folder The mod_omnis.so file provides Apache module support for Apache 2.x webservers.