2
Installing the Software

Chapter summary

This chapter explains how to install the server and client components of Financial Analyzer and set correct directory and file access. The chapter also provides information about configuring Financial Analyzer for Web access and setting up the Task Processor to run in the background.

List of topics

This chapter includes the following topics:

• Determining Which Server Component to Install

• Installing Financial Analyzer on the Server

• Understanding the Installed Server Directories and Files

• Installing Financial Analyzer on Client PCs

• Performing a Single-user Installation on a Client PC

• Performing a Shared Installation on a Client PC

• Understanding the Installed Client Directories and Files

• Setting Directory and File Access

• Financial Analyzer Database Security

• Configuring Financial Analyzer for Web Access

• Configuring the Task Processor to Run in the Background

• Starting Financial Analyzer for the First Time

Determining Which Server Component to Install

Introduction

Before you can create a user of any type, you must first use Installer to install an environment for that user. This environment, called a component, contains shell databases and configuration files for that user.

Your first task is to determine which component you will install. The following server components are available for Financial Analyzer:

• Super administrator

• Administrator

• Cluster

• Web

• Single Sign-On

• AS Portlets

Super administrator component

You must install a Super administrator component before installing any other component type.

After installing this component, all other users of this component will be created through the Super administrator workstation using the Users option from the Manage menu. For detailed information about how to perform this task, refer to the topic "Creating Users" in the Financial Analyzer Help system.

Administrator component

If you install an Administrator component you must create the personal database for that component by creating an Administrator workstation using the superior Administrator workstation. For detailed information about how to perform this task, refer to the topic "Creating Users" in the Financial Analyzer Help system.

Cluster component

If you have installed a cluster component you can install the Budget workstation personal databases for that component by creating Budget workstations in the Administrator of that component. For detailed information about how to perform this task, refer to the topic "Creating Users" in the Financial Analyzer Help system.

Note: If you are installing more than one Administrator component that will use the same instance of Express Server, see Appendix B for information about renaming shared databases.

Web component

You should only install the Financial Analyzer Web component separately if you want to place the Web component on a different computer from the one that Express Server is running on.

Single Sign-On component

You should install Single Sign-On only if you plan to use this functionality with Oracle Applications for Financial Analyzer Web users. For detailed information about how to perform this task, refer to the topics "Implementing Single Sign-on and "Procedure: Completing the Single Sign-On component installation .

AS Portlets component

The AS Portlets make data from Financial Analyzer available to users of Oracle Portal. For detailed information about how to install this component, refer to the topic "Procedure: Completing the AS Portlets component installation . For information on setting up and maintaining AS Portlets, refer to Appendix D.

Installing Financial Analyzer on the Server

Introduction

The following procedures explain how to install a Financial Analyzer component on the server.

Procedure: Beginning the server installation

Follow these steps to begin installing Financial Analyzer on the server:

1. Ensure that Express Server is installed and configured on the server.

   Note: For Windows NT systems, make sure that the SecurityLevel setting in Configuration Manager is not set to DOMAIN.

2. Insert the Financial Analyzer Server CD-ROM into the CD-ROM drive and run f:\setup.exe, where "f" represents your CD-ROM drive.

3. In the Welcome dialog box, choose Next.

4. In the File Locations dialog box under Destination, specify the name and path of the Oracle Home that you want to use, then choose Next.

5. The Available Products dialog box appears. It provides the following list of installable components:
   • Super administrator

   • Administrator

   • Cluster

   • Web Listener Files

   • Single Sign-On

   • AS Portlets

   Select the component that you want to install; then choose Next.

6. Complete the installation of the component that you selected, as follows.

   IF you chose . . .	THEN follow the instructions in . . .
   Super administrator,	"Procedure: Completing the Super administrator component installation
   Administrator,	"Procedure: Completing the Administrator component installation
   Cluster,	"Procedure: Completing the Cluster component installation
   Web,	"Procedure: Completing the Web Listener Files component installation
   Single Sign-On,	"Procedure: Completing the Single Sign-On component installation
   AS Portlets	"Procedure: Completing the AS Portlets component installation

   Note: If more than one Super administrator, Administrator, or cluster component is installed on the same server, you must specify a unique Oracle Home for each component.

Procedure: Completing the Super administrator component installation

The following procedure describes the additional steps to follow if you are installing the Super administrator component.

Note: This procedure provides all of the steps for the Complete installation type (described below). If you choose the Typical installation type, which is composed of a subset of the steps in the Complete installation, skip the steps that are related to Financial Analyzer Web.

1. In the Installation Types dialog box, select the type of installation that you want to perform from the following choices:
   • Typical -- This type of installation installs the Super administrator component only.

   • Complete -- This type of installation installs both the Super administrator and Web components.

   When you have completed this task, choose Next.

   Result: The Component Location dialog box appears

2. In the Path box of the Component Location dialog box, specify the path for the location into which you want to install the Super administrator component.

   When you have completed this task, choose Next.

   Note: If you are installing on the Unix platform, do not use uppercase letters or spaces in the path. If you are installing on the Windows NT platform, do not use spaces in the path.

   Result: Depending on you Express Server installation, one of the following can occur:

   • If Installer cannot locate the Express Server home, the Express Server dialog box appears. Proceed to Step 3.

   • If Installer locates more than one Express Server home, the Express Server Instance dialog box appears. Proceed to Step 4.

   • If Installer locates the Express Server home, the Personal Database Information dialog box appears. Proceed to Step 5.

3. If Installer cannot locate the Express Server home, the Express Server dialog box appears. In the Path box of the Oracle Express Server dialog box, enter the path of the Express Server home. You can type the path into the box, or you can click the Browse button to access the Choose Directory dialog box, where you can navigate to the appropriate location.

   When you have completed this task, choose Next.

   Result: The Personal Database Information dialog box appears. Proceed to Step 5.

4. If Installer locates more than one Express Server home, the Express Server Instance dialog box appears. Select the Express Server instance that you would like to configure as a Financial Analyzer Express Server.

   When you have completed this task, choose Next.

   Result: The Personal Database Information dialog box appears. Proceed to Step 5.

5. In the Personal Database Information dialog box, specify the following information related to the personal database:
   • The name of the Super administrator's personal database

   • The server name

   • The port number for Express Server

   • The language in which information will be displayed to your Web users

   When you have completed this task, choose Next.

   Result: The JInitiator Use dialog box appears.

6. In the JInitiator Use dialog box, specify whether you want to use JInitiator when you run Financial Analyzer Web.

   Note: If you are using other Oracle products, it is recommended that you use JInitiator. If you do not use other Oracle products, you may choose not to use JInitiator because of its additional disk space requirements.

   When you have completed this task, choose Next.

   Result: The General Ledger Integration dialog box appears.

