The following files are distributed with the FlashConnect software and placed in the host file system, or are existing host files used by FlashConnect.
FCdebug.exe (UNIX, Windows)
The FCdebug command is useful for tracking down problems with the FlashConnect server. It displays the information in FlashConnect’s shared memory segment in tabular format, and can release locks if necessary. See Using the FlashConnect Server Debug Program in the FlashConnect Administrator’s Guide for additional information.
fccgi.exe (UNIX, Windows)
fccgi.exe is an application the HTTPD server starts when it receives an HTTP connection destined for a FlashConnect dynamic application. fccgi.exe reads the browser information passed from the HTTPD server, transforms the browser information into a form acceptable to the D3 server, then connects to FCService.exe. fccgi.exe waits for the reply from the D3 server and passes it back to the browser.
fcisapi.dll (Windows)
fcisapi.dll does the same job as fccgi.exe, but does it faster by becoming part of the Web server. Instead of the Web server running a separate executable (fccgi.exe), fcisapi.dll runs within the Web server’s address space, providing a faster response time. Use fcisapi.dll on Web servers that support ISAPI (such as Microsoft Internet Information Server).
To use fcisapi.dll instead of fccgi.exe, make it part of the URL. Instead of:
http://localhost/cgi-bin/fccgi.exe?w3exec=boo
your URL would be:
http://localhost/cgi-bin/fcisapi.dll?w3exec=boo
fcss.jar (UNIX/Windows)
The fcss.jar file is installed with the FlashConnect Java components and contains the Java classes required to use FlashConnect Socket Server and FCServlet.
FlashConnect.d3 (UNIX/Windows)
FlashConnect.d3 contains an account-save of the www account.
Images (UNIX/Windows)
The images directory is installed with the FlashConnect Java components and contains the images used by FlashConnect Socket Server.
Readme.txt (UNIX/Windows)
The Readme.txt file contains important information not included in other FlashConnect documentation. The Readme display during the FlashConnect installation.
WebContent (UNIX/Windows)
The WebContent directory contains the Web pages and images for the FlashConnect demonstrations and examples.
agent.exe (Windows)
The agent.exe application is installed with FlashConnect Java components. It is used by the FlashConnect installation application to help install the FlashConnect Socket Server.
FCSocketServer.exe (Windows)
The FCSocketServer.exe application is installed with the FlashConnect Java components and is located in the system32 directory. It is used by the FlashConnect installation application to help install, start, and stop the FlashConnect Socket Server.
FCServlet.dll (Windows)
The FCServlet.dll is installed with the FlashConnect Java components and is located in the system32 directory. It is the Java Servlet connector that augments the fcisapi.dll and fccgi.exe connectors.
FCServlet.so (UNIX)
FCServlet.so is installed in the location you specify during installation. If you did not specify a directory, this file is installed in the default directory, /usr/lib/tigerlogic/fcservlet.so.
FCService (UNIX)
The FlashConnect Service, referred to as FCService, directs data packets between browsers and the D3 server. When a connection is made, FCService checks if it is part of an established session.
If it is a new connection, FCService begins a new session by selecting a free D3 server and passing the data from the browser to the D3 server.
If it is an existing connection, FCService directs the data from the browser to the D3 server that is waiting for it. FCService does not terminate the connection; it is the responsibility of the application running on the D3 server to decide when the connection is to be terminated.
FCService’s configuration is maintained in the FlashConnect.conf file. The location of the FlashConnect.conf file can be specified in the command line. For example,
./FCService -c/temp/test
If it is not specified in the command line, FCService looks for the FlashConnect.conf file in the /etc directory.
Using FCService -d0 causes FCService to log diagnostic messages to the file /tmp/FCdebug.000n.txt file. See the Logging Diagnostic Messages for FCService and FCSocketServer topic in the FlashConnect Administrator’s Guide for more information on the format of this file.
FCService.exe (Windows)
The FlashConnect Service, referred to as FCService, or FCService.exe, directs data packets between browsers and the D3 server. When a connection is made, FCService.exe looks to see if it is part of an already established session.
If it is a new connection, FCService.exe begins a new session, selects a free D3 server, and passes the data from the browser to the D3 server.
If it is an existing connection, FCService.exe directs the data from the browser to the D3 server that is waiting for it. FCService.exe does not terminate the connection; it is the responsibility of the application running on the D3 server to decide when the connection terminates.
The configuration information for FCService.exe is located in the system registry. Access FCService.exe from the FlashConnect program group in the Start menu.
Diagnostic messages log to the file /tmp/FCdebug.000n.txt file. See the Logging Diagnostic Messages for FCService and FCSocketServer topic in the FlashConnect Administrator’s Guide for more information on the format of this file.
To log diagnostic messages:
Open the Windows Services application from the Control Panel.
Right-click FCService from the list of services and select Properties.
The Properties dialog box displays.
Enter the text below in the Start Parameters text box:
-debug -d0 |
Click OK.
Registry Key (Windows)
The FlashConnect registry key is located in this directory:
HKEY_LOCAL_MACHINE\Software\TigerLogic\FlashConnect
WARNING |
It is best not to edit registry values from the registry editor. Instead, use FCConfig.exe to make any registry value changes. See the Customizing the Local Environment topic in the FlashConnect Administrator’s Guide for more information. |
See Also