Thu Jul 18 2002 dynamicXport 1.5 Release All Rights Reserved. Copyright (c) 2001 - 2002 by: Dynamic Concepts, Inc. Aliso Viejo, CA 92656 USA Email address: techsupport@dynamic.com Information: www.dynamic.com Downloads: ftp.dynamic.com Product Description =================== dynamicXport is a portal and RAD (Rapid Application Development) toolkit, consisting of customizable web templates and a software API (Application Program Interface) which enables the creation of a web based presentation layer to existing software and database. dynamicXport requires both an Application server and a Web server. Although both the Application and the Web servers may reside on a single physical system, Dynamic Concepts strongly recommends the usage of two separate systems and that the Application server is secured behind a Firewall. The Web server may be either a Unix server or a Windows IIS server. The Application server may be either a Unix server or a Windows server. Any combination of Unix and Windows servers may be used with dynamicXport. Pre-installation instructions ============================= o This release requires dL4 version 5.1.1 or higher. Users running with a dL4 license prior to version 5 must also acquire a dL4 version 5 SSN. o Problem reports should be emailed to techsupport@dynamic.com. All problem reports should contain a description of the problem, the operating system name/revision, and, if at all possible, a reproducible sequence Highlights of revision 1.5 ========================== o dynamicXport version 1.5, which requires dL4 version 5.1.1, now supports the dynamicXport Application server on a Windows NT/2000 server. New in This Release =================== Jul 18, 2002 (Release 1.5) o dynamicXport version 1.5, which requires dL4 version 5.1.1, now supports the dynamicXport Application server on a Windows NT/2000 server. o See the section, "NT Application Server Installation " in this document. The application server runs on TCP/IP port 9632 in C:\dxapp directory. The installation process requires that dL4 version 5.1.1 or greater is in C:\Program Files\dl4 directory. NT Application Server Installation ================================== 1. Login as Administrator. 2. Unpack dynamicXport distribution. For example, type unzip FF_dxport_1_5.zip to unpack version 1.5 3. Create a temporary installation directory. 4. cd to the temporary installation directory. 5. Extract tar image by using pax, e.g. pax -r < dxport.pax 6. cd ApplicationServer 7. .\instlapp C:\dxapp 8. The installation process uses Notepad to edit the WebServer1IP=LOCALHOST entry in the dxsystem.txt file. Change the LOCALHOST value to the IP address of the application server. Save changes and exit Notepad. 9. .\instsrvr 10. Type ".\instdemo C:\dxapp" from C:\dxapp directory to install dynamicXport optional demo options. Highlights of revision 1.4.1 ============================ o A new option in the dxsystem.txt file allows configuration of the minimum and maximum lengths of dynamicXport user passwords. o The view audit page now shows organization ID. It is now possible to display the username and organization name by placing mouse cursors over User ID and Organization ID values, respectively. o dynamicXport can be used with Verisign Payflow Pro to accept credit card payments. o A new test program, dxbridgetest.dl4, may be used to test a dynamicXport Application server on IP address 127.0.0.1 and TCP/IP port number 9632. New in This Release =================== Jun 28, 2002 (Release 1.4.1) o A new option in the dxsystem.txt file allows configuration of the minimum and maximum lengths of dynamicXport user passwords. These options are PwdMinLength and PwdMaxLength. The default values for minimum and maximum are 5 and 20, respectively. It can also operate with minimum password length set to zero, provided that the appropriate HTML pages accept a zero length password. dynamicXport accepts only the first 32 characters in a password and discards any additonal characters. o The view audit page now shows organization ID. It is now possible to display the username and organization name by placing mouse cursors over User ID and Organization ID values, respectively. o dynamicXport can be used with Verisign Payflow Pro to accept credit card payments. o A new test program, dxbridgetest.dl4, may be used to test a dynamicXport Application server on IP address 127.0.0.1 and TCP/IP port number 9632. Type, "run dxbridgetest.dl4", from the Application server's home directory, and it will display the dynamicXport revision number if the Application server is configured correctly. o Bug Fix: It is possible to use a dynamicXport low security option requiring a secure SSL. o Bug Fix: It was possible to grant user options from a higher level organization. Highlights of revision 1.4 ========================== o A new configuration option in the dxsystem.txt file allows dynamicXport errors to be e-mailed to a designated email address. o Automatic, configurable house-keeping option. o A new configuration option in the dxsystem.txt file controls the frequency of purging dead sessions and audit records. o If the web server cannot open an html output file, then a new configuration option in the dxserver.txt file determines if the name of the missing file should be displayed. o A low security session is not authenticated. New in This Release =================== May 2, 2002 (Release 1.4) o A new configuration option in the dxsystem.txt file allows dynamicXport errors to be e-mailed. Set the "EmailAddress" to the person who should be notified in the event of a dynamicXport error. The "AuditFileType" must also be set to either a "T" or an "F" to enable this new emailing feature. The content of the email message is identical to the log file. o A separate process is automatically started for house-keeping. A single process is invoked the first time the application server is accessed. This process, dxpurge.dl4, runs continuously waking up every 15 minutes to check the dxsystem.txt file to determine if it should purge dead sessions and the audit records. o A new configuration option in the dxsystem.txt file controls the frequency of purging dead sessions and audit records. Set the "CRONFREQUENCY" to the desired value in hours:minutes. The default value (every 15 minutes) is used if the "CRONFREQUENCY" setting is undefined or if it contains an invalid entry. o If the web server cannot open an html output file, then a new configuration option in the dxserver.txt file determines if the name of the missing file should be displayed. Set the "SHOWOUTPUTFILE" to a "Y" if the name of a missing html file should be displayed. Do not set it to a "Y" if the name of a missing html file should not be displayed. o A low security session is not authenticated. o A low security session remains active beyond the "TimeOut" value, meaning it is not authenticated. A low security session is removed if it exceeds the "Elapsed" or "Expired" settings in the dxsystem.txt file and an activation error is reported. o The CyberCash interface program is no longer part of dynamicXport as Verisign, the owners of CyberCash, no longer issues merchant ids to new customers. Please call Dynamic Concepts for alternatives to CyberCash or if you are interested in on-line credit card payments. o Bug fix: It is now possible to create a session if a user from the same IP address attempts to login in less than a second. o Bug fix: An unexpected or subscript error occurred if an application program returned a very large buffer. Highlights of revision 1.3 ========================== o Support for relational operators, AND and OR, in customized logins. o Support for CyberCash CashRegister. o Support for total session count in the View Session option. o Support for ascending or descending sort order in the View Audit option. o Support for summary by option, summary by user and summary by user and option in the View Audit option. o Support for evicting an active session. o Additional dL4 and UniBasic dynamicXport examples programs in the examples directory. o Increased size of a message in the file dxmsg.txt, to 1900 characters. Pre-installation instructions ============================= o This release requires an SSN authorized for release 1 of dynamicXport. dynamicXport will not run without such an SSN. o You _must_ have dL4 version 4.4 or greater and passport version 3.7 or greater (dL4 version 4.4 or greater and passport version 2.1.4 or greater for Windows) with an SSN for dynamicXport installed _before_ installing dynamicXport. o An SSN authorized for release 1 of dynamicXport must be installed _before_ dynamicXport may be installed. o It is assumed that dL4 run is in the /usr/bin directory on the application server. o Both dL4 and UniBasic may be used to develop dynamicXport applications. dL4 developers must obtain dL4 version 4.4 or greater for Unix (dL4 version 4.4 or greater for Windows with passport version 2.1.4 or greater). UniBasic developers must obtain UniBasic version 7.1.1 along with an SSN for UniBasic 7. Regardless of the language of your choice, you must obtain an SSN for dynamicXport. o All problem reports should contain a description of the problem, the product name/revision, the operating system name/revision for both the application and the web server, and, if possible, a reproducible sequence. o Both the user and the audit files contain additional key fields from versions 1.2 or earlier. Thus, these files MUST BE REBUILT using the dxrebuild.dl4 utility program for upgrade from versions 1.2 or earlier. o dynamicXport application server uses shared memory, effective version 1.4. The operating system may require configuration changes for shared memory. dynamicXport will report an "unexpected error" if the operating system is not properly configured for shared memory. Upgrade Instructions ==================== 1. Make a current backup of the directory where DynamicXport is currently installed on the Application server. 2. This version requires dL4 4.4 or greater for Unix or 4.4 or greater for Windows with Passport version 2.1.4 or greater. 3. Both the Application and the Web servers must be upgraded with files from this version. 4. If upgrading from a previous version, simply follow the regular installation procedure for product upgrade. 5. The upgrade procedure keeps a backup copy of the dynamicXport support files in the oldfiles directory. 6. If you wish to retain your older files, then rename oldfiles directory to files. 7. If you want to retain files from revision 1.2.2 or older, please run the dxrebuild.dl4 utility to convert your files. Login as 'dxport' and type the following: run dxrebuild.dl4 Type 'run dxrebuild.dl4 help' for help. Installation instructions ========================= 1. Ensure that you have the latest Passport version installed on your systems. For common platforms, the latest Passport software can be obtained from either www.dynamic.com or ftp.dynamic.com. Older versions of ssnmaint list dynamicXport as product 6. 2. The login page for dynamicXport may be accessed from a JavaScript enabled browser by opening: domain_name/dx/login/dxstd/login.html Application Server Configuration ================================ 3. Login as 'root'. 4. Install dL4 version 4.4 or greater for Unix, along with your dynamicXport SSN. 5. Create a new Unix account named 'dxport'. 6. Create a home directory for the account created in the previous step, e.g. '/usr/dxport'. 7. Configure a Unix Application server by adding new entries in /etc/services and /etc/inetd.conf files. Entries in /etc/services and /etc/inetd.conf, respectively, should look something like the following: dxport 9632/tcp # dynamicXport tcp/ip port 9632 in /etc/services file # the entry below in /etc/inetd.conf file is for dynamicXport dxport stream tcp nowait dxport /usr/bin/run run -XB /usr/dxport/dxlistener.dl4 8. Login as 'dxport'. 9. cd to the temporary installation directory, e.g. /tmp/dxport. 10. Copy the distribution file to any temporary directory on your system, e.g. "/tmp". 11. If the distribution file has a ".Z" extension, uncompress the file using the command "uncompress filename.Z". If the file has an extension of ".z", then rename the file with an uppercase "Z" before uncompressing the file. 12. Unpack the distribution file using the command "cpio -imcduv Programs ==> Windows NT 4.0 Option Pack ==> Microsoft Internet Information Server ==> Internet Service Manager 8. Select the domain site. 9. Select "Properties" with a right mouse click. 10. Select the "Home Directory" tab. 11. Press the "Configuration" button on "Application Settings". 12. Select the "App Mappings" tab. 13. Press the "Add" button. 14. Type the following as a single line in the box labeled "Executable" with a space between each of the three values: "C:\Program Files\dl4\runc.exe" D:\InetPub\wwwcust\domain_name\dx\cgi-bin\dxserver.dl4 dx\cgi-bin\dxserver.txt 15. Type ".cgi" in the box labeled "Extension". 16. Select the "Apply" button. 17. Select the "OK" button. New in This Release =================== Jan 4, 2002 (Release 1.3) o It is now possible to login using any of the fields in the user file. This alternate login method, i.e. other than User ID and password usage, requires defining a LOGINFIELDS in the dxsystem.txt file. The syntax for LOGINFIELDS is: LOGINFIELDS=a field in the user file AND/OR another field Please note that the & symbol is the AND operator, and the | symbol is the OR operator. The AND operator has a higher precedence than the OR operator. The expression is evaluated from left to right, but the precedence order may be modified by using parentheses. You may add as many fields as you require, provided that the fieldname is a valid fieldname in the user file (dxuser). However, the total size of LOGINFIELDS is limited to 254 characters. Unlike the AND and OR operators, the first defined field in LOGINFIELDS is used to index into the user file. The alternate login method also requires customizing the login and the verification html page. Example: LOGINFIELDS=username&(password | useremail) o CyberCash may be accessed by calling (running) the dxccbridge.dl4 program. You must, however, first obtain your CyberCash ID from CyberCash. Please visit register.cybercash.com to sign up for CyberCash. o You can get a total session count by checking "Show Session Count" checkbox option on "View Sessions" page. o You may now evict another session from the "View Sessions" page. o It is now possible to run an SSL option from dxbridge.dl4. o It is now possible to view ascending and descending detail audit logs. o It is now possible to get summary by option, summary by user, or summary by user and option from the "View Audit" page. o Increased size of a message in the file dxmsg.txt, to 1900 characters. o The demo options may be added anytime by running the dxcreatedemo.dl4 program from the 'dxport' account. o The demo example files may be created by running docreate.dl4 o The "Prelink" field must be set to blank for the MASTER organization. o Bug fixed: Pressing the "login" icon repeatedly on the login page resulted in a login session error. o Bug fixed: Attempting to add a new option with a runtime only license reported an "Option not in file" error message. o Bug fixed: Users with non-MASTER organization IDs were unable to login. o Bug fixed: It was possible to remove the "admin" user using the dxbridge.dl4 program. o Bug fixed: S_ViewOptionType and session id fields were not returned while attempting to run non-securely an option that requires an SSL connection. o Bug fixed: It was possible to have non-alphanumeric characters in a password using the bridge program. o Bug fixed: S_VIEWOPTIONTYPE was not returned on Validate page. =================== Jul 16, 2001 (Release 1.2.2) o It is now possible to output a user defined value for "Content-Type". DynamicXport automatically adds the two required 'CR's following the content-type value. o The dxbridge.dl4 program is now accessible to all users with a permission setting of 644. o The session ID is provided as an encrypted session id to an application program. o Bug fixed: A non-administrative user was able to add a new user using the dxbridge.dl4 program. o Bug fixed: A non-administrative user was able to change an existing user using the dxbridge.dl4 program. o Bug fixed: The Parent ID must be set to Null for a menu option type. o Bug fixed: Only audit records with proper permissions are displayed. Earlier releases displayed all audit records. o Bug fixed: Input and output of an extended audit log record is from the application's perspective, meaning input to and output from an application program. o Bug fixed: An existing U_ field is now updated with new values between sessions. o Bug fixed: Updated U_ fields' values are now logged in the extended log file. o Bug fixed: A user is now permitted to have more than 10 menu options. o Bug fixed: Those options that require SSL connections now run as https connections. o Bug fixed: Users were unable to login using browser settings for a proxy server such as a Microsoft Proxy server. New in This Release =================== May 16, 2001 (Release 1.2.1) o The dxinstall script will _NOT_ install the product unless an SSN authorized for dynamicXport has already been installed. o The dxinstall script will _NOT_ install from the super-user (root) account as the dynamicXport files must be owned by the Application server account (default dxport). o Provides improved Wireless Access Protocol (WAP) support. o The CheckBrowser option in the dxserver.txt file _must_ be set to WML to enable WAP support. o The CopyUser field is returned with Change user option with the dxbridge.dl4 program. o The dxbridge.dl4 program may add or modify a user's CopyUser field. o dynamicXport will run with a demo SSN and dL4 version 4.4 or greater. o Supports both Microsoft Internet Explorer browser versions 4 and 5. o Bug fixed: It was not possible to run an option without first logging in. o Bug fixed: The dxbridge.dl4 program received an "illegal subscript" error. o Bug fixed: The "View Audit" option did not display more than one page. o Bug fixed: The "Begin HTML Test Page" option was unable to find the HTML page filename. New in This Release =================== May 7, 2001 (Release 1.2) o OutsideIP, SecondaryServer, and AllowLocalHost options have been removed from the dxsystem.txt file. o The dxtestapp.dl4 program is no longer distributed. The dxbridge.dl4 program may be used to test dynamicXport application programs. o The product now uses a new option, REVISION, as 1.2 for this release in the dxsystem.txt file. o A new option, WebServerXIP, in the dxsystem.txt file controls the valid IP address of the webserver. The X in WebServerXIP is a sequential number for each webserver, starting with one (1) as the first webserver. o A new option, BridgeXIP, in the dxsystem.txt file controls the valid IP address of the local webserver. The X in BridgeXIP is a sequential number for each server, starting with one (1) as the first server. o A new option, AuditFileType, in the dxsystem.txt file enables connection logging. Connection logging may be enabled by setting the AuditFileType value to "T" for non-extended logging, and "F" for extended logging. Connection logging may be disabled by setting the AuditFileType value to nothing. o A new option, PurgeAuditAge, in the dxsystem.txt file specifies the number of days audit records are archived. All audit records older than the PurgeAuditAge are purged. o A new option, BufSize, in the dxsystem.txt file specifies the dynamicXport buffer size in characters for efficient memory management. Although it is restricted to 1024 as its minimum value, the maximum value is limited to free memory availability. The default value is 128K characters. o A new option, GlobalExtendedLog, may be used to log additional information. The extended log filename is audit.ext and must be purged by the developer as needed. These extended logging capabilities may be used as a debugging aid during program development. o A new program, dxpurge.dl4, may be run on the applicationer server to remove old audit and session records. o The dxbuildfiles script builds dynamicXport support files. This script may be run anytime after installation to re-build support files. It keeps a backup copy of the original files directory as oldfiles directory. o dynamicXport auto-configures the value for S_Root if it is undefined in the dxserver.txt file. The REVISION option (open domain/dx/cgi-bin/dxserver?OPTION=REVISION from a browser) displays the recommended value for S_Root, if it is undefined in the dxserver.txt file. The S_Root should be set in the dxserver.txt file to improve performance. o A new option, ConnectRetryCount in the dxserver.txt file controls the number of connection attempts with the Application server before an error is reported. o A new option, DXBUFSIZE, in the dxserver.txt file specifies dynamicXport buffer size in characters for efficient memory management. Although its value is restricted to 1024 as its minimum value, the maximum value is limited to free memory availability. The default value for is 128K characters. o dynamicXport now supports WAP (Wireless Access Protocol) enabled browsers. o A new option, CheckBrowser in the dxserver.txt file enables WML (Wireless Markup Language) if WML is supported by the user's web browser. The syntax for CheckBrowser in the dxserver.txt file is CheckBrowser=WML. o The DXContent option in the dxserver.txt file controls the type of webserver URL encoding. This release of dynamicXport supports only HTML. o A new option, S_ContentOut in the dxserver.txt file controls the browser output header. The value is changed to WML if the browser supports WML and the CheckBrowser is set for WML. It is always set to the same value as the DXContent if the S_ContentOut is undefined in the dxserver.txt file. o A new option, S_ContentOut in the dxserver.txt file controls the browser output header. The value is set to WML if the browser supports WML and the CheckBrowser specifies WML. It is always set to the same value as DXContent if the S_ContentOut is undefined in the dxserver.txt file. o A new option, E_EnvironmentVariableName in the dxserver.txt file specifies which environment variables as seen by the web server are provided to the application programs. The syntax does not require a value for these fields. For example, setting E_HTTP_ACCESS as E_HTTP_ACCESS= in the dxserver.txt file allows an application program access to the HTTP_ACCESS environment variable as seen by the web server. o For Linux Apache and Microsoft IIS web servers, set the S_URL option in the dxserver.txt file to your domain name (e.g. http://www.dynamic.com). o For Linux Apache and Microsoft IIS web servers, set the S_SECUREURL option in the dxserver.txt file to your domain name (e.g. https://www.dynamic.com). o Times displayed on all browser pages reflect local time on the application server. o The example file contains a single customer record with DCI as its Customer ID. o The example file contains a single customer record with DCI as its Customer ID File list ========= dxinstall Installation script dxbuildfiles Builds dynamicXport support files license.txt dynamicXport product license file readme.txt dynamicXport product readme file ApplicationServer dynamicXport files for Application Server dxadmin.dl4 dynamicXport administrative program dxbridge.dl4 dynamicXport bridge program dxbridgetest.dl4 dynamicXport bridge test program dxchecklicense.dl4 part of dynamicXport installation script dxcreatecontacts.dl4 Creates dynamicXport dxcontacts support file dxcreatedemo.dl4 Creates dynamicXport example demo dxcreateoption.dl4 Creates dynamicXport dxoption support file dxcreateorg.dl4 Creates dynamicXport dxorg support file dxcreatesession.dl4 Creates dynamicXport dxsession support file dxcreateuser.dl4 Creates dynamicXport dxuser support file dxcreateuseroptions.dl4 Creates dynamicXport dxuseroptions support file dxcreateview.dl4 Creates dynamicXport dxview support file dxerror.lib dynamicXport library module dxfullisamio.lib dynamicXport library module dxgeneral.lib dynamicXport library module dxgetplatformno.dl4 gets dynamicXport platform ID dxio.lib dynamicXport library module dxlistener.dl4 dynamicXport Application server runtime module dxmsg.txt dynamicXport message file dxpurge.dl4 Purges old audit and session records dxrebuild.dl4 Rebuilds dxynamicXport system files dxsocket.lib dynamicXport library module dxsystem.txt dynamicXport Application server file dxverisignpayflow.dl4 Supports Verisign Payflow Pro. examples/ dynamicXport example programs instlapp.bat batch file to install NT application server instdemo.bat batch file to install demo on NT instsrvr.bat batch file to install NT application server WebServer dynamicXport files for Web Server admin/ Contains HTML files admin/images/ Contains graphics (gif) files cgi-bin Contains CGI programs and libraries cgi-bin/dxerror.lib cgi-bin/dxfullisamio.lib dynamicXport library module cgi-bin/dxgeneral.lib cgi-bin/dxio.lib dynamicXport library module cgi-bin/dxsocket.lib cgi-bin/dxserver.dl4 dynamicXport Web server runtime module cgi-bin/dxserver.cgi cgi-bin/dxserver.txt dxstd/ Contains HTML files dxstd/icons/ Contains graphics (gif) files dxstd/images/ Contains graphics (gif) files examples/ Contains HTML files includes/ Contains JavaScripts and HTML files login/ Contains subdirectories login/dxstd/ Contains gif files and HTML file styles/ Contains cascading style sheets (css) files Copyright ========= CyberCash CashRegister is a trademark or registered trademark of CyberCash, Inc. in the United States and other countries. Platforms ========= Operating system information for dynamicXport 1.5 production: ID Platform "uname -a" ---------------------------------------------------------------- FF All platforms Not applicable