7. In the General Ledger Integration dialog box, specify whether you want to install the Oracle General Ledger integration module.

   Note: The Oracle General Ledger integration module allows Financial Analyzer users to load data from Oracle General Ledger into Financial Analyzer for analysis purposes, and to write Financial Analyzer budget data back to Oracle General Ledger.

   When you have completed this task, choose Next.

   Result: The Web Listener Information dialog box appears.

8. In the Web Listener Information dialog box, specify the following information:
   • The Web listener name

   • The Web listener port number

   • A description of the shared database

   • The CGI-bin Alias, which is the name of the virtual directory that specifies the physical directory that contains the Oracle OLAP Web Agent executable file, OOWA.EXE

   When you have this task, choose Next.

   Result: The Web Access Method dialog box appears.

9. In the Web Access Method dialog box, select one of the following options to specify how your users' browsers will load the files that are needed to run Financial Analyzer Web:
   • Load files from the network every time the user logs in -- Financial Analyzer. This option requires less storage on client PCs, but is slower.

   • Load files from the network once; then store them on the client PC -- This option provides better performance, but requires more storage on the client PC.

   When you have completed this task, choose Next.

   Result: The Summary dialog box appears.

10. Review the information in the Summary dialog box to ensure that it is correct; then choose Install.

    Result: Installer installs the Super administrator component. When the installation is complete, the End of Installation dialog box appears.

11. If you chose the Complete installation type, then Installer automatically checks if Oracle WebServer IAS is installed on the machine where the application or component is currently being installed. .

    If Installer detects Oracle WebServer IAS, then you are prompted to configure it automatically.

    If you select Yes, then Installer configures Oracle WebServer IAS.

    If you select No or if Installer does not detect the Oracle WebServer IAS on the machine where the application or component is being installed, then an End of Installation dialog box is displayed. Note the directory information that is displayed in the End of Installation dialog box. You will need to use this information when you add virtual directories to the Web listener, as described in the topic "Configuring Financial Analyzer for Web Access

12. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing the Administrator component installation

The following procedure describes the additional steps to follow if you are installing the Administrator component.

Note: This procedure provides all of the steps for the Complete installation type (described below). If you choose the Typical installation type, which is composed of a subset of the steps in the Complete installation, skip the steps that are related to Financial Analyzer Web.

1. In the Installation Types dialog box, select the type of installation that you want to perform from the following choices:
   • Typical -- This type of installation installs the Administrator component only.

   • Complete -- This type of installation installs both the Administrator and Web components.

   Note: This procedure documents all of the steps that are part of a Complete installation. If you are performing a Typical installation, skip the steps that are related to Financial Analyzer Web.

   When you have completed this task, choose Next.

   Result: The Component Location dialog box appears

2. In the Path box of the Component Location dialog box, specify the path for the location into which you want to install the Super administrator component.

   When you have completed this task, choose Next.

   Note: If you are installing on the Unix platform, do not use uppercase letters or spaces in the path. If you are installing on the Windows NT platform, do not use spaces in the path.

   Result: Installer searches for the Express Server home.

3. If Installer cannot locate the Express Server home, the Express Server dialog box appears. In the Path box of the Oracle Express Server dialog box, enter the path of the Express Server home. You can type the path into the box, or you can click the Browse button to access the Choose Directory dialog box, where you can navigate to the appropriate location.

   When you have completed this task, choose Next.

   Result: The Oracle Express Server Instance Name dialog box appears.

4. In the Oracle Express Server Instance Name dialog box, specify the name of the Express Server instance that you want to configure to support Financial Analyzer.

   When you have completed this task, choose Next.

   Result: The Specify Language dialog box appears.

5. In the Specify Language dialog box, select the language that will appear to your users in Financial Analyzer Web.

   When you have completed this task, choose Next.

   Result: The JInitiator Use dialog box appears.

6. In the JInitiator Use dialog box, specify whether you want to use JInitiator when you run Financial Analyzer Web.

   When you have completed this task, choose Next.

   Result: The Web Listener Information dialog box appears.

7. In the Web Listener Information dialog box, specify the following information:
   • The Web listener name

   • The Web listener port number

   • A description of the shared database

   • The CGI-bin Alias, which is the name of the virtual directory that specifies the physical directory that contains the Oracle OLAP Web Agent executable file, OOWA.EXE

   When you have this task, choose Next.

   Result: The Web Access Method dialog box appears.

8. In the Web Access Method dialog box, select one of the following options to specify how your users' browsers will load the files that are needed to run Financial Analyzer Web:
   • Load files from the network every time the user logs in -- Financial Analyzer. This option requires less storage on client PCs, but is slower.

   • Load files from the network once; then store them on the client PC -- This option provides better performance, but requires more storage on the client PC.

   When you have completed this task, choose Next.

   Result: The Summary dialog box appears.

9. Review the information in the Summary dialog box to ensure that it is correct; then choose Install.

   Result: Installer installs the Administrator component. When the installation is complete, the End of Installation dialog box appears.

10. If you chose the Complete installation type, then Installer automatically checks if Oracle WebServer IAS is installed on the machine where the application or component is currently being installed. .

    If Installer detects Oracle WebServer IAS then you are prompted to configure it automatically.

    If you select Yes, then Installer configures Oracle WebServer IAS

    If you select No or if Installer does not detect the Oracle WebServer IAS on the machine where the application or component is being installed, then an End of Installation dialog box is displayed. Note the directory information that is displayed in the End of Installation dialog box. You will need to use this information when you add virtual directories to the Web listener, as described in the topic "Configuring Financial Analyzer for Web Access

11. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing the Cluster component installation

The following procedure describes the additional steps to follow if you are installing the Cluster component.

1. In the Path box of the Component Location dialog box, specify the path for the location into which you want to install the Cluster component.

   When you have completed this task, choose Next.

   Note: If you are installing on the Unix platform, do not use uppercase letters or spaces in the path. If you are installing on the Windows NT platform, do not use spaces in the path.

   Result: The Summary dialog box appears.

2. Review the information in the Summary dialog box to ensure that it is correct; then choose Install.

   Result: Installer installs the Cluster component. When the installation is complete, the End of Installation dialog box appears.

3. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing the Web Listener Files component installation

The following procedure describes the additional steps to follow if you are installing the Web Listener Files.

1. In the Path box of the Directory of Shared Database dialog box, specify the location of the Financial Analyzer shared database.

   You can type the path into the box, or you can choose the Browse button to open the Choose Directory dialog box, in which you can choose the appropriate directory.

   When you have completed this task, choose Next.

   Result: The Web Listener Information dialog box appears.

