FlashCONNECT 3.
Copyright (c) 1982, 2004. Raining Data Corporation. All rights reserved. Raining Data, TigerLogic, D3 (referred to as D3), Pick, Omnis, mvDesigner, and mvEnterprise are registered trademarks or trademarks of Raining Data Corporation. This product may include or be accompanied by software developed by third parties, including those listed below. Software from third parties may be subject to additional or different license terms.
Preface This publication is intended for a technical audience with knowledge about a database (D3 or mvBase), BASIC, some knowledge of UNIX or Windows, and moderate knowledge of HTML and the Internet.
Preface Document Conventions In this document, references to Windows include: • Windows 2000 • Windows XP Professional (Pro) • Windows 2003 In this document, references to UNIX include: • AIX • Linux • SunOS (Web server components only) All Windows dialog boxes, edit boxes, screens, and product displays in this guide are shown in Windows 2000. Some features and options may not be available or may be accessed differently on other Windows systems.
Document Conventions Convention Description n{-m} The letters n and m represent numbers. Numbers are usually input as a single string without commas. Numbers can also be used to define a range designation. The starting and ending numbers are typed with a hyphen between. For example, n{-m} could be replaced by 10 or by 1-31. {} Braces ( { } ) delimit a mutually exclusive set of options. on | off The vertical line or pipe sign ( | ) separates a mutually exclusive set of options.
Preface Related Documentation To download or order related documentation published by Raining Data Corporation, please refer to the Raining Data Web site at: http//www.rainingdata.com/support/documentation/index.html These links can also be used to access the FlashCONNECT Programmer’s Online Reference quickly.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . Active Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1 ... ... ... ... .... .... .... .... Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Adding FlashCONNECT Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Deleting FlashCONNECT Groups . . . . . . . . . . . . . . . . . . . . . . . . .33 Adding Users to Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Removing and Adding Users from Membership Lists . . . . . . . . . . . .34 Deleting FlashCONNECT Users . . . . . . . . . . . . . . . . . . . . . . . . . .34 Assigning Users and Groups to Dynamic Applications . . . . . . . . . . .
Contents Customizing the Local Environment . . . . . . . . . . . . . . . . . . . . Environment tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Startup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FlashCONNECT Service . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 9 .... .... .... .... 89 89 90 92 Customizing the FlashCONNECT Server and Web Server . . . . . 95 Using WWW-STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Application Debug Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Static Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Dynamic Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Determining if the Application is in the Debugger . . . . . . . . . . . . 147 Using the FlashCONNECT Server Debug Program . . . . . . . . . . . . . 147 Debugging Server Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1 Introduction This publication is intended for administrators knowledgeable about: • D3, mvBase, and Pick BASIC • UNIX or Windows operating systems • HTML and the Internet All topics apply to both the UNIX and Windows platforms, unless a specific platform is specified. We hope this guide is a valuable tool for administering and maintaining the FlashCONNECT software.
Chapter 1: Introduction About This Document The purpose of this publication is to explain FlashCONNECT system administration. NOTE— The FCService components are necessary only for FlashCONNECT dynamic applications and mvDesigner. Topic Descriptions Use the table below as a guide to this document. 2 Type Topic Description Chapter 1 Introduction Discusses key concepts and explains how FlashCONNECT works. Chapter 2 Getting Started Discusses the steps to take after installing FlashCONNECT.
About This Document Type Topic Description Chapter 8 Configuring, Starting and Stopping FlashCONNECT Components Provides turnkey installation instructions, customizing the local environment, starting and stopping FCService, and starting FlashCONNECT with D3. Chapter 9 Customizing the FlashCONNECT Server and Web Server Discusses FlashCONNECT heartbeats, customizing WWW-IRUN and unnamed Common.
Chapter 1: Introduction Document Conventions Different typefaces and type styles are used throughout this guide to indicate specific kinds of information. NOTE— • Although the database account containing the FlashCONNECT software may be named differently for your installation, this document usually refers to it as the www account. • In some cases where a software change will be implemented soon, you may notice that this document differs from actual displays in your specific installation.
About This Document Entering Data Action Description Enter Input the specified commands or text as shown in the instruction and then press the carriage return key, usually labeled as , , or on your keyboard. Type Input the specified commands or text as shown in the instruction. Do not press the carriage return key unless instructed. Press Press the single specified character or combination of characters as instructed.
Chapter 1: Introduction File Naming Conventions The w3... file names (w3Exec, w3HtmlInsert, and so on) use capitalization to make them easier to read in the text. The casing is not necessary when typing them in your applications.
About FlashCONNECT About FlashCONNECT Earlier releases of FlashCONNECT provided a browser-based middleware component between FlashCONNECT clients, Web servers and the D3 or mvBase database. This enabled remote, cross-platform capabilities for programmers to write and post applications using Pick BASIC subroutines and to display these applications in HTML templates, creating viewable Web pages.
Chapter 1: Introduction FlashCONNECT is a middleware package that connects Pick BASIC business rules with TCP/IP-based external components such as Web servers, Java programs, Javascript, Visual Basic programs and mvDesigner servers. FlashCONNECT uses either CGI, ISAPI, Java Servlet or a TCP/IP connection to an mvDesigner server. FlashCONNECT also uses named pipes for inter-process communication. FlashCONNECT subroutines send a Web page to the user’s browser.
About FlashCONNECT FlashCONNECT’s connection to a browser or to an mvDesigner server provides a graphical user interface for your database application and meets many of today’s e-commerce requirements by offering these features: • Transparent interoperability with mvDesigner, a connection between the database and an mvDesigner server that provides a graphical user interface. • Compatible with browsers and Web servers.
Chapter 1: Introduction • Uses familiar Pick BASIC programming subroutines to get you up and running quickly. • Creates static and active (or dynamic) Web pages from database queries. • Supports Secure Socket Server Layers. • Enhances Web server performance with FlashCONNECT Java Components. Before installing FlashCONNECT, think about the features you want to use and how you want to use this product.
Architecture Architecture The diagram below illustrates the fundamental components of FlashCONNECT and mvDesigner.
Chapter 1: Introduction Selecting a Web Server Almost any Web server can be used as long as it supports the CGI and ISAPI interface, which most Web servers do. The FlashCONNECT product has been tested with: 12 • UNIX with Netscape and Apache Web servers • Windows 2000 IIS 5.0/XP IIS 5.1/2003 IIS 6.
FlashCONNECT Application Types FlashCONNECT Application Types There are two types of applications that can be built with FlashCONNECT: • static (also referred to as inactive) • dynamic (also referred to as active) The table at the end of this topic provides comparisons. Static A FlashCONNECT application that builds static Web pages does so without processing input from the user. When static Web pages are built from a rarely changing set of data, static FlashCONNECT applications are the best choice.
Chapter 1: Introduction BASIC applications. This allows the BASIC programmer to focus on writing an application, not on managing Web pages.
About mvDesigner About mvDesigner mvDesigner (a separate product from FlashCONNECT) is an application development environment used with the mvDesigner client and server. FlashCONNECT includes the mvDesigner API that allows Pick BASIC applications to work with mvDesigner; either by driving mvDesigner screens from D3 or by encapsulating FlashCONNECT business rules in mvDesigner applications.
Chapter 1: Introduction Interactive Multiuser Web Applications FlashCONNECT Sessions A session begins when a user reaches the first form. At that time, the FlashCONNECT connection is available only to the browser that started the session. Unless initialized by the application, the FlashCONNECT logon screen does not start a session. A session ends when the FlashCONNECT application returns to the FlashCONNECT application that called it.
Interactive Multiuser Web Applications Web Browsers HTTPD Server Give me record "1234" Joe’s Browser Here is record "1234" Give me record "1234" Wally’s Browser Here is record "1234" Update record "1234" Update record "1234" Joe’s Browser Give me record "1234" Wally’s Browser Here is record "1234" but it is not what you think... Clicking a browser link sends a message to the server. The server responds by sending the document.
Chapter 1: Introduction Web Browsers HTTPD Server Give me record "1234" Joe’s Browser Wally’s Browser Joe’s Browser Here is record "1234" Give me record "1234" Sorry, that record is locked Update record "1234" Give me record "1234" Wally’s Browser Here is (updated) record "1234" Explanation of Our Solution In addition to the Web browser and the HTTPD server, the FlashCONNECT solution includes two elements: 18 • Web server (includes the FlashCONNECT CGI or ISAPI connector and FCService) • Dat
Interactive Multiuser Web Applications A detailed explanation of each element, along with the FlashCONNECT solution, is illustrated in the example below. Web Server The Web server includes the FlashCONNECT CGI, ISAPI, and Java Servlet connectors and FCService. fccgi.exe, fcisapi.dll, or FCServlet UNIX: The HTTPD server starts the connector application fccgi.exe or FCServlet when it receives an HTTP connection destined for a FlashCONNECT dynamic application.
Chapter 1: Introduction Database Server FlashCONNECT consists of an API and subroutines that implement the API. On the database server, an application runs as a called subroutine under the FlashCONNECT driver, WWW-IRUN. Before the connection is made, authorization to use the application is authenticated where applicable. Once authenticated, a new session begins. See the FlashCONNECT Administrator’s Guide for more information.
Interactive Multiuser Web Applications This example continues using the URL in the diagram above. When a URL is entered into the browser the following occurs: • Address portion of the URL (http://www.hostname.com/) is used to contact the Web server at that address and requests the specified page (/cgi-bin/ fccgi.exe?). • Web server processes the request and, since the requested page is an application, executes the application. • Web server starts fccgi.exe, fcisapi.
Chapter 1: Introduction Using Virtual Directories A virtual directory is an alias for another directory, which is an additional name for a directory that actually exists on the disk. Virtual directories are used in FlashCONNECT in two ways: To maintain a consistent environment between the Windows Web servers and the UNIX Web servers. Windows Web server, IIS, creates a folder called scripts. This folder is located in the Inetpub directory (\Inetpub\scripts).
Using Virtual Directories • Copy the WebContent directory and place it under the document root directory. Rename the WebContent directory w3library. On UNIX platforms, these steps are done for you as part of the standard installation process.
Chapter 1: Introduction 24 FlashCONNECT Administrator’s Guide
Chapter 2 Getting Started Once FlashCONNECT is installed, if you intend to use secured applications, you must: • set up groups and users. • change any configuration settings if you do not want to use the default settings. • configure server pools. • configure FlashCONNECT socket servers.
Chapter 2: Getting Started Administrative Tasks The following is a list of FlashCONNECT administrative tasks and the location in which to access them: FlashCONNECT Maintenance Web Pages • Setting up and configuring server pools. • Setting up groups and users. • Performing maintenance functions for users, groups and applications. • Adding, editing, deleting or assigning groups and/or users to applications.
Administrative Tasks Information about setting up FlashCONNECT components is located in: • Maintaining Applications, Groups, and Users • Administering Server Pools • Accessing Administration Reports • Administering the FlashCONNECT Socket Server Manager • Understanding FlashCONNECT Java Components • Configuring, Starting and Stopping FlashCONNECT Components • Customizing the FlashCONNECT Server and Web Server • Administering Log and JOBS Files • Using Character Translation w3Users, w3App
Chapter 2: Getting Started • Dynamic. Dynamic Web pages that do interact with the database may require group level and/or user level authentication.
Chapter 3 Maintaining Applications, Groups, and Users Use the FlashCONNECT Maintenance Web pages to set up, delete and maintain FlashCONNECT users and groups, and FlashCONNECT application privileges. After users and groups are set up, assign them access to dynamic applications in the w3Apps file. NOTE— This topic describes performing various administrative tasks from the FlashCONNECT File Maintenance Web page. These menus and maintenance screens are also accessible from the www account. For example: 1.
Chapter 3: Maintaining Applications, Groups, and Users Logging On to FlashCONNECT Maintenance Pages Access the FlashCONNECT Maintenance Web pages via your browser using the host name or URL address assigned to your Web server. For example: ttp://yourwebhost/w3library/w3admin.htm The FlashCONNECT Maintenance Menu displays. To log on to a FlashCONNECT Maintenance Page: 1. Select the FlashCONNECT Maintenance page to log to (for example, User Groups or Server Pools.
Logging On to FlashCONNECT Maintenance Pages The Log On screen displays. 2. Enter the name and password (as stored in the W3USERS file). NOTE— If you do not want the Log On page to display, update the w3Apps file entry for the w3Admin application to enable the Anonymous option. The specified page displays: NOTE— Screen information is maintained should a timeout occur. So, if you have entered any data prior to the timeout, that information is processed and updated after logging on again.
Chapter 3: Maintaining Applications, Groups, and Users Adding FlashCONNECT Groups Use the FlashCONNECT Group Maintenance Web page to add, edit or delete groups that are allowed to access dynamic applications. Members of groups are restricted to the applications assigned to that group. However, if a member belongs to more than one group, that member may have access to other applications as well.
Adding FlashCONNECT Groups Deleting FlashCONNECT Groups Deleting groups permanently removes the group and its members from accessing any applications. To delete groups: • From the FlashCONNECT Group Maintenance Web page, select the check box of the group you want to delete, then click Submit. Adding Users to Groups Every user name in the w3Users file is in either the Members or Non-Members list box.
Chapter 3: Maintaining Applications, Groups, and Users 3. Type the user’s name in the User Name column. 4. (Optional.) Type a password for the user in the Password column. The password may include a maximum of 28 alphanumeric characters. 5. Select the group or groups to which you want to add the member from the Non-Member list, then click Submit. The groups for which the user is a member display in the Member list.
Adding FlashCONNECT Groups Assigning Users and Groups to Dynamic Applications You can assign users and groups to dynamic applications through the w3Apps file or from the FlashCONNECT Applications Selection Web page. If you use the FlashCONNECT Applications Selection Web page, a list of your applications is available from the drop-down list box. To assign users and groups to new or existing applications, or to edit application information using the FlashCONNECT Applications Selection Web page: 1.
Chapter 3: Maintaining Applications, Groups, and Users The FlashCONNECT Applications Maintenance Web page displays. 3. (Optional.) Type any additional application information in the Description text box. 4. Select the users you want to access this application from the Non-Members list box. 5. (Optional.) Type the application name in the Program text box if the name differs from the application name. 6. (Optional.
Adding FlashCONNECT Groups Option Description Anonymous Enables users access to applications without entering their user ID or password. Debug Mode Enables debugging capabilities. 9. Select the names of the groups that you want to access this application from the Non-Members list box. 10. (Optional.) Type the number of seconds in the Timeout text box to indicate the amount of time to the user name and password is remembered if Profile is selected. Set Timeout to 0 or null to disable this feature. 11.
Chapter 3: Maintaining Applications, Groups, and Users 38 FlashCONNECT Administrator’s Guide
Chapter 4 Administering Server Pools FlashCONNECT’s server pooling extends the concept of connection pooling. Connection pooling enables applications to reuse a connection from a pool of connections. Once a connection is created and placed in the pool, an application can use a connection within the same pool without performing the complete connection process. Connections (when released by an application) remain available, waiting for the next occasion they are needed.
Chapter 4: Administering Server Pools Using Server Pools Server pooling extends connection pooling capabilities by allowing the naming and grouping of one or more FlashCONNECT connections. Server pools can connect one or more database servers to one or more Web servers. Server pools enable the distribution of an application across several systems, and allow load balancing and tighter control of resource allocation. Setting up, configuring and using server pools are optional.
Using Server Pools POOLNAME Server pool name of this set of FlashCONNECT servers. The name is case-sensitive. If left blank, these servers are added to the default pool. For example, to start ten connections in the GAME server pool on www.rainingdatagames.com (assuming that www.rainingdatagames.com has a Web server and FlashCONNECT service running on it), use this command: WWW-START 10 WWW.RAININGDATAGAMES.
Chapter 4: Administering Server Pools Examples: • To stop all GAME servers, use the command: WWW-STOP GAME • To stop only the server running on database line number 98, use the command: WWW-STOP 98 • To stop all entries in the default server pool on this database server, use the command: WWW-STOP DEFAULT Connecting Database Server Pools FlashCONNECT allows one or more database servers to connect to one or more FlashCONNECT enabled Web servers.
Using Server Pools • The system administrator specifies which server pool a system supports using the WWW-START command or via server pools configuration. • The programmer specifies which server pool is used to service a request by setting the w3ServerPool variable. • FlashCONNECT assigns the connection to any database server that supports the requested server pool. If no server pool is specified, the default server pool is used. WARNING— • Server Pool names are case sensitive.
Chapter 4: Administering Server Pools The following example shows which database servers are available to each Web server when a request to the server pool is made. Requested Pool Accounting Payroll Sales Web Server 1 Database Server 1 or 2 Database Server 2 Database Server 1 or 2 Web Server 2 Database Server 2 Database Server 2 or 3 Database Server 2 or 3 Specifying the Relationship Specify which system should process a request and which server pool to use in processing that request.
Using Server Pools Server pool: Accounting Min Max MaxFree MinFree Freq Port HB Period WEBSERVER1 1 3 2 1 60 1505 120 WEBSERVER2 1 3 2 1 60 1505 120 WEBSERVER1 1 3 2 1 60 1505 120 WEBSERVER2 1 3 2 1 60 1505 120 Max MaxFree MinFree Freq Port 1 3 2 1 60 1505 120 1 3 2 1 60 1505 120 Server pool: Sales Database Server 3: Server pool: Payroll WEBSERVER1 Min HB Period Server pool: Sales WEBSERVER2 The following commands manually start the same serve
Chapter 4: Administering Server Pools FlashCONNECT enabled Web server should use. In the following examples, Apps represents an item in the w3Apps file. Using the information in the Web Server 1 row in the table above: • to specify Web Server 1 for the Accounting server pool to Database Server 1 or 2, use the URL: http://WebServer1/cgi-bin/fcisapi.
Using Server Pools 2. Assign the connection (to any database server which supports that server pool). See Assigning the Connection. 3. Set up w3Monitor on each database server to maintain a minimum of one or more free connections to the Web server. How it Works: For example, there are two database servers (A and B) supporting one Web server. Two connections to the default server pool are made from each database server to the Web server (Table 2).
Chapter 4: Administering Server Pools 1. Database A Yes 2. Database A Yes 3. Database B Yes 4. Database B Yes 5. Database A No 6. Database B No From this point forward, as additional connections are requested, they are alternately assigned to each database server. w3Monitor creates additional connections as needed until the configuration limits are reached, thus balancing the load. As connections are dropped, they are reassigned in connection number order.
Chapter 5 Accessing Administration Reports The FlashCONNECT Maintenance Menu Pages provide access to several administration reports: • Concurrent FlashCONNECT Use Report • FlashCONNECT Sessions Report • FlashCONNECT Contacts Report • FlashCONNECT Redirect Report • FlashCONNECT Rotating Content Report • FlashCONNECT Line Status Report FlashCONNECT report descriptions and sample reports are available here and online.
Chapter 5: Accessing Administration Reports Concurrent FlashCONNECT Use Report The Concurrent FlashCONNECT Use report indicates the number of FlashCONNECT ports being used during various periods. Use this report to see the volume of traffic and to determine if more connections are needed. Periods with no usage are not shown. Each FlashCONNECT port is counted only once, so the information represents an estimate of the number of concurrent FlashCONNECT users.
FlashCONNECT Sessions Report FlashCONNECT Sessions Report The FlashCONNECT Sessions Report provides information about each completed FlashCONNECT session. Use this report to determine who is running what applications. The following information is reported for each completed session: • FlashCONNECT port used. • Session starting date. • Session starting time. • Session duration including the hours, minutes and seconds that the process was run. • FlashCONNECT Profile ID. • Client IP address.
Chapter 5: Accessing Administration Reports FlashCONNECT Contacts Report The FlashCONNECT Contacts Report shows the volume of FlashCONNECT traffic, providing the raw number of active FlashCONNECT sessions (or hits) during a time period. The date and time, as well as the number of FlashCONNECT sessions, is listed.
FlashCONNECT Redirect Report FlashCONNECT Redirect Report The FlashCONNECT Redirect Report lists the number of FlashCONNECT click-throughs to other sites. Use this report to monitor the click-throughs that have occurred on your site. The following information is reported: • Click-through date and time. • FlashCONNECT port used. • Web page containing the link or the page that the user navigated from. • Destination or the page the user navigated to. • Client IP address.
Chapter 5: Accessing Administration Reports FlashCONNECT Rotating Content Report The FlashCONNECT Rotating Content Report details the use of rotating content. Since rotating content can be a revenue source, you may want to use this report to monitor it. The following information is reported: • Date and time used. • FlashCONNECT port used. • Client IP address. • FlashCONNECT Profile ID. • Value used or the name of the object being used.
FlashCONNECT Line Status Report FlashCONNECT Line Status Report The FlashCONNECT Line Status Report details the current connection status. Use this report to monitor the line status. The following information is reported: • FlashCONNECT line number. • Server Pool name. • Server host name. • FlashCONNECT Listening Server port. • Status from the w3lines file. • Start date and time. • Socket or the TCP/IP port on the D3 server. • Application being run. • User name, if any.
Chapter 5: Accessing Administration Reports 56 FlashCONNECT Administrator’s Guide
Chapter 6 Administering the FlashCONNECT Socket Server Manager FlashCONNECT uses the FlashCONNECT Socket Server Manager to connect to the mvDesigner client and server. This enables Pick BASIC applications to communicate with mvDesigner forms to provide a graphical display of your database queries.
Chapter 6: Administering the FlashCONNECT Socket Server Manager Accessing the FlashCONNECT Socket Server Manager The FlashCONNECT Socket Server Manager (fcss.jar) installs with FlashCONNECT, provided a Java Virtual Machine is available on your machine. Please see the FlashCONNECT Installation Guide for more information. Windows: To verify the location of the fcss.jar file: 1. Select Start > Programs > Raining Data > FlashCONNECT > Configure from the Start menu.
Accessing the FlashCONNECT Socket Server Manager UNIX: During installation, enter the path to the directory for the FCSocket server: Enter the path to the directory for the FCSocketServer script used to start and stop the FlashCONNECT Java component [/usr/bin](Q=QUIT): Starting the FlashCONNECT Socket Server Manager The FlashCONNECT Socket Server Manager provides a visual interface for starting, stopping and monitoring socket servers.
Chapter 6: Administering the FlashCONNECT Socket Server Manager The FlashCONNECT Socket Server Properties dialog box displays. 4. (Optional) Change any of the following: • Display name. Change this to another descriptive name. • Description. Add additional information. • Startup type. Select Automatic, Manual or Disabled. • Start or Stop the Socket Server service. 5. (Optional) Select the Log On tab. a.
Accessing the FlashCONNECT Socket Server Manager Starting the FlashCONNECT Socket Server Manager Manually This procedure starts the FlashCONNECT Socket Server Manager and the port that you set in the configuration. Windows: 1. Open the MS-DOS Window. 2. Type: FCSocketServer -start 3. Press Enter. The FlashCONNECT Socket Server Manager dialog box displays. UNIX: To run the FlashCONNECT Socket Server Manager graphical user interface, X Windows must be installed.
Chapter 6: Administering the FlashCONNECT Socket Server Manager Using the FlashCONNECT Socket Server Manager The FlashCONNECT Socket Server Manager dialog box provides server information in the upper pane and monitoring information in the lower pane. The FlashCONNECT Socket Server Manager allows you to add new socket servers, start and stop socket servers, and monitor socket server events.
Using the FlashCONNECT Socket Server Manager The Start FCSocket Server dialog box displays. 2. Type the port number, then click OK. NOTE— The TCP/IP Port number range is 1025-65535. Click Reset to return to the initial port number. Stopping FlashCONNECT Socket Servers If you have multiple FlashCONNECT socket server ports, you can stop a connection at any time using the FlashCONNECT Socket Server Manager. To stop a FlashCONNECT Socket Server: Windows and UNIX: 1.
Chapter 6: Administering the FlashCONNECT Socket Server Manager • Select FlashCONNECT Socket Server from the list. Right-click and select Stop from the pop-up menu. • Click Exit from the FlashCONNECT Socket Server Manager dialog box. UNIX: Do one of the following: • Click Exit from the FlashCONNECT Socket Server Manager dialog box. • At the prompt, type: .
Using the FlashCONNECT Socket Server Manager The Terminate a Client dialog box displays. 3. Type the FlashCONNECT Socket Server port number in the text box. 4. Type either the Client WorkerID or the IP address depending on the type of connection you are terminating. 5. Click OK. Using the FlashCONNECT Socket Server Log The FlashCONNECT Socket Server log information can be displayed in either or both the Monitoring pane and log file.
Chapter 6: Administering the FlashCONNECT Socket Server Manager The FlashCONNECT Socket Server Log records the following information: Log Options Description Error Unable to service a request. Internal or protocol error. Access Provides logon history and information. Detail Displays FlashCONNECT Socket Server and mvDesigner Server messages. Displays each message sent and received by the FlashCONNECT Socket Server Manager.
Using the FlashCONNECT Socket Server Manager Error Name Value Definition Incorrect w3Exec, w3SessionId 007 Either both a w3Exec and w3SessionId were specified or neither w3Exec or w3SessionId were specified. Unsupported Feature 008 Feature used is not supported, for example, an unsupported data type. Maximum Message Length Exceeded 009 Overall message length exceeds the maximum message length.
Chapter 6: Administering the FlashCONNECT Socket Server Manager If you elected to have errors logged to a file, it might look something like this: 68 FlashCONNECT Administrator’s Guide
Using the FlashCONNECT Socket Server Manager Understanding Log Information The following example displays an error code line that was logged: 6886 127.0.0.1/127.0.0.1 012501 085127 2916 -1512324104 S ERROR: 00100000003490140000000000000030010150000000000 00290com.pick.br.FCConnectionUnavailableException: From FCJavaServer.call(FCRule): The connection to the FlashCONNECT failed. Possible causes: 1)FCService is not available.
Chapter 6: Administering the FlashCONNECT Socket Server Manager Code Line Description 0010000000349014000000 00000000300101500000000000029 0com.pick.br.FCConnectionUnav ailableException: From FCJavaServer.call(FCRule) Error message sent to mvDesigner. The connection to the FlashCONNECT failed. Possible causes: 1)FCService is not available. OR, 2)D3 Server pool might not start or available, or invalid D3 Server pool name. 3)Invalid session id value request.
Chapter 7 Understanding FlashCONNECT Java Components FlashCONNECT contains Java features that enable it to communicate more efficiently with the Web browser. Java components increase the speed of data transfer by enabling better communication between the Web server and FCService. The Java components include FCServlet, an FCServlet Diagnostic application, and a Java Native Interface (JNI).
Chapter 7: Understanding FlashCONNECT Java Components FCServlet The Java Servlet interface between the Web server and FCService provides important benefits for FlashCONNECT users: • Servlets increase the speed of the data transfer between the Web browser and D3 because the servlet is loaded only one time by the Web server and is shared among users. • Servlets are platform independent and easy to use.
Working with FCServlet Working with FCServlet FCServlet provides an alternative path for the flow of data between the Web server and FCService. The path contains three stages: 1. FCServlet gets the request from the Web browser via the Java Servlet engine and passes the request to the JNI interface. 2. The JNI interface translates the environmental and form variables and passes them to FCService. 3.
Chapter 7: Understanding FlashCONNECT Java Components Testing FCServlet After installing the FlashCONNECT software, but before using FCServlet, perform tests to confirm that the Java Servlet Engine runs properly and is properly configured to run FCServlet. There are two tests to perform: Test 1: Use FCHelloWorld to test the communication between the Web server and the Java Servlet Engine. Test 2: Use FCJNIHelloWorld to test if the Java Servlet Engine works properly with the Java Native Interface codes.
Testing FCServlet The test failed if: • An error message or no message displays. If the test failed, do the following: 1. Confirm that the Web server supports Java servlets. 2. Confirm that the Java Servlet engine is properly installed. 3. Verify that the correct path was used in the URL. 4. Using other steps in the FCServlet Diagnostic application, confirm the Web server is running. For more information, see FCServlet Diagnostic.
Chapter 7: Understanding FlashCONNECT Java Components The test failed if: • An error message or no message displays. If the test failed, do the following: 1. Confirm that the Web server supports JNI servlets. 2. Using other steps in the FCServlet Diagnostic application, confirm that the Web server is running. For more information, see FCServlet Diagnostic.
Using FCServlet Using FCServlet After Test 1 and Test 2 run successfully, run FCServlet to access several D3 applications. To run FCServlet: • Issue a URL in the form: http://webservername/servlet/ com.rdta.bin.FCServlet?w3exec=ApplicationName where webservername Name of the Web server to run, servlet Virtual directory that contains the active servlets. com.rdta.bin.FCServlet Package name of the FCServlet. ApplicationName Name of the FlashCONNECT application.
Chapter 7: Understanding FlashCONNECT Java Components FCServlet Diagnostic The FCServlet Diagnostic tool is a servlet diagnostic application that tests whether a system is capable of running the FlashCONNECT Java Components. Run the FCServlet Diagnostic to ensure that the FlashCONNECT Java Components are set up properly.
FCServlet Diagnostic The FlashCONNECT Socket Server Manager dialog box displays. 2. Click Help. The Help Options dialog box displays. 3. Select the Diagnostic option, then click OK.
Chapter 7: Understanding FlashCONNECT Java Components The Diagnostic Options box displays. 4. Select FCServlet Diagnostic, then click OK. The FCServlet Diagnostic dialog box and the FCServlet Configuration box display. The configuration box provides the parameters needed to run the FCServlet Diagnostic. 5. Enter the appropriate parameters, then click OK to return to the FCServlet Diagnostic dialog box. The FCServlet Diagnostic is ready to test the FlashCONNECT Java components.
FCServlet Diagnostic Testing Once the FCServlet Diagnostic is ready, perform any of the five tests to check the compatibility of the system. NOTE— Tests 1 and 5 can be skipped if only mvDesigner is being used and FCServlet is not being used. • Test 1 verifies that the FCServlet shared library is available on the system. Run this test to confirm that the FlashCONNECT shared library file, which is a part of FlashCONNECT Java Components, is properly installed.
Chapter 7: Understanding FlashCONNECT Java Components Test Number Passed Failed 5 A Java Servlet Engine is installed on the system and available. A Java Servlet Engine is not configured properly to run FlashCONNECT, the Web server is not running, the Web server port number is incorrect, or FlashCONNECT is not running. To test the FlashCONNECT Java components: 1. Select any of the check boxes to run the tests. The results display in the FCServlet Diagnostic dialog box. 2. Click Run Check.
FCServlet Diagnostic Viewing the FCServlet Diagnostic Report After running tests, view the test report that describes the test results. To view the report: 1. Click View Report from the FCServlet Diagnostic dialog box. The FCServlet Diagnostic Report displays. 2. Do one of the following: • Click Save to save the report. Enter the file name for the report, then click OK. • Click Open to view a report previously saved on the system or, click Browse to locate the file, then click OK.
Chapter 7: Understanding FlashCONNECT Java Components To reconfigure setup parameters: Click Reconfigure from the FCServlet Diagnostic dialog box. The FCServlet Diagnostic Configuration box displays. 3. Change any of the parameters, then click OK. Resetting the Test Selection You can clear the FCServlet Diagnostic dialog box and reselect the tests to perform. To clear the FCServlet Diagnostic dialog box and select new tests: 1. Click Reset in the FCServlet Diagnostic dialog box.
Chapter 8 Configuring, Starting and Stopping FlashCONNECT Components These instructions are for both the UNIX and Windows platforms. When both the Web server and the FlashCONNECT service are properly configured and started, start the FlashCONNECT servers.
Chapter 8: Configuring, Starting and Stopping FlashCONNECT Components Turnkey Installation A turnkey installation is one in which FlashCONNECT becomes available when the host system starts. NOTE— A turnkey installation can be created automatically when installing the WWW account by responding yes to the prompt: Do you want USER-COLDSTART and USER-SHUTDOWN to automatically start and stop FlashCONNECT in the accountname account at boot and shutdown time? (Y/N) See the FlashCONNECT 3.5 and mvDesigner 2.
Turnkey Installation The Services dialog box displays. b. To start FlashCONNECT automatically, double-click FlashCONNECT Service. The FlashCONNECT Service dialog box displays. c. Change the Startup Type to Automatic. d. Click OK. e. Click Close in the Services dialog box.
Chapter 8: Configuring, Starting and Stopping FlashCONNECT Components Starting FlashCONNECT in the Foreground Manually starting FlashCONNECT in the foreground from TCL facilitates the debugging process. Follow these instructions to start FlashCONNECT in the foreground. To start FlashCONNECT in the foreground: 1. From TCL, enter the command below: WWW-POOL W3SERVERPOOL where W3SERVERPOOL is the name of the set of FlashCONNECT server pools. 2.
Customizing the Local Environment Customizing the Local Environment An administration utility is included with FlashCONNECT to customize your local environment. To start the administration utility: • Select Start > Programs > Raining Data > FlashCONNECT > Configure from the Start menu. Environment tab When the FlashCONNECT service passes a request to your application, several environment variables are sent with the request.
Chapter 8: Configuring, Starting and Stopping FlashCONNECT Components The Environment tab options are: Option Description Delete Deletes environment variables. Select one or more variable from the list, then click on the Delete button. Add New Adds an environment variable. Type the environment variable name in the space provided. Click the Add New button. OK Saves changes and exits the dialog box. Cancel Quits without saving any unapplied changes.
Customizing the Local Environment The Startup tab options are: Option Description Maximum Servers Supported Specifies the maximum number of concurrent FlashCONNECT connections. Enter the maximum number of connections to allow. Each increment uses 28 bytes of additional shared memory and may be set as high as desired, subject to the limits of your system. The default is 256 (default is 16 on Linux).
Chapter 8: Configuring, Starting and Stopping FlashCONNECT Components FlashCONNECT Service The FlashCONNECT service (FCService) was installed during the installation process. On Windows systems, the service can be started from Services located in the Control Panel. • If the computer was restarted at the end of the installation process, or the FlashCONNECT service was started manually from the Control Panel, the service is ready for operation.
Customizing the Local Environment 4. Set the Startup Type to Automatic or Manual. If you set the Startup Type to Automatic, reboot the machine to start. If you set the Startup Type to Manual, click Start. 5. Set the Log On As: parameter. 6. Click OK, then click Close. Starting FlashCONNECT on D3 To start FlashCONNECT on D3: 1. Log to the www account. : logto www 2. Configure the server pools. See Connecting Database Server Pools for more information. 3. Start the w3Monitor and all server pools.
Chapter 8: Configuring, Starting and Stopping FlashCONNECT Components Stopping FlashCONNECT on D3 To stop FlashCONNECT on D3: 1. Log to the www account. 2. Enter: WWW-MANAGER STOP Manually Starting and Stopping the w3Monitor These instructions are for both the Windows and UNIX platforms. The WWW-MONITOR command is executed in the www account to manually start and stop the w3Monitor as a phantom process.
Chapter 9 Customizing the FlashCONNECT Server and Web Server Instructions for using the FlashCONNECT server and the Web server are discussed. Information provided includes: • Confirming that the D3 FlashCONNECT connections are established to the Web server. • Identifying server problems using WWW-STATUS and w3Lines messages.
Chapter 9: Customizing the FlashCONNECT Server and Web Server Using WWW-STATUS Use WWW-STATUS to confirm that the D3 FlashCONNECT connections are established to the Web server. WWW-STATUS displays the status of one or more FlashCONNECT lines. Both the FlashCONNECT internal status information and the where command information for each line display. If a select list is active, WWW-STATUS uses it to allow viewing of selected subsets of the active lines.
Using WWW-STATUS In mvBase: The information on the first line of each entry is the FlashCONNECT internal status. The information on the second line (or 3rd line in D3) displays the current execution status of processes currently logged on to the system (where command results). The table below describes each element in the first line of WWW-STATUS. Element Description Idx ID number to an internal table index on the Web server. Server Pool Server pool name.
Chapter 9: Customizing the FlashCONNECT Server and Web Server Element Status Description Status of the line. Input: waiting for input. Processing: processing a FlashCONNECT application. Socket: waiting to connect to the Web server. Other: copy the w3Lines item to the screen to see the full text. To see the complete message, enter: ct w3lines See Explanation of WWW-STATUS and w3Lines Status Messages for more information. Time/Date Time and date of the last time the line was used.
Using WWW-STATUS The usual sequence of messages for a typical connection is: 1. w3_SettingSocket (Socket) 2. w3_Input 3. w3_ProcessingRequest (Processing) The last two messages repeat when processing and waiting for requests. Many of these messages display very briefly. Messages displaying for more than a brief period is usually an indication of a problem. Use the information below to identify and resolve any problems. NOTE— Input is the normal message and is displayed for long time periods.
Chapter 9: Customizing the FlashCONNECT Server and Web Server Message Name Message Meaning and Suggestions w3_Can’t Open Socket Unable to open Socket (errno=XXX) An error occurred when using the host operating system. The number shown is the error code returned by the host operating system. See Error Messages and refer to the FlashCONNECT FAQs section of the Raining Data Web site. w3_BadActivation Product must be activated before it can be used FlashCONNECT cannot be activated.
Using WWW-STATUS Message Name Message Meaning and Suggestions w3_SettingSocket Socket FlashCONNECT is attempting to establish a connection with FCService. If this message appears for more than a brief period, ensure that the connection to FCService is correct, that FCService is running, and the D3 and Web server components are compatible. This message appears only when a FlashCONNECT connection is starting.
Chapter 9: Customizing the FlashCONNECT Server and Web Server Configuring the Heartbeat These parameters are set when configuring the FlashCONNECT heartbeat: frequency (Set in the server pool/Web host definition from the database server.) Sets the frequency (in seconds) in which w3Monitor checks this configuration. heartbeat (Set from the database server.
Using WWW-STATUS For UNIX: Edit the flashconnect.conf file. For Windows: Select Start > Programs > Raining Data > FlashCONNECT > Configure from the Start menu. NOTE— The heartbeat is configured from the FlashCONNECT Server Pool Maintenance Web page. For more information, see Configuring, Starting and Stopping FlashCONNECT Components. Customizing WWW-IRUN The FlashCONNECT driver application on the database server consists of the WWW-IRUN and WWW.IRUN2 applications.
Chapter 9: Customizing the FlashCONNECT Server and Web Server Windows Server Administration Web Server Any Web server supported by Windows that supports CGI and/or ISAPI, such as Microsoft Internet Information Server (IIS), Netscape, or Apache, can be used with FlashCONNECT. The following two steps are required and should have been completed as part of the installation procedure. If they were not performed during installation, complete them now to enable FlashCONNECT to run. 1. Copy the fccgi.
Windows Server Administration customized to fit your Web site and client needs. Refer to your Web server documentation for instructions for changing HTTP error messages. You can modify or create a new file that contains graphics or better represents your Web site. You may want to provide content that is more descriptive about the possible actions your users can take after receiving the error message.
Chapter 9: Customizing the FlashCONNECT Server and Web Server The FlashCONNECT Configuration dialog box displays (parameters are specified from the Error handling tab): The RedirectParametersPath parameter (Directory for temporary files in Windows) specifies the path in which to create a text file that contains the name and value pair parameters of the error as well as the W3EXCEPTIONERROR and W3EXCEPTIONTEXT variables (generated by the error).
Windows Server Administration where filename is a randomly generated 10 character string (for example, jaofvhznwx). The random generation ensures that each file name is unique. NOTE— • An automatically generated question mark (?) separates the error path and the appended text file. • In this example, the path specified in the NoServerException actually calls a PERL program. This allows you to create a custom program (PERL or other) for handling the data passed.
Chapter 9: Customizing the FlashCONNECT Server and Web Server Parameter (UNIX) Parameter (Windows) Description UncategorizedException= Uncategorized Specifies the redirect URL for uncategorized exception errors. NOTE— If the database detects an error, it calls the w3processerror BASIC program. The source code for this program may be customized and is located in the wbp file. Example #!/usr/bin/perl # # There has been a FlashCONNECT exception redirected here.
Chapter 10 Administering Log and JOBS Files We provide information about administering log files for tracking daily activities and for FlashCONNECT errors. Also included is information for clearing the JOBS file.
Chapter 10: Administering Log and JOBS Files Administering Log Files The FlashCONNECT W3LOGS CONTROL File Maintenance Menu allows creation, deletion, or modification of w3Logs.Control entries. A w3Logs.Control entry controls an associated w3Logs data file. Adding or deleting a w3Logs.Control entry does not create or delete the associated w3Logs data file. Deleting w3Logs data files is done manually. w3Logs data files are created automatically when an entry is written to it.
Administering Log Files Entries are placed in the FlashCONNECT log files by applications using the w3Log subroutine. FlashCONNECT uses several log files. They are: w3Logs,FlashCONNECT Tracks daily activity such as starting FlashCONNECT, errors while starting FlashCONNECT, starting and stopping applications, and log on errors. w3Logs,errors Used when the w3Log subroutine needs to log an error. w3Logs,Dump A diagnostics log file. w3Logs,w3Rotator Records the use of w3Rotator.
Chapter 10: Administering Log and JOBS Files Administering the JOBS File FlashCONNECT phantoms create entries in the JOBS file. A switch is available that toggles whether the entries remain or are automatically cleared from the JOBS file when the phantom process ends. The default setting is to leave the entries intact. To set the JOBS file switch: 1. Log to the www account from the D3 or mvBase database (if it is not the current account). 2.
Administering the JOBS File The FlashCONNECT File Maintenance Menu displays. 4. Select option 6 (Maintain JOBS file). NOTE— Option 6 (Maintain JOBS file) is not available from the corresponding FlashCONNECT File Maintenance Menu Web page. The Maintain JOBS File utility displays. 5. Verify the current setting. For example, the screen above indicates that phantoms do not automatically delete their entries when the process ends. 6. Do one of the following: • Enter 1 to toggle the current setting.
Chapter 10: Administering Log and JOBS Files 114 FlashCONNECT Administrator’s Guide
Chapter 11 Using Character Translation Character translations allow the D3 data structure to handle binary or non-ANSI data. The values, OxFF, OxFE, OxFD, and OxFC are reserved and cannot be used in fields passed into FlashCONNECT. In order to handle these values (non-ANSI data), character translation may be performed on inbound and outbound data.
Chapter 11: Using Character Translation Performing Character Translation 1 to 1 Translation Translation Table FF>0F FF<0F FF=0F The following table explains the translation pair and its description. Translation Pair Description FF>0F Translates FF to 0F for inbound messages. FF<0F Translates 0F to FF for outbound messages. FF=0F Translates FF to 0F for inbound messages and 0F to FF for outbound messages. This translation pair is the same as using both FF>0F and FF<0F pairs together.
Performing Character Translation FF>0F Translates FF to 1B0F for inbound messages. FF<0F Translates 1B0F to FF for outbound messages. FF=0F Translates FF to 1B0F for inbound messages and 1B0F to FF for outbound messages. This translation pair is the same as using both FF>0F and FF<0F pairs together. 00>30 Not allowed. You cannot translate a binary zero.
Chapter 11: Using Character Translation Each translation file contains a translation map that is used by FCService. This feature operates in two modes: 1 to 1 Translates one byte to one other byte. 1 to 2 Translates one byte to an escape byte followed by another byte. Each line of the map file contains one character translation hex pair separated by a direction code. These pairs must start in column 1 and anything after the translation pair or escape character definition is taken to be a comment.
Performing Character Translation For example: C:\Program Files\FlashCONNECT\FCXlate.txt. 5. Click Add. 6. Repeat steps 3-5 to add additional server pools. 7. (Optional.) Click Apply to save this information to the registry without closing this dialog box. 8. Click OK. NOTE— Use the Select button to select an existing server pool entry to edit. This also this allows you to add another server pool using the same translation file.
Chapter 11: Using Character Translation Character Translation Error Messages If you encounter problems when processing translation definitions, the error messages are logged to the flashconnect.log file if using UNIX or the Event log if using Windows. The following table describes the character translation error messages: 120 Error Message Description Could not open translation map file . Displays when the file containing the translation definition cannot be opened.
Appendix A FlashCONNECT SOAP Access This topic discusses deploying FlashCONNECT for SOAP (Simple Object Access Protocol) access.
Appendix A: FlashCONNECT SOAP Access Deploying the FlashCONNECT SOAP Interface The FlashCONNECT SOAP interface enables client access to the database via a SOAP server. The procedure involves the client accessing a servlet server (for example, Tomcat). This servlet runs the SOAP server (for example, Axis) that connects to FlashCONNECT. These instructions are SOAP server dependent.
Deploying the FlashCONNECT SOAP Interface Deploying the execute Interface Methods The execute interface methods (located in the com/rdta/fc/facade/ flashconnect.class contained within fcss.jar file) must be deployed. This requires: • Preparing for Deployment • Creating and Running a Deployment wsdd7 Preparing for Deployment Axis is a servlet that is run by a servlet server (for example, jrun or Apache Tomcat).
Appendix A: FlashCONNECT SOAP Access To create and run the deployment wsdd: 1. Insert the wsdd code. For example: 2. Run the deployment. For example: java org.apache.axis.client.
Deploying the FlashCONNECT SOAP Interface PAGE 136Appendix A: FlashCONNECT SOAP Access
Deploying the FlashCONNECT SOAP Interface PAGE 138Appendix A: FlashCONNECT SOAP Access 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 016 017 SUBROUTINE GETQUOTE INCLUDE WBP W3INCLUDE * * Sending back a non-numeric for error cases causes * an exception in applications looking explicitly for * numerics. That exception should be handled there. * OPEN "TESTDATA" TO FV_TESTDATA THEN CALL W3GETVAL(SYMBOL,'symbol') READ ITEM FROM FV_TESTDATA,SYMBOL ELSE ITEM = "That symbol does not exist in the TESTDATA file.
Deploying the FlashCONNECT SOAP Interface 2. Run the sample program. For example: java -classpath %CLASSPATH% samples/FCStock/fc getquote ibm NOTE— The getquote database business rule is a parameter. The example below should also execute properly, and display html text: java -classpath %CLASSPATH% samples/FCStock/fc boo ibm The second parameter (ibm) is required by the java program, but is ignored by boo.
Appendix A: FlashCONNECT SOAP Access * * 4. The names "Axis" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called * "Apache", nor may "Apache" appear in their name, without prior * written permission of the Apache Software Foundation.
Deploying the FlashCONNECT SOAP Interface public String serverpool = null; public String[] parameternames = null; public String[] parametervalues = null; // helper function; does all the real work public String run (String args[]) throws Exception { Options opts = new Options( args ); args = opts.getRemainingArgs(); if ( args == null ) { System.err.println( "Usage: fc getquote " ); System.
Appendix A: FlashCONNECT SOAP Access Object ret = call.invoke( new Object[] { username, password, rulename, serverpool, parameternames, parametervalues} ); if ( !(ret instance of String)) { System.out.println("Received problem response from server: "+ret); throw new AxisFault("", (String)ret, null, null); } return (String)ret; } public static void main(String args[]) { try { fc fcInstance = new fc(); String val = fcInstance.run(args); // args array gets side-effected System.out.
Deploying the FlashCONNECT SOAP Interface * rights reserved. * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the * following conditions are met: * * 1.Redistributions of source code must retain the above * copyright notice, this list of conditions and the following * disclaimer. * * 2.
Appendix A: FlashCONNECT SOAP Access * For more information on the Apache Software Foundation, * please see . */ * This is a copy of axis/samples/stock/GetQuote.java modified * to use FlashCONNECT. */ package samples.FCStock ; import import import import import org.apache.axis.AxisFault; org.apache.axis.client.Call; org.apache.axis.client.Service; org.apache.axis.encoding.XMLType; org.apache.axis.utils.Options; import javax.xml.namespace.QName; import javax.xml.rpc.
Deploying the FlashCONNECT SOAP Interface String user = opts.getUser(); String passwd = opts.getPassword(); */ /* done by wsdl above opts.setDefaultURL("http://:8080/axis/ servlet/AxisServlet"); URL url = new URL(opts.getURL()); call.setTargetEndpointAddress( url ); call.setOperationName( new QName("flashconnect", "run") ); call.addParameter( "username", XMLType.XSD_STRING, ParameterMode.IN ); call.addParameter( "password", XMLType.XSD_STRING, ParameterMode.IN ); call.
Appendix A: FlashCONNECT SOAP Access String val = fcInstance.run(args); // args array gets side-effected System.out.println( val); } catch( Exception e ) { e.
Appendix B Debugging and Diagnosing FlashCONNECT Configuration Strategies, diagnostics and instructions to help troubleshoot your Windows or UNIX installation are included in these topics: • Diagnosing FlashCONNECT Configuration Problems (D3 Only) • Running the Loop-Back Test (D3 Only) • Roving Tandem Debugger • Application Debug Strategies • Determining if the Application is in the Debugger • Using the FlashCONNECT Server Debug Program • Debugging Server Pools • Debugging w3Monitor • Rec
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Diagnosing FlashCONNECT Configuration Problems (D3 Only) The checkup program examines the overall FlashCONNECT configuration and checks for potential and fatal problems. The checkup program does not change the D3 or FlashCONNECT configuration. There are two ways to run the diagnostic: • From TCL type: run bp checkup • From the TCL FlashCONNECT Main Menu, select 7. Diagnostics, then select 1. Run the Online Diagnostics.
Diagnosing FlashCONNECT Configuration Problems (D3 Only) The report displays fatal errors which indicate that the tested feature will not work: • Yes indicates the tested feature should work. • No indicates the tested feature should partially work. Starting Diagnostic Checking if FlashCONNECT is activated? Yes Are there user licenses available? Yes ... 50 available Are there phantom processes available? Yes ... 26 available Verifying that the database version is supported Yes ...
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Message Example Values Starting The program is starting the evaluation. Checking if FlashCONNECT is activated. Yes Are there user licenses available? Yes ... 5008 available Are there phantom processes available? Yes ... 21 available Can this version of D3 run FC? Yes … Can FlashCONNECT connect to the configured hosts? • FC Host Port • 172.16.250.218 1505 Yes • host.rainingdata.
Diagnosing FlashCONNECT Configuration Problems (D3 Only) Message Example Values Comments Are there enough available phantoms to run the minimum number of connections? Yes … requested Number of minimum connections for each server pool/host/name combination is totaled and compared to the number of currently available phantom processes. If there are sufficient available phantom processes to run the minimum number of connections, Yes is displayed.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Message Example Values Comments Are there enough available licenses to run the maximum number of connections? Yes … requested Number of maximum connections for each server pool/host/name combination is totaled and compared to the number of currently available D3 user licenses. If there are sufficient available D3 user licenses to run the maximum number of connections, Yes is displayed.
Running the Loop-Back Test (D3 Only) Running the Loop-Back Test (D3 Only) This diagnostic test periodically runs the FlashCONNECT boo application and records in the w3logs,loopback file the state of the application (success or failure), when the test started, and whenever the test switches between success and failure. In addition, the results of each test are displayed on the console. This test can be used to determine when a site goes down or to periodically poll a site.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Roving Tandem Debugger A characteristic of persistent applications is that they can run on any phantom port running FlashCONNECT. This is not problematic for small development systems that use only one active FlashCONNECT connection. However, on larger multiuser systems, determining the port on which the application being debugged is running can be a repetitive, time-consuming task.
Roving Tandem Debugger 13 call w3HtmlFooter("","") 14 15 call w3Tandem("test", "Stop") 16 return If you are using the command line, type this command at the prompt: WWW-TANDEM TEST For more information about the w3Tandem API call and the WWW-TANDEM command, see the FlashCONNECT Programmer’s Online Reference.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Application Debug Strategies Static Applications Static FlashCONNECT applications are normal database applications. Employ standard debugging procedures. Dynamic Applications The following methods can be used to debug dynamic applications. Using the w3Logs File Within the application, use the w3Log subroutine to log important information to the w3Logs file. Step-by-Step Debugging 1.
Application Debug Strategies Determining if the Application is in the Debugger For D3: Use the WWW-STATUS command to determine if the application is in the debugger. There are two indicators that you are in the debugger: • If the stat column displays a D. • If the second line displays a mode name starting with any of the following: PX_DB, PX.DB, DB or DB_GETBUF.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Option Description FCIsUp FlashCONNECT is running. FCServicePID Internal use. Semaphores per ID Internal use. (UNIX only) * Configured using the FlashCONNECT Administration program on Windows Web servers or editing FCService.conf on UNIX Web servers. -kpool where pool is the server pool name. Terminates all connections in the specified server pool. However, if the database side is still running, it will reconnect.
Application Debug Strategies Option -tr Description TimeOut Number of seconds until the connection times out. Pipe Name Name of pipe used by the ISAPI or CGI connector. Host Name Value of the w3ServerPool used to establish this connection. Cookie Value of the w3SessionId for this session. xidx Index for the translation module. Multiple translation modules may be specified in the configuration file. They are stored starting with an index of 0.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Option Description 2 Sema Semaphore number. Also the index in w3SessionId. 3 TimeOut Number of seconds until the connection times out. 4 KillInfo Windows: socket UNIX: Process ID -uNN 5 Pipe Name Name of the pipe used by the ISAPI or CGI connector. 6 Host Name Value of the w3ServerPool used to establish this connection. 7 Cookie Value of the w3SessionId for this session. Unlocks table entry NN. For development use only.
Application Debug Strategies 3. Use the tandem command to connect to and debug the FlashCONNECT application. 4. Tandem to the port before running the application, so when the connection is made, the application is already being observed. Debugging w3Monitor When w3Monitor detects a FlashCONNECT port in either the system or Pick BASIC debugger, it removes the connection automatically unless this feature is overridden by enabling debugging.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration Enabling and Disabling the w3Debugging Tool There are three methods that can be used to enable or disable the w3Debugging tool. Although each method has a slightly different scope, they can be used together. 1. Within the URL: http://yourwebhost.rainingdata.com/cgi-bin/ fccgi.exe?w3exec=boo&w3Debug=1 Debugging starts when this URL is received. Debugging stops when reset or when the application ends by returning to WWW-IRUN. 2.
Application Debug Strategies Testing FCService on a Specified Machine and Port Use this procedure to verify that the FCService installed is the correct version, running properly, and configured to run on the specified port. To test FCService: 1. Telnet to the machine and port to test. 2. Press Enter one or more times. One of the following occurs: • The message below displays: FlashCONNECT invalid message where version is the FCService version running.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration For example: • FCSocketServer -D12 Logs FCSocketServer miscellaneous and input/output diagnostic messages. • FCService -D0 Logs FCService constructor and deconstructor diagnostic messages. • FCService -D012 Logs FCService constructor and deconstructor, miscellaneous, and input/output diagnostic messages. All messages are logged to the FCdebug000n.txt file, where n is either 0 or 1.
Application Debug Strategies Examining CGI and Form Variables To examine the cgi and form variables being passed between the browser, Web server and FlashCONNECT, redirect the URL that submits the form from your application to a URL within the cgidisplay application provided with FlashCONNECT. For example: • Change this URL that submits the form from your application:
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration The number in the lower left of the window (in this case 2) is the most recent Win32 error. Possible solutions are: Problem Solution The FCService is not running. Use the Services program from the Control Panel to determine if the FlashCONNECT service is running. Start it if it is not running. The FCService and FCConnector applications are running as different users.
Determining Release Levels Determining Release Levels Use these methods to determine the release level of the FCService, fccgi.exe, and the D3 components. To determine the release level of FCService or fccgi.exe: 1. Go to the shell prompt. 2. To see the version for: • FCService, enter: FCService -V • FCcgi, enter: fccgi.exe -V To determine the release level of the D3 component: 1. Load the FlashCONNECT Main Menu by entering M from TCL in the www account. 2. Select the Diagnostic menu. 3.
Appendix B: Debugging and Diagnosing FlashCONNECT Configuration 158 FlashCONNECT Administrator’s Guide
Appendix C Troubleshooting for UNIX Platforms Strategies for troubleshooting problems associated with UNIX platforms are discussed. For topics not covered here, refer to the FlashCONNECT Forum listed on the Raining Data Web site.
Appendix C: Troubleshooting for UNIX Platforms Troubleshooting for the UNIX Platform Diagnostics Assuming the Web server and browser are operating properly and are properly configured, the following processes can be used to diagnose problems while using FlashCONNECT. If a problem occurs, please perform each step in the diagnostic process in order to isolate the problem (see diagram below). Test details are found on the following pages.
Troubleshooting for the UNIX Platform Test 1. Verify the browser can access a non-FlashCONNECT HTML page. Setup: • FlashCONNECT does not have to be installed. • The Web server must be running. • The browser must be able to connect to the Web server. Process: Enter the URL to a Web page on your Web site. Success: The expected Web page displays. Failure: Web server or browser may be misconfigured, not running, or the network connection may be down.
Appendix C: Troubleshooting for UNIX Platforms Test 3. Verify the Web server can run a script in the cgi-bin directory, using sh. NOTE— This diagnostic tests the ability for the Web server to execute shell scripts. Since FlashCONNECT does not use shell scripts, it is possible for FlashCONNECT to work even if this diagnostic fails. Setup: • FlashCONNECT must be installed on your Web server. • FlashCONNECT need not be installed on the database server.
Troubleshooting for the UNIX Platform Test 4. Verify the Web server can run a script in the cgi-bin directory, using PERL. NOTE— This diagnostic tests the ability for the Web server to execute PERL scripts. Since FlashCONNECT does not use PERL scripts, it is possible for FlashCONNECT to work even if this diagnostic fails. Setup: • FlashCONNECT must be installed on your Web server. • FlashCONNECT need not be installed on the database server.
Appendix C: Troubleshooting for UNIX Platforms Test 5. Verify the Web server is using fccgi.exe. Setup: • FlashCONNECT must be installed on your Web server. • FlashCONNECT need not be installed on your database server. • Your Web server must be running. Process: Use a browser to access the fccgi.exe program.The URL will look something like: http://yourwebhost/path/fccgi.exe For example: http://mywebhost.rainingdata.com/cgi-bin/fccgi.exe Success: This message displays: " is an illegal command.
Troubleshooting for the UNIX Platform Success: Several lines contain the entire word FCService. Failure: No lines contain the word FCService. Follow-up: If no lines display, then verify the FCService file is executable and verify the location of the flashconnect.conf file. Make sure the process used to start the FCService is correct. Test 7. Confirm the fccgi.exe program can access the FCService program. Setup: FCService must be running on the Web server.
Appendix C: Troubleshooting for UNIX Platforms Success: Status ESTABLISHED displays on line one for each connection. The status LISTEN displays on the second line, if it exists. Failure: There is not an entry with the status ESTABLISHED for each connection to database. Follow-up: • Verify that FCService is running. • Verify FlashCONNECT was started on the database server. • Shut down and restart both the Web and database components of FlashCONNECT. b.
Troubleshooting for the UNIX Platform Test 9. Check that the FCService can access the database server. Setup: • FlashCONNECT must be installed and running on the Web server. • FlashCONNECT must be installed and running on the database server. • Copy the fccgi.to.d3.test.sh script to the Web server's cgi-bin directory. As needed, modify the script to correct the location of the fccgi.exe, grep, and echo commands.
Appendix C: Troubleshooting for UNIX Platforms 168 FlashCONNECT Administrator’s Guide
Appendix D Troubleshooting for Windows Platforms Strategies for troubleshooting problems associated with Windows platforms and provides a description of Event Log error messages are discussed. For topics not covered here, refer to the FlashCONNECT Forum listed on the Raining Data Web site.
Appendix D: Troubleshooting for Windows Platforms Troubleshooting for Windows This section documents: • Diagnostic steps to isolate problems. • Diagnostic messages shown in the browser. • Event log entries written by FlashCONNECT. Diagnostics Assuming the Web server and browser are operating properly and are properly configured, the following processes can be used to diagnose problems while using FlashCONNECT.
Troubleshooting for Windows Test 1. Verify the browser can access a nonFlashCONNECT HTML page. Setup: • FlashCONNECT does not have to be installed. • The Web server must be running. • The browser must be able to connect to the Web server. Process: Enter the URL to a Web page on your Web site. Success: Expected Web page displays. Failure: Web server or browser may be misconfigured, not running, or the network connection may be down. Follow-up: This problem does not involve FlashCONNECT.
Appendix D: Troubleshooting for Windows Platforms Test 3. Verify the Web server can run a script in the cgi-bin directory. Setup: • FlashCONNECT must be installed on the Web server. • FlashCONNECT need not be installed on the database server. • FlashCONNECT does not have to be running on the Web server nor D3 server. • Copy the program helloworld.exe from the WebContent directory to the Web server’s cgi-bin directory where fccgi.exe is located. Process: Use a browser to access the helloworld.
Troubleshooting for Windows Test 4. Verify the Web server can run a script in the cgi-bin directory, using PERL. NOTE—This diagnostic tests the ability for the Web server to execute PERL scripts. Since FlashCONNECT does not use PERL scripts, it is possible for FlashCONNECT to work even if this diagnostic fails. Setup: • FlashCONNECT must be installed on your Web server. • FlashCONNECT need not be installed on the database server. • The PERL scripting language must be installed on the Web server.
Appendix D: Troubleshooting for Windows Platforms Test 5. Verify the Web server is using fccgi.exe. Setup: • FlashCONNECT must be installed on your Web server. • FlashCONNECT need not be installed on your database server. • Your Web server must be running. Process: Use a browser to access the fccgi.exe program. The URL will look something like: http://yourwebhost/path/fccgi.exe For example: http://mywebhost.rainingdata.com/cgi-bin/fccgi.
Troubleshooting for Windows Test 6. Verify that the FCService is running. Setup: FlashCONNECT must be installed on the Web server. Process: From the command prompt, enter these commands: cd path fcdebug -h where: path is the location where FlashCONNECT is installed. Success: FlashCONNECT header information displays. A description of the header information is located in Using the FlashCONNECT Server Debug Program. Failure: FlashCONNECT not running message displays.
Appendix D: Troubleshooting for Windows Platforms Test 8. Verify that FCService and the database server are connecting with each other. Use either of these two methods as a valid diagnostic. a. Method One Setup: • FlashCONNECT must be installed and running on the Web server. • FlashCONNECT must be installed and running on the database server.
Troubleshooting for Windows Follow-up: • Use the Task Manager to verify there is only one copy of FCService running. • Verify FlashCONNECT was started on the database server. • Shut down and restart both the Web and database components of FlashCONNECT. Test 9. Check that the fccgi.exe program can access the database server. Setup: • FlashCONNECT must be installed and running on the Web server. • FlashCONNECT must be installed and running on the database server.
Appendix D: Troubleshooting for Windows Platforms FlashCONNECT Event Log Entries FCService writes messages to the Windows Event Log. Some messages are informative and others may indicate that an error occurred. This section describes each message written to the Event Log by FCService. MSG_STARTED Type Informative. Meaning FlashCONNECT Service started successfully. When Displays when the FlashCONNECT service starts. Action None. MSG_STOPPED Type Informative.
Troubleshooting for Windows Meaning Unable to attach to the shared memory segment. When An attempt was made to use FCService before it was running. Action Verify that FCService is running. MSG_LOSTCOOKIES Type Warning. Meaning FCService lost a cookie. When A user returns to a form that has already timed out. Action If this message is received often, check the timeout values in your application. They may be too short. MSG_SPIN Type Warning. Meaning FlashCONNECT Connector (FCCGI.
Appendix D: Troubleshooting for Windows Platforms 180 FlashCONNECT Administrator’s Guide
Appendix E MSG_Exception Messages We describe MSG_Exception error messages. For topics not covered here, refer to the FlashCONNECT Forum listed on the Raining Data Web site.
Appendix E: MSG_Exception Messages MSG_Exception: Event Handler Messages FlashCONNECT provides the MSG_Exception messages that display in either the Windows Event Handler or in the UNIX Log file. The following describes the different message types, their meaning, the severity and what action to take. There are two types of severity: Page will fail Processing of the submitted page will fail. FlashCONNECT can continue processing valid requests. FCService will fail FCService will stop.
MSG_Exception: Event Handler Messages 400, ERROR: Unknown method Meaning: Method must be specified as either GET or POST. The form being submitted was not submitted as a POST or GET. Severity: Page will fail. Action: Correct the form being submitted. 400, pecb, ERROR: ReadClient failed Meaning: FCisapi failure processing very large input value. Severity: Page will fail. Action: Internal error. Contact Raining Data Customer Support.
Appendix E: MSG_Exception Messages accept() failed, errorcode Meaning: FCService encountered an invalid socket while attempting to accept a new connection. Severity: Page will fail, FCService may become unstable. Action: Check errorcode and resolve the underlying problem. bind() failed Meaning: Unable to bind a socket to an address. Severity: FCService will fail. Action: Contact Raining Data Customer Support. bind(): only AF_INET supported Meaning: The bind failed.
MSG_Exception: Event Handler Messages EnvVar() ERROR_MORE_DATA Meaning: There was a problem getting the server variables. Severity: Page will not be returned. Action: Check the Web server configuration. FCisapi (Windows) only. Failed to create semaphore set, errorcode Meaning: CreateSemaphore returned a null pointer. Severity: Page will fail. FCService will not process pages. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages FCisapi.dll: Redirect string too long, FCCBLocSize Meaning: Buffer overrun in FCisapi (Windows) only. Severity: Page will fail. Action: Verify expected size of returned page. FCServiceStore::D3SeverNew() s.consume Meaning: Unable to get a semaphore for a new worker thread. Severity: Page will fail. FCService will not process pages. Action: Verify that a process can have as many threads as are being started.
MSG_Exception: Event Handler Messages Semaphore get-value failed, errorcode Meaning: Bad status returned while attempting to get the value of a semaphore. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. Semaphore production failed, errorcode Meaning: Unable to produce the required semaphore count. Severity: Page will fail. FCService will not process pages. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages w3Config::create() Unable to create db, errorcode Meaning: Failure to open or create the configuration database (registry problems under Windows). Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. Verify presence and permissions of flashconnect.conf (UNIX) or registry entries (Windows). w3Config::create() Use an unopened object Meaning: Configuration Internal error. Configuration database appears to already be open.
MSG_Exception: Event Handler Messages w3Config::open() Unable to open db, errorcode Meaning: Unable to open the configuration file under UNIX. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. Check permissions on the configuration file. w3Config::open() Unable to open key, errorcode Meaning: Unable to open a key value in the registry. Windows only. Severity: FCService will fail. Action: Check errorcode. Ensure FlashCONNECT is properly installed.
Appendix E: MSG_Exception Messages w3Connection::OnClose() Override this function in your derived class. Meaning: Internal error. Severity: Internal compiler error. Action: Contact Raining Data Customer Support. w3Connection::OnConnect() Override this function in your derived class. Meaning: Internal error. Severity: Internal compiler error. Action: Contact Raining Data Customer Support. w3Connection::OnRead() Override this function in your derived class. Meaning: Internal error.
MSG_Exception: Event Handler Messages w3ErrLog::ActuallyOpen() RegisterEventSource() failed, errorcode Meaning: Failure opening the error log. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3Pipe::FinishAccept(): accept(), errorcode Meaning: Unable to finish the accept on the pipe socket. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages w3Pipe::make( const char *n): listen() ,errorcode Meaning: Failure to listen while making a socket for a named pipe. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3Pipe::make( const char *n): malloc() Meaning: Out of memory for a security descriptor while making a named pipe. Severity: FCService will fail. Action: Check memory usage.
MSG_Exception: Event Handler Messages w3Pipe::StartConnect(): connect(), errorcode Meaning: Failure during socket connection under UNIX. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3Pipe::StartConnect(): CreateEvent() Meaning: Failure to create an event during socket connection start-up under Windows. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages w3Pipe::StartRead() Read already in progress Meaning: Internal error trying to read while in the middle of a read. Severity: FCService will fail. Action: Contact Raining Data Customer Support. w3Pipe::StartRead() Unexpected error, errorcode Meaning: Unexpected status from ReadFile. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3Pipe::StartWrite() buf==NULL Meaning: Internal error trying to write a null buffer.
MSG_Exception: Event Handler Messages w3Selector::insert() out of memory Meaning: Out of memory while trying to insert a w3connection. Severity: FCService will fail. Action: Check memory availability. w3Selector::run() select() unknown error, errorcode Meaning: Unexpected error returned from select while looping of selector. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages w3Semaphore::consume() - semid <0 Meaning: Trying to consume an illegal semaphore ID. UNIX only. Severity: FCService will fail. Action: Contact Raining Data Customer Support. w3Semaphore::consume() - semnum <0 Meaning: Trying to consume an illegal semaphore number. UNIX only. Severity: FCService will fail. Action: Contact Raining Data Customer Support. w3Semaphore::consume() - timeout <0 Meaning: Invalid timeout while trying to consume a semaphore. UNIX only.
MSG_Exception: Event Handler Messages w3Semaphore::create(): malloc() Meaning: Out of memory while trying to build a new semaphore. Windows only. Severity: FCService will fail. Action: Check memory usage. w3Semaphore::create(): SetSecurityDescriptorDacl(), errorcode Meaning: Failure of SetSecurityDescriptorDacl while trying to build a new semaphore. Windows only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages w3Semaphore::value() - semnum <0) Meaning: Bad semaphore number while trying to return the value of a semaphore. UNIX only. Severity: FCService will fail. Action: Contact Raining Data Customer Support. w3Semaphore::value() semctl() failed, errorcode Meaning: Failure of semctl while trying to return the value of a semaphore. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
MSG_Exception: Event Handler Messages w3SharedMemory::create() CreateFileMapping() (exists), errorcode Meaning: Shared memory segment already exists. Windows only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. Verify only one copy of FCService is running. w3SharedMemory::create() CreateFileMapping(), errorcode Meaning: Failure to create the shared memory segment. Windows only. Severity: FCService will fail.
Appendix E: MSG_Exception Messages w3SharedMemory::Create(): InitializeSecurityDescriptor(), errorcode Meaning: Problems setting up security descriptor for the shared memory. Windows only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3SharedMemory::Create(): malloc() Meaning: Out of memory while creating shared memory segment. Severity: FCService will fail. Action: Check system resources.
MSG_Exception: Event Handler Messages w3SharedMemory::open() shmat(), errorcode Meaning: Failure to map the shared memory segment. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3SharedMemory::open() shmctl(), errorcode Meaning: Failure to get the size of the shared memory segment. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
Appendix E: MSG_Exception Messages w3Socket::select() CreateEvent(), errorcode Meaning: Failure trying to set up a socket for a selector object. Windows only. Severity: FCService will fail. Action: Check errorcode. w3Socket::select() WSAEventSelect(), errorcode Meaning: Failure trying to attach an event to a socket for a selector object. Windows only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem.
MSG_Exception: Event Handler Messages w3Socket::StartWrite() buf==NULL Meaning: Internal error. Trying to write a null buffer. Severity: FCService will fail. Action: Contact Raining Data Customer Support. w3Socket::StartWrite() bufsz<1 Meaning: Internal error. Trying to write a buffer of negative size. Severity: FCService will fail. Action: Contact Raining Data Customer Support. w3Socket::StartWrite() write already in progress Meaning: Internal error.
Appendix E: MSG_Exception Messages w3Thread::w3Thread(): fork(), errorcode Meaning: Failure to start the new thread. UNIX only. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. w3Thread::wait(), errorcode Meaning: Failure to wait on a thread. Severity: FCService will fail. Action: Check errorcode and resolve underlying problem. Winsock version 2.0 required Meaning: Failure while trying to init with WSAStartup under Windows. Severity: FCService will fail.
Appendix F Error Messages We define common error messages that you might encounter. For topics not covered here, refer to the FlashCONNECT Forum listed on the Raining Data Web site.
Appendix F: Error Messages UNIX Platform Error Messages Server Error If accessing a dynamic application, such as the w3Admin, and the browser reports a Server Error, the FlashCONNECT servers have probably not been set up correctly. See the documentation for WWW-STATUS, WWW-START and WWW-STOP. Unknown line in configuration file: xxxx When the FCService starts, it reads the flashconnect.conf file. At this time, if an unexpected line is found, the above message is printed.
UNIX Platform Error Messages This URL example shows the correction: http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3exec=app&w3ClosingPage=!url This message indicates an application setup error and not a run-time error, and thus should not be visible to the user during normal operations. It is not kept in the system messages file. Socket message • Verify that the Web server and the database component are both running compatible versions of FlashCONNECT.
Appendix F: Error Messages Windows Platform Error Messages Error 1067 If starting the FlashCONNECT server on the Web server host produces this error, shut down and restart the server. Unable to attach to shared memory segment. Please refer to the diagnostic message Unable to connect to FCService in Diagnostic Messages Displayed On the Browser. Failed to open semaphore There is a version mismatch between fccgi.exe and FCService. The versions must match.
Windows Platform Error Messages This URL shows the correction: http://w3lib.rainingdata.com/cgi-bin/fccgi.exe?w3exec=app&w3ClosingPage=!url This message indicates an application setup error and not a run-time error, and thus should not be visible to the user during normal operations. It is not kept in the system messages file. ERROR - Invalid or stale cookie(000) This message displays to the user when a previously established connection is no longer valid.
Appendix F: Error Messages 210 FlashCONNECT Administrator’s Guide
Appendix G Customer Service Raining Data Customer Service representatives are available to provide assistance. For current information, please refer to the Raining Data Web site at: http://www.rainingdata.com/support/cservice/customer.
Customer Service Contacting Customer Service Refer to the topics below for more information. Providing Required System Information When you contact any of our offices for support, please have the System ID available. This number is located on the back of the product CD package. Receiving Extended Support Services Extended support services are available, preferably with advance notice. Extended hours are those hours outside our standard business hours, which includes holiday closures.
Index Symbols /etc/inittab 86, 92 ? FCdebug command 147 [ ] brackets v { } braces v | pipe sign v | vertical line v |-V FCDebug command 150 A ABS base WWW-STATUS 98 adding FlashCONNECT Socket servers 62 ADI 43 administering log files 110 administration reports 49 completed sessions 51 concurrent users 50 contacts 52 line status 55 redirect 53 rotating content use 54 usage 52 administration utility environment tab 89 startup tab 90 Windows 89 administrative tasks 26 Anonymous applications 37 Apache Web serv
Index w3ServerPool 117 w3SessionId 117 Character Translation component enabling 117 Checkup Program D3 version 140 diagnosing FlashCONNECT problems 138 FC Host port 140 FlashCONNECT activation 140 licenses 141 licenses available 140 phantom processes available 140 phantoms 141 valid host names 142 clearing phantom entries 112 Closing Page Sent error socket server 67 completed sessions report 51 components Character Translation 117 configuring 85 Java 71 starting 85 stopping 85 concurrent users report 50 co
Index PERL scripts 173 verify browser access 171 verify browser access to static Web pages 171 Web server scripts running in cgi-bin directory 172 diagnostics messages displayed on browser 155 UNIX 160 Windows platform 170 directories cgi-bin 22 Inetpub 22 scripts 22 virtual 22 w3library 22 WebContent 22 directory virtual 10 dm users file 32 document conventions 4 drivers program 103 WWW-IRUN 103 drivers, WWW-IRUN 20 dynamic application 10, 13, 19, 27 adding users and groups 35 authentication process 27 de
Index reconfiguring diagnostic parameters 83 running diagnostics from FlashCONNECT Socket Server 78 setting diagnostic parameters 78 testing 74, 81 viewing application information 84 FCServlet diagnostic 71 fcss.
Index socket server 64 ISAPI 8 ISAPI interface web server 104 italic font style iv J Java components 10, 71 testing with FCServlet diagnostic 82 Java Native Interface 71 overview 72 Java Runtime Environment 10 Java Servlet 8 Java Servlet Engine 10 Java Servlet engine 72 Java servlets 10 Java Virtual Machine 58 Javascript 9 JNI Java Native Interface 71 JNI interface 72 JOBS file 112 K kill client 64 kpool FCDebug command 148 L letters representing numbers v Line WWW-STATUS 98 line status report 55 load b
Index No Connections error socket server 66 No Response error socket server 66 No Such Application error socket server 66 non-ANSI data 115 NT See Windows P parameter FCXlate 117 password maintenance pages 30 PCB FID WWW-STATUS 98 PERL 173 PERL scripts executing 163 persistent connections item locks 13 peripheral devices 13 record locks 13 persistent data BASIC application 13 Common application 13 dynamic application 13 resources 13 phantom entries 112 phantom process tandem 146 PIB Stat WWW-STATUS 98 Pic
Index server error 206 server pool name 43 server pooling 39 introduction 39 server pools 39 administering 39 assigning connection 45 automatic load balancing 46 configuring connections 48 connecting 42 debugging 150 deleting translation server pools 119 diagnostics 166, 176 groups 40 individual lines 40 manually controlling 48 specifying the relationship 44 starting 40 stopping 41 service 92 environment tab 89 port 91 startup tab 90 TCP/IP port 91 services socket server 60 sessions beginning and ending 16
Index tandem 146 debugger 144 example code 144 TCP/IP connection 8 TCP/IP port 91 TCP/IP Port number socket server 63 TCP/IP port number socket server 58 terminating socket server connections 64 testing FCServlet 74, 81 TimeOut 149 timeout applications 37 FlashCONNECT Web pages 31 tr FCDebug command 149 translation character translation 115 deleting server pools 119 errors 120 one to one 116 translation files 117 translation hex pair 118 translation map 118 troubleshooting 137, 159, 169, 181 debug strategi
Index w3HostName see w3ServerPool 43 w3Html static vs. active pages 14 w3HtmlFormBeg 206 w3HtmlFormEnd 206 w3library 22 w3library directory 22 w3lines 43 w3Lines status 98 w3Log subroutine 110, 146 w3Logs 110, 146 debug 146 w3Logs,Dump log file 111 w3Logs,Dump file 151 w3Logs,errors log file 111 w3Logs,FlashCONNECT log file 111 w3Logs,w3Rotator log file 111 w3Logs.Control 110 w3Logs.
Index WWW-POOL 40 WWW-START configuration 44 WWW-STATUS 96, 98, 207 line descriptions 97 server 96 WWW-STOP 41 WWW-TANDEM 144 X X windows 61 222 FlashCONNECT Administrator’s Guide