2. In the Web Listener Information dialog box, specify the following information:
   • The Web listener name

   • The Web listener port number

   • A description of the shared database

   • The CGI-bin Alias, which is the name of the virtual directory that specifies the physical directory that contains the Oracle OLAP Web Agent executable file, OOWA.EXE

   When you have this task, choose Next.

   Result: The Web Access Method dialog box appears.

3. In the Web Access Method dialog box, select one of the following options to specify how your users' browsers will load the files that are needed to run Financial Analyzer Web:
   • Load files from the network every time the user logs in -- Financial Analyzer. This option requires less storage on client PCs, but is slower.

   • Load files from the network once; then store them on the client PC -- This option provides better performance, but requires more storage on the client PC.

   When you have completed this task, choose Next.

   Result: The Summary dialog box appears.

4. Review the information in the Summary dialog box to ensure that it is correct; then choose Install.

   Result: Installer installs the Web component. When the installation is complete, the End of Installation dialog box appears.

5. Installer automatically checks if Oracle WebServer IAS is installed on the machine where the application or component is currently being installed. .

   If Installer detects Oracle WebServer IAS then you are prompted to configure it automatically.

   If you select Yes, then Installer configures Oracle WebServer IAS.

   If you select No or if Installer does not detect the Oracle WebServer IAS on the machine where the application or component is being installed, then an End of Installation dialog box is displayed. Note the directory information that is displayed in the End of Installation dialog box. You will need to use this information when you add virtual directories to the Web listener, as described in the topic "Configuring Financial Analyzer for Web Access

6. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing the Single Sign-On component installation

The following procedure describes the additional steps to follow if you are installing Single Sign-On.

1. If Installer cannot locate the Oracle Required Support Files, the Required Support Files dialog box appears.

   In the Path box, specify the Oracle home where the Oracle Required Support Files are located.

   You can type the path into the box, or you can click the Browse button to access the Choose Directory dialog box, where you can navigate to the appropriate location.

   When you have completed this task, click Next.

   Result: The FND_TOP Environment Variable dialog box appears.

2. In the Path box of the FND_TOP Environment Variable dialog box, specify the directory location to be stored in the FND_TOP environment variable.

   Note: This environment variable contains the root directory path for the /secure directory, where the appropriate database connection (.dbc) file currently resides, or where a new database connection file will be created. The information in this file is used by Single Sign-On to make a connection to Oracle Applications.

   You can type the full path into the box, or you can click the Browse button to access the Choose Directory dialog box, where you can navigate to the appropriate location.

   When you have completed this task, click Next.

   Results: Depending on whether Installer can locate a database connection (.dbc) file, one of the following results occurs:

   • If the location that you specified in the FND_TOP Environment Variable dialog box contains one or more database connection files, the Oracle OLAP Single Sign-On dialog box appears and Installer prompts you to select the appropriate database connection file from a drop-down list of all of the connection files in the directory.

     Note that the first option in the list is <New .dbc>, which you can use to create a new database connection file, even if others exist.

   • If there are no connection files in $FND_TOP/secure, the New Database Connection File Configuration Information dialog box appears immediately so that you can create one. Proceed to Step 4.

3. If the .dbc file that you need exists in $FND_TOP/secure, select it from the drop-down list in the Database Connection Files box of the Oracle OLAP Single Sign-On dialog box.

   When you have completed this task, click Next.

   Results: One of the following results occurs, depending on whether you are installing on Unix or NT.

   • If you are installing on Unix, the Remote Operation Connection Settings dialog box appears. Skip Steps 4 and 5, and follow the information in Step 6 that applies to Unix installations.

   • If you are installing on NT, the Communication Protocol dialog box appears. Go on to Step 5.

4. If there are no connection files in the directory, or if you select <New.dbc>, the New Database Connection File Configuration Information dialog box appears.

   Use this dialog box to specify the following connection configuration information:

   • File Name -- Specify the name of the database connection file that you are creating.

     The default file name is <machine_name>_<SID>.dbc.

   • Connect String -- Specify the SQL*Net name of the database. This name is also used as the label in the tnsnames.ora file, under which the information needed to connect to the RDBMS is to be stored.

     Note: The TWO_TASK environment variable contains this information.

   • FNDNAM -- Specify the ID for the Application Objects Library (AOL) schema. This is also the Oracle User that will be used for connection to Oracle 8i.

     Note: The value for FNDNAM is usually apps.

   • GWYUID -- Specify the Oracle User/Password combination of the public account to be used for the initial Oracle Applications connection to the Oracle 8i database.

     Note: The GWYUID Oracle User must have Oracle Applications privilege level Public.

   • Server ID -- If Application Server Security is enabled on this database, specify the ID of the Oracle Applications server.

     Note: If Application Server Security is not enabled, this field can be left blank.

   • Guest Applications User -- Specify the Applications User/Password of the Guest user.

     Note: The Guest Applications User is a public Applications user with no responsibilities assigned.

   When you have completed this task, click Next.

   Results: One of the following results occurs, depending on whether you are installing on NT or Unix.

   • If you are installing on Unix, the Remote Operation Connection Settings dialog box appears. Skip Step 5 and follow the information in Step 6 that applies to Unix installations.

   • If you are installing on NT, the Communication Protocol dialog box appears. Go on to Step 5.

5. For NT installations, in the Communication Protocol dialog box, specify the networking protocol that is appropriate to your network from the following choices:
   • MS-RPC (Remote Procedure Call) -- Used for NT Web server to NT Express Server installations.

   • Remote Operations -- Used for Unix Express Server to NT Web server installations.

   When you have completed this task, click Next.

   Result: Depending on the selection you made, one of the following results occurs:

   • If you selected MS-RPC, the MS-RPC Connection Settings dialog box appears.

   • If you selected Remote Operations, the Remote Operation Connection Settings dialog box appears.

6. In the MS-RPC or Remote Operation Connection Settings dialog box, specify the appropriate connection settings for the networking protocol that you selected, as follows:
   • If you selected MS-RPC as your protocol, enter the following information:
     • Instance Name -- Specify the name for the instance of Express Server to which you want to connect. You can find the instance name using the Express Instance Manager.

     • Host -- Specify the host name or IP address for the remote system on which Express Server is running.

     • UUID -- Specify the unique universal identifier (UUID) for a specific Express Server instance, if multiple instances of Express Server are running on the server.

   • If you selected Remote Operations as your protocol, enter the following information:
     • Instance Name -- Specify the name for the instance of Express Server to which you want to connect. You can find the instance name using the Express Instance Manager.

     • Host -- Specify the host DNS name or IP address for the remote system on which Express Server is running.

     • RO Port -- Specify the port number of the Remote Operations Listener.

       Note: This is the value of the ROListenPort parameter, which was set in the Express Instance Manager when you installed Express Server.

   • For Unix installations, enter the following information:
     • Instance Name -- Specify the name for the instance of Express Server to which you want to connect.

     • Host -- Specify the host name or IP address for the remote system on which Express Server is running.

     • RO Port -- Specify the port number of the Remote Operations Listener.

       Note: This is the value of ROListenPort parameter, which was set in the Express Instance Manager when you installed Express Server. For more information, refer to the Express Instance Manager online Help topics.

   When you have completed this task, click Next.

   Result: The Summary dialog box appears.

7. Review the information in the Summary dialog box to ensure that it is correct; then choose Install.

   Result: Installer installs the Single Sign-On component. When the installation is complete, the End of Installation dialog box appears.

8. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing the AS Portlets component installation

Note: For a list of requirements for installing the AS Portlets and making them available to users, refer to "As Portlets .

During the installation, you will need to specify the following information related to the host system on which the Oracle server is running:

• The TNS name (for UNIX installations only)

• The name of the host system

• The system ID (SID)

• The port number

The following procedure describes the additional steps to follow if you are installing AS.Portlets:

1. In the Installation Types dialog box, select the type of AS Portlet installation you want to perform and click Next:
   • Single node -- You can install the AS Portlets Express Files component and the AS Portlets Web Listener Files component on the same server.

   • Multi-node -- If you prefer, you can distribute the functionality of the AS Portlets across multiple servers by installing the AS Portlets Express Files component and the AS Portlets Web Listener Files component on different servers.

   Note: The following requirements apply for multi-node installations

   • You must install the Express files on each server on which there is a Financial Analyzer instance to which the portlets require access.

   • You must install the Web Listener files on the server where the Web Listener is running.

   Result: Depending on the installation type you selected you should proceed as follows:

   • If you select the Multi Node installation type, then proceed to Step 2.

   • If you select the Single Node installation type, then proceed to Step 4.

2. If you selected Multi Node in Step 1, then the Available Product Components dialog box appears.

   The following table shows the numbers of the steps in this procedure that correspond to the product components that you select in this dialog box. After you select one or more components, click Next and proceed to the next step that applies to your selections.

   Product Component	Relevant Steps
   Java Runtime environment	3, 9, and 10
   AS Portlets Express Files	4, 5, 9, and 10
   AS Portlets Web Listener Files	6, 7, 8, 9, and 10

3. If you selected Jave Runtime Environment in Step 2, then the Component Location dialog box appears.

   You can select an alternative location for the Java Runtime Environment that will be installed. The list box shows the component or components for which the location may be changed.

   To show all components, select Show all components to be installed. For more information on a specific component, move the mouse cursor over the component in the list box and hold it there briefly to display a pop-up description.

   For components in which you can change location, selecting a component displays a Destination Location field that you can edit and a Change Location button to browse for alternative locations.

   The Destination Location field enables you to change the location of the component.

   The Change Location button allows you to browse for possible alternative locations for the components.

   Available Disk Space shows the available disk space. By default, the disk space is shown for the volume to which the files will be copied.

   When you have completed this task, click Next.

   Result: Depending on the installation type you selected you should proceed as follows:

   • If you also selected AS Portlets Express Files in Step 2 or you selected the Single Node installation type in Step 1, then proceed to Step 4.or Step 5.

   • If you also selected AS Portlets Web Listener Files in Step 2, then proceed to Step 6.

   • If you did not select any other product components in Step 2, then proceed to Step 9.

4. If Installer cannot locate the Express Server home, the Express Server dialog box appears.

   If Installer locates one or more Express Server homes, the Express Server Instance dialog box appears. Proceed to Step 5.

   In the Path box of the Oracle Express Server dialog box, enter the path of the Express Server home. You can type the path into the box, or you can click the Browse button to access the Choose Directory dialog box, where you can navigate to the appropriate location.

   When you have completed this task, choose Next.

   Result: Depending on the installation type or prouct components you selected you should proceed as follows:

   • If you also selected AS Portlets Web Listener Files in Step 2 or you selected the Single Node installation type in Step 1, then proceed to Step 9.

   • If you did not select any other product components in Step 2, then proceed to Step 9.

5. If Installer locates more than one Express Server home, the Express Server Instance dialog box appears. Select the Express Server instance that you would like to configure as a Financial Analyzer Express Server.

   When you have completed this task, choose Next.

   Result: Depending on the installation type or product components you selected you should proceed as follows:

   • If you also selected AS Portlets Web Listener Files in Step 2 or you selected the Single Node installation type in Step 1, then proceed to Step 6.

   • If you did not select any other product components in Step 2, then proceed to Step 9.

6. In the Oracle Apache Server Home dialog box, use the Path box specify the Apache Server Home (the Home for Oracle HTTP Server).

   Note: If Oracle HTTP Server is not already installed, exit from this installation, install Oracle HTTP Server, and then begin this installation again.

   You can type the path into the box, or you can click the Browse button to access the Choose Directory dialog box, where you can navigate to the appropriate location.

   When you have completed this task, click Next.

   Result: The Oracle Server Information dialog box appears.

7. In the Oracle Server Information dialog box, supply the following information information related to the Oracle server (the server on which the Oracle database resides).
   • TNS Name -- Specify the name of the TNS variable (for Unix installations only)

   • Host Name -- Specify the host name or IP address for the remote system on which the Oracle database resides.

   • SID -- Specify the system ID

   • Port Number -- Specify the port number.

   When you have completed this task, click Next.

   Result: The AS Portlets User Information dialog box appears.

8. In the AS Portlets User Information dialog box, specify the following infomration:
   • AS User ID -- Specify your AS Portlets user ID. This is the user ID for the schema that contains the AS_PORTAL_DATABASE_LIST table, in which you will need to enter information about the databases that you want to make available to users.

   • AS User Password -- Specify the password for your AS portlets user ID.

   When you have completed this task, click Next.

   Result: The Summary dialog box appears.

9. Review the information in the Summary dialog box to ensure that it is correct; then choose Install.

   Result: Installer installs the AS Portlets component. When the installation is complete, the End of Installation dialog box appears.

10. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products or product components.

Related information

For information on setting up and maintaining AS Portlets, refer to Appendix D.

Understanding the Installed Server Directories and Files

Default directory structure

When the installation process is complete, a default directory structure and set of files is set up for each component type. The following default directories are set up beneath the standard root directory for each component type:

• A CODE directory -- Contains the code databases for the application.

• A SHARED directory -- Contains the shared databases for the application and subdirectories that contain files for Financial Analyzer Web access.

• A TEMPORARY directory -- The location for temporary files that are created by the system as it runs.

• A TASKFILE directory -- The location for tasks that are created by users and processed by the system.

• A SHELLS directory -- Contains a set of EIF files used by the system to create personal databases for user workstations.

• A USERS directory -- For the Super administrator installation, contains the Super administrator personal database and a Task Processor personal database. (The Task Processor database is used only if the Task Processor is running in stand-alone mode.) This directory is created as a suggested location for personal databases.

Note: These default directories contain differing combinations of default installation files for each component type.

When Financial Analyzer Web is installed, either as part of a Super administrator or Administrator installation, or when the Web component is installed separately, then the following default directories are set up in the express_home\OLAP\OFAxxx directory where xxx represents the current release of Financial Analyzer:

• An OFAWEB directory -- Contains all of the files needed to run the Web interface.

• An OFASTART directory -- Contains the index.html files for all Web users.

Note: During installation, the Express Server SERVERDBPATH parameter, which is used by Financial Analyzer Web, is updated with the path to the Super administrator's CODE directory. If you subsequently install one or more administrators that use the same instance of Express Server, the SERVERDBPATH parameter will continue to point to the CODE directory of the Super administrator, not to that of any newly installed administrator.

Super administrator component

The following table describes the files that are installed into the default directory structure when you install a Super administrator component.

Directory	Installed Files
CODE	ofaserve.db ofatools.db ofaupgr.db ofacdcf.db ofacdcf.cfg The installed files also include a set of language database files. There is one file for each supported language. The file names use the format ofaxxx.db, where xxx is a three-character identifier for a specific language.
SHARED	ofas.db ofastask.db ofasctl.db ofaslck.db ofasyscf.db ofasyscf.cfg ofabgrtk.cfg ofaweb.cfg Note: If you enable Web access to the Super administrator's shared database through Financial Analyzer, the following file is created in this directory: index.html
TEMPORARY	Empty
TASKFILE	Empty
SHELLS	insar.eif insbw.eif instpm.eif
USERS	super_personal.db super_personal.cfg tpm.db tpm.cfg

Administrator component

The following table describes the files that are installed into the default directory structure when you install an Administrator component.

Directory	Installed Files
CODE	ofaserve.db ofatools.db ofaupgr.db ofacdcf.db ofacdcf.cfg The installed files also include a set of language database files. There is one file for each supported language. The file names use the format ofaxxx.db, where xxx is a three-character identifier for a specific language.
SHARED	ofas.db ofastask.db ofsctl.db ofaslck.db ofasyscf.db ofabgrtk.cfg ofaweb.cfg Notes: When you complete this workstation's setup using the Maintain Users feature, the following file is set up in this directory: ofasyscf.cfg For detailed information about how to complete the workstation setup, refer to the topic "Creating Users" in the Financial Analyzer Help system. If you enable Web access to the Administrator's shared database through Financial Analyzer, the following file is created in this directory: index.html
TEMPORARY	Empty
TASKFILE	Empty
SHELLS	insar.eif insbw.eif insdba.eif instpm.eif
USERS	Empty Note: When you complete this workstation's setup using the Maintain Users feature and if you specified this suggested location, the following files are placed in this directory: administrator_personal.db administrator_personal.cfg tpm.db tpm.cfg For detailed information about how to complete the workstation setup, refer to the topic "Creating Users" in the Financial Analyzer Help system.

Cluster component

The following table describes the files that are installed into the default directory structure when you install a cluster component.

Directory	Installed Files
CODE	ofaserve.db ofatools.db ofaupgr.db ofacdcf.db ofacdcf.cfg The installed files also include a set of language database files. There is one file for each supported language. The file names use the format ofaxxx.db, where xxx is a three-character identifier for a specific language.
SHARED	ofasyscf.db Note: When you complete this workstation's setup using the Maintain Users feature, the following file is set up in this directory: ofasyscf.cfg For detailed information about how to complete the workstation setup, refer to the topic "Creating Users" in the Financial Analyzer Help system.
TEMPORARY	Empty
TASKFILE	Empty
SHELLS	insbw.eif
USERS	Empty Note: When you complete this workstation's setup using the Maintain Users feature and if you specified this suggested location, the following files are placed in this directory: cluster_wks_personal.db cluster_wks_personal.cfg For detailed information about how to complete the workstation setup, refer to the topic "Creating Users" in the Financial Analyzer Help system.

Installing Financial Analyzer on Client PCs

Client installation options

You have two options for installing Financial Analyzer on client PCs:

• You can install Financial Analyzer as a single-user installation.

• You can install Financial Analyzer as a shared installation.

Important Client Installation Information

If a previous release of the Financial Analyzer client software is already present on the PC where you are installing Financial Analyzer 11i, you must uninstall that previous release before installing the new release.

Single-user installations

Description: Single-user installation

In a single-user installation, users install Financial Analyzer directly from the CD-ROM. The single-user installation copies client files to the PC.

Configuration options: Single-user installation

A single-user installation offers two options for client mode: thin client or thick client. For a description of these modes, refer to "Client configuration options .

Advantages: Single-user installation

A single-user installation offers the following advantages:

• Users are set up individually.

• The installation process is not affected by network traffic.

Shared installations

Description: Shared installation

In a shared installation, you install Financial Analyzer Client to a common staging area on the network. This area is referred to as a shared OLAP home. Users then access the shared area to install Financial Analyzer on their PCs.

For further information about setting up a shared OLAP home on the network, see "Procedure: Setting up a shared OLAP home on the network .

Configuration options: Shared installation

A shared installation offers thin client mode and thick client mode. For a description of these modes, refer to "Client configuration options . There is also a third option: a thinner thin client installation, referred to as a "thinner client installation," in which most of the client files are stored on the network rather than on the PC.

Advantages: Shared installation

A shared installation offers the following advantages:

• Users have access to the same standardized software from the network.

• If you choose the thinner client installation, the shared installation installs a minimum number of files on the PC, thereby requiring considerably less disk storage. Most of the client files reside on the server, which can be anywhere on the network.

• A shared installation is easy to update. Updates can be run from the shared OLAP home on the network.

Procedure: Setting up a shared OLAP home on the network

Follow these steps to set up a shared OLAP home as a staging area for a shared installation:

1. Insert the Oracle Financial Analyzer CD-ROM into the drive and run setup.exe from the f:\lan client directory, where "f" represents your CD-ROM drive.

2. In the Welcome dialog box, choose Next.

3. In the File Locations dialog box, specify the Oracle Home that you want to use, then choose Next.

4. In the Shared OLAP Home Location dialog box, specify the location for the shared OLAP Home on the network. The drive that you specify must be a mapped drive. After you have specified the path information, choose Next.

5. In the Summary dialog box, make sure that all of the specifications for the installation are correct, then choose Install.

   Installer performs the installation on the network.

6. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

7. Notify your users of the shared OLAP home location on the network that contains the setup.exe file that they must run to perform the shared installation on client PCs.

Providing multiple shared installations

When you provide shared installations for users, you have the option to provide different installation packages (that is, different product and component configurations) for different sets of users. You can specify a unique set of products and components for each installation package.

For each shared installation package that you want to create, follow the procedure in "Procedure: Setting up a shared OLAP home on the network , with the following stipulations:

• In the File Locations dialog box, you must specify a unique Oracle Home for each shared installation package.

• In the Shared OLAP Home Location dialog box, you must specify a unique shared OLAP Home for each shared installation package.

Note: For each installation package that you set up, users must install the entire set of products that you have specified for that package; they cannot choose individual products from the set that you have provided.

Performing a Single-user Installation on a Client PC

Procedure: Beginning a single-user installation

Follow these steps to begin the installation of Financial Analyzer on a client PC using the client CD-ROM:

1. For a workstation that will access the server in thick client mode, ensure that Personal Express Server has been installed on the workstation.

2. Insert the Financial Analyzer Client CD-ROM into the drive and run setup.exe from the f:\local client directory, where "f" represents your CD-ROM drive.

3. In the Welcome dialog box, choose Next.

4. In the File Locations dialog box under Destination, specify the Oracle Home that you want to use, then choose Next.

5. The Available Products dialog box appears. This dialog box allows you to choose whether to perform a thin client or thick client installation. Select the desired client mode, then choose Next.

   Note: If you choose the thick client installation and you have not yet installed Personal Express Server, Installer issues a prompt that reminds you to install Personal Express Server after you have completed the Financial Analyzer installation. Choose Next on the prompt dialog box to continue with the Financial Analyzer installation.

6. Depending on the client mode that you have chosen to install, do one of the following.

   IF you chose the . . .	THEN follow the instructions in . . .
   thin client installation,	"Procedure: Completing a thin client single-user installation
   thick client installation,	"Procedure: Completing a thick client single-user installation

Procedure: Completing a thin client single-user installation

The following procedure describes the additional steps to follow if you are performing a thin client installation.

1. In the Thin Client Installation: Location dialog box, specify the path for the application initialization file (OFA.INI). You can use the default path, you can use the Browse button to choose a different path, or you can type a path name. After you have specified the path information, choose Next.

2. In the Thin Client Installation: Sever Type dialog box, select the operating system for the server where the personal database is to run, then choose Next.

3. In the Summary dialog box, make sure that all of the specifications for the installation are correct, then choose Install.

   Installer installs the products that you have selected.

4. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing a thick client single-user installation

The following procedure describes the additional steps to follow if you are performing a thick client installation.

1. In the Thick Client Installation: Location dialog box, specify the path for the location of the Budget workstation personal database file. You can use the default path, you can use the Browse button to choose a different path, or you can type a path name. After you have specified the path information, choose Next.

2. In the Thick Client Installation: Shared Database Information dialog box, specify the following information for the shared database that the Budget workstation is to access on the server.
   • The path for the shared database

   • The server name

   • The Express Server port number

   After you have specified the above information, choose Next.

3. In the Thick Client Installation: Server Type dialog box, select the operating system for the server where Express Server is running.

4. In the Summary dialog box, make sure that all of the specifications for the installation are correct, then choose Install.

   Installer installs the products that you have selected.

5. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Performing a Shared Installation on a Client PC

Procedure: Beginning a shared installation

Follow these steps to begin the installation of Financial Analyzer on a client PC from a staging area on the network:

1. For a workstation that will access the server in thick client mode, ensure that Personal Express Server has been installed on the workstation.

2. Run the the setup.exe file that performs the shared installation, as instructed by your database administrator. The setup.exe file is located in the shared OLAP home on the network.

   Note: The shared OLAP home is the area on the network in which the staging area for the shared installation has been established, as described in "Procedure: Setting up a shared OLAP home on the network .

3. In the Welcome dialog box, choose Next.

4. In the File Locations dialog box under Destination, specify the Oracle Home that you want to use, then choose Next.

5. The Available Products dialog box appears. This dialog box allows you to choose whether to perform a thinner client, thin client, or thick client installation. Select the desired client mode, then choose Next.

   Note: If you choose the thick client installation and you have not yet installed Personal Express Server, Installer issues a prompt that reminds you to install Personal Express Server after you have completed the Financial Analyzer installation. Choose Next when prompted to continue with the Financial Analyzer installation.

6. Depending on the client mode that you have chosen to install, do one of the following.

   IF you chose the . . .	THEN follow the instructions in . . .
   thinner client installation,	"Procedure: Completing a thinner client shared installation
   thin client installation,	"Procedure: Completing a thin client shared installation
   thick client installation,	"Procedure: Completing a thick client shared installation

Procedure: Completing a thinner client shared installation

The following procedure describes the additional steps to follow if you are performing a thinner client installation.

1. In the Thinner Client Installation: Location dialog box, specify the path for the application initialization file (OFA.INI). You can use the default path, you can use the Browse button to choose a different path, or you can type a path name. After you have specified the path information, choose Next.

2. In the Thin Client Installation: Server Type dialog box, select the operating system for the server where the personal database is to run, then choose Next.

3. In the Summary dialog box, make sure that all of the specifications for the installation are correct, then choose Install.

   Installer installs the products that you have selected.

4. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing a thin client shared installation

The following procedure describes the additional steps to follow if you are performing a thin client installation.

1. In the Thin Client Installation: Location dialog box, specify the path for the application initialization file (OFA.INI). You can use the default path, you can use the Browse button to choose a different path, or you can type a path name. After you have specified the path information, choose Next.

2. In the Thin Client Installation: Server Type dialog box, select the operating system for the server where the personal database is to run, then choose Next.

3. In the Summary dialog box, make sure that all of the specifications for the installation are correct, then choose Install.

   Installer installs the products that you have selected.

4. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Procedure: Completing a thick client shared installation

The following procedure describes the additional steps to follow if you are performing a thick client installation.

1. In the Thick Client Installation: Location dialog box, specify the path for the location of the Budget workstation personal database file. You can use the default path, you can use the Browse button to choose a different path, or you can type a path name. After you have specified the path information, choose Next.

2. In the Thick Client Installation: Shared Database Information dialog box, specify the following information for the shared database that the Budget workstation is to access on the server.
   • The path for the shared database

   • The server name

   • The Express port number

   After you have specified the above information, choose Next.

3. In the Thick Client Installation: Server Type dialog box, select the operating system for the server where Express Server is running.

4. In the Summary dialog box, make sure that all of the specifications for the installation are correct, then choose Install.

   Installer installs the products that you have selected.

5. In the End of Installation dialog box, choose Exit to close Installer or choose Next Install to install additional Oracle products.

Understanding the Installed Client Directories and Files

Thick client component

For a thick client installation, the following files are located in the oracle_home\OLAP\OFAxxx\thickclient directory (where xxx represents the current release of Financial Analyzer):

ofaserve.db

ofatools.db

ofaupgr.db

ofacdcf.db

ofacdcf.cfg

This directory also contains the Financial Analyzer application files.

The installed files also include a set of language database files. There is one file for each supported language. The file names use the format ofaxxx.db, where xxx is a three-character identifier for a specific language.

In addition, a thick client installation also includes the following directory:

oracle_home\OLAP\OFAxxx\thickclient\user

where:

• xxx represents the current release of Financial Analyzer and

• user is a directory name specified during the installation procedure.

The oracle_home\OLAP\OFAxxx\thickclient\user directory contains the following files:

personal_database.db

personal_database.cfg

ofasyscf.db

ofasyscf.cfg

ofa.ini

Thin client component

In a thin client installation, the following directory is created:

oracle_home\OLAP\OFAxxx\thinclient\user

where:

• xxx represents the current release of Financial Analyzer and

• user is the name of the directory on the PC for the application initialization file (ofa.ini), as specified during the installation procedure.

Thinner client component

In a thinner client installation, the following directory is created:

oracle_home\OLAP\OFAxxx\thinnerclient\user

where:

• xxx represents the current release of SNAPI and

• user is the name of the directory on the PC for the application initialization file (ofa.ini), as specified during the installation procedure.

Refer to the current Oracle Financial Analyzer 11i Release Notes for the correct software release information.

Additional client component information

The Financial Analyzer client installation process will also install SNAPI (Structured N-Dimensional API) in the following directory:

oracle_home/OLAP/OSNxxxx/

where xxx represents the current release of SNAPI.

This directory contains SNAPI files, which provide the application programming interface between the Financial Analyzer client component and the personal database using Express Server or Personal Express.

Setting Directory and File Access

Introduction

This topic explains how to set up the correct type of access to the installed directories and files, so that users have access to the information that they need.

Setting up rights access for NT servers

All users who need to connect to an NT server running Financial Analyzer must have the Log on locally right assigned to their network account. For more information about the Log on locally right, refer to the Express Installation and Configuration Guide.

Setting up access to directories

The following table provides information about the type of access that all users need to the directories that are set up during the installation process.

Directory	Type of Access Required
CODE	Read-Only
TEMPORARY	Read/Write
TASKFILE	Read/Write
SHELLS	Read-Only
personal_database	Read/Write
SHARED:	Administrator and Task Processor	All Other Users
OFAS	Read/Write	Read-Only
OFASTASK	Read/Write	Read/Write
OFASCTL	Read/Write	Read-Only
OFASLCK	Read/Write	Read-Only
OFASYSCF	Read/Write	Read-Only

Important: At installation time, when using the Manage User feature to set up users' workstations, administrators need full access to directories into which they will install users' personal databases.

Note: Databases that are created through Express Server have the same file access rights that are specified in Express. On Unix servers, to change file access rights of databases that are created through Express, you must use the acls command. Do not use the chmod command on these files.

Financial Analyzer Database Security

Shared Database

Access to a Financial Analyzer shared database ofas.db is controlled through the PERMIT_READ and PERMIT_WRITE functions of the Express Server PERMIT command.

To attach the shared database in read/write mode the connection to Express Server must be made using an operating system username that is associated with the Financial Analyzer Administrator workstation user for that shared database. Once attached in read/write mode, all the objects in the database are available to the user.

When you attach the shared database read-only the connection to Express Server must be made using an operating system username associated with a valid Financial Analyzer user who is defined by the Administrator for that shared database. The user will only be able to access the dimensions, dimension values, financial data items, hierarchies, and attributes that have been distributed to that Financial Analyzer user connected with that operating system username. If the operating system username is associated with more than one Financial Analyzer user then the database objects available to the user will be those distributed to the first instance of that Financial Analyzer user in the list of users.

Workstation personal database

Access to a workstation's personal database is controlled by the operating system username entered in the Connect to EXPRESS Session dialog box when starting Financial Analyzer. The operating system username must be associated with a Financial Analyzer user.

For detailed information about associating operating system usernames with Financial Analyzer users, refer to the topic "Creating Users" in the Financial Analyzer Help system.

Configuring Financial Analyzer for Web Access

Overview of configuration procedure

Follow these general steps to configure Financial Analyzer for Web access:

1. Ensure that you have installed all the necessary components that are required to run Financial Analyzer through the Web. These include:
   • Express Web Agent

   • Web listener software (Oracle Web Application Server is recommended)

2. Enable Web Agent security in Oracle Express Instance Manager, as described in "Procedure: Enabling Web Agent security .

3. Modify the Web listener, as described in "Procedure: Adding virtual directories to the Web listener .

4. Provide the URL for the shared database to the users who need Web access to that database, as described in "Providing the URL for a shared database to users . By specifying this URL in their browsers, users will be able to see everything that the administrator has distributed to them.

Procedure: Enabling Web Agent security

Follow these steps to enable Web Agent security:

1. Start Oracle Express Instance Manager.

2. In the Web Agent tab, set the following setting:

   WebAuthenticationType=BASIC

   or

   WebAuthenticationType=FORM

   Leave all other settings as the default.

3. Choose Set.

4. In the Security tab, set the following setting:

   RequirePasswordEncryption=NO

   Leave all other settings as the default.

5. Choose Set.

6. Choose OK.

Note: After you complete the above procedure, you must restart Express Server to enable Web Agent security.

Procedure: Adding virtual directories to the Web listener

Follow these steps to modify the Web listener.

1. Start your Web browser.

2. Add the mappings for the two virtual directories that you noted from the End of Installation dialog box in the Super administrator and Administrator component installations into your Web listener.

   Important: You can change the name of the ofastart directory, but you cannot change the name of the ofaweb directory.

   Notes: If you an enabling more than one shared database for Web access with one Web listener you will need to specify unique ofastart virtual directories for each shared database.

   Unix is case sensitive, so you must use the correct case when you enter the virtual directories. NT is not case sensitive.

   The virtdirs.txt text file describes the virtual directory structures that you must create. It is located in the ofaweb directory on the Web Agent server.

3. Restart the Web listener. If you are using Oracle Web Server, you must restart the Web listener whenever you modify it.

   The Web listener checks that the directories that you entered exist. If any directories are not present, you receive an error message.

   Important: If you move or delete any of the files or directories on the server that are referenced in the Web listener directory mappings, you must update the mappings to refer to the new locations.

Providing the URL for a shared database to users

To complete the configuration of Financial Analyzer for Web access, provide users who are to have Web access to a shared database with a URL that consists of the name of the Web server and the name of the virtual directory for the shared database (ofastart).

For example, assume that the name of the Web server is servername. Users can access the shared database on the Web by specifying the following URL in their browsers:

http://servername/ofastart

Notify your users that they must accept cookies if they are prompted to do so. Also alert them that the Netscape browser will prompt them to download Java classes the first time that they access Financial Analyzer on the Web. If they have chosen Smart Update, they will be asked to specify a location for downloading these files.

Implementing Single Sign-on

About Single Sign-On

Single Sign-On is an Oracle Web Agent CGI program that allows authenticated Oracle Self Service Application users to access Financial Analyzer without additional security challenges.

Implementing Single Sign-On assumes that you have performed several preliminary installation and setup tasks.

Note: This feature is available only for Financial Analyzer Web users.

Requirements for implementing Single Sign-On

Install the Application Object Library (AOL) patch

You must install a special AOL patch for Financial Analyzer. The patch will update Oracle Applications with Financial Analyzer Single Sign-On metadata (roles, menus, functions, and so forth).

Install Single Sign-On

You must install Single Sign-On on the same machine on which the Web server is installed.

Set up users and responsibilities in Oracle Applications

You must define each Financial Analyzer Web user in Oracle Applications and assign user responsibilities. You can associate a user with one or more of the following responsibilities:

• OFA Administrator

• OFA Budget

• OFA Analyst

• OFA External

Set up system profiles in Oracle Applications

You must also set up the following system profiles in Oracle Applications:

• OFA Server Profile --The Web listener host and, optionally, its port number, in the format host_name[:port]

• OFA Web Agent profile -- The name and virtual path of your Single Sign-On Web Agent CGI program.

• OFA Express Access Descriptor profile -- The service name of the instance to which you will connect.

• OFA Installation Path profile -- The path to your Financial Analyzer root directory.

Set Up the Single Sign-On Web Agent in Express

To ensure that Single Sign-On users can connect to a Financial Analyzer session, in the Express Instance Manager, you must set the following properties to a value of None:

• Required Security Level

• Required Authentication Level

• Web Agent Web Authentication Type

Ongoing task: Import users into Financial Analyzer from Oracle Applications

As you create new users, you must import their user names from Oracle Applications. For details, refer to the topic called "Creating Users" in the Financial Analyzer Help system.

Configuring the Task Processor to Run in the Background

Overview

You can configure the Task Processor so that it runs as a background task on the server. When configured to run as a background task the Task Processor is not reliant on the Administrator or Task Processor workstation interface. When you use the background method you can control the Task Processor from outside of Financial Analyzer.

Procedure: Configuring the Task Processor to run in the background

Use the following procedure to configure the Task Processor to run in the background. Follow this procedure for each instance of Express Server for which you want to run a Task Processor in the background.

1. Start Oracle Express Instance Manager.

2. Select the Session tab.

3. In the Category box, select Initial Session, then specify the following settings:

   ShutDownSPLScript=oecnn/taskstop.inf
SPLScriptLogging=NO
StartupSPLScript=oecnn/taskini.inf
WakeupMilliseconds=30000
WakeupSPLScript=oecnn/taskrun.inf

   Note: The WakeupMilliseconds setting determines how often the server checks whether the tkstop.flg file is present in the taskfile directory. Oracle Corporation recommends a setting of 30000 milliseconds, which is equal to 10 seconds.

4. Choose Set.

5. Choose OK.

6. In the Express Server Client Support File directory, open the file tkserver.ini and add the location and name of the Task Processor initialization file (ofabgrtk.cfg) for each Administrator.

   Example:

   oracle_home/olap/super/shared/ofabgrtk.cfg

   or

   oracle_home/olap/subdba/shared/ofabgrtk.cfg

   Note: On NT, you must use forward slashes for drive paths.

7. Access the Administrator workstation and add the Persistent Session Initialize username as a valid administrator user.

   Notes: The default values for the Initialize user name are:

   • For the NT operating system: OESinit

   • For Unix operating system: oesinit

8. Run the Task Processor in the foreground to process the username change.

9. Ensure that the Persistent Session Initialize user name has write access to the Financial Analyzer shared directory.

10. Restart Express Server to activate these new settings.

    Once Express Server has been restarted, the Task Processor will initialize on the server in the background. Therefore, anything sent to the Task Processor in Financial Analyzer will be processed immediately.

Using the Task Processor directly on the server

You can start the Task Processor directly on the server by renaming or removing the tkstop.flg file in the taskfile directory. To stop the Task Processor directly on the server, put the tkstop.flg file back in place in the taskfile directory.

Related information

For information about running the Task Processor, refer to the topic "Running the Task Processor in Background Mode," in the Financial Analyzer Help system.

Starting Financial Analyzer for the First Time

Verifying the installation

A successful client installation creates an Oracle for Windows program group on the PC. To verify the installation, you start up the workstation by running Financial Analyzer from this program group. The Connect to EXPRESS Session dialog box appears, allowing you to connect to an Express Server session to start Financial Analyzer.

Note: When you log in for the first time, you must specify information that enables the user to connect to an Express Server session. This information is retained by the system. Only the password is needed to log into subsequent sessions.

Procedure: Logging into Express Server

Use the following procedure to log into Express Server.

1. Double-click on the Financial Analyzer icon.

2. Complete the fields as follows.
   • Username -- Enter the workstation user's username for the operating system on which Express Server is running.

   • Password -- Enter the user's password for the operating system on which Express Server is running.

   • Domain -- If the user's workstation is connecting into an Express Server instance running on an NT domain server, enter the domain name.

   • Name -- Enter the name of the user's personal database.

     Note: For certain installations, this information appears automatically.

   • Path -- Enter the full path of the user's personal database.

     Important: When running on an NT server, you must use server drive letters rather than UNCs.

   • Server -- Enter the name or IP address of the server where the instance of Express Server to which this workstation will connect is installed.

     Note: If the user's workstation is running as a thick client, you can leave this field blank.

   • EndPoint or UUID -- If the Express Server instance is running on Unix, specify its EndPoint.

     If multiple instances of Express Server are running on an NT server, identify the Express Server instance to which this workstation will connect by entering its unique universal identifier (UUID).

3. Choose OK.

   If you are logging in on any type of workstation other than a Super administrator workstation, the Financial Analyzer main screen now appears.

   If you are logging in on a Super administrator workstation, you must complete these additional steps:

   1. You will be asked to select a language. The language that you select will be the system-wide language for entering object descriptions into Financial Analyzer. Select the desired language, then choose OK.

   2. You will be asked to verify the language that you selected. Make sure that the selected language is the correct one, then choose Yes.

      The Financial Analyzer main screen now appears.