Installing the Reporting and Analytics Application Server

This chapter describes the prerequisites, instructions, and verification steps for installing the Reporting and Analytics application server:

• Installing Reporting and Analytics

• Verifying the Reporting and Analytics Application Server Installation

• Installing Reporting and Analytics
  
• Verifying the Reporting and Analytics Application Server Installation
  

Installing Reporting and Analytics

1. If you are installing Reporting and Analytics on a different drive letter than the one you used on the OBIEE server, change the drive letter for the following properties in the OBIEE server microsConfig.properties file:

   myInsightRootDir=Drive:/myMicros/myInsight

   reportDefPath=Drive:/myMicros/myInsight/org

   OBIEE.ImageTempPath=Drive:/myMicros/myPortal/imagesTemp

   mySecureDocXDir=Drive:/myMicros/myInsight/secureMyDocX (if you are using the docViewer portlet)

2. Extract the following from the installation file archive in the same file structure to the Reporting and Analytics application server. Do not extract the files to a folder structure that contains spaces.

   /Weblogic/

   Install_version.exe

3. Double-click Install_version.exe to launch the installation wizard.
4. On the Choose Install Folder page, enter the installation path or click Choose to select the installation path.
5. On the Before We Begin page, select Yes or No for the questions shown to help the installation wizard understand your installation environment. The selections do not affect whether or not the wizard installs the selected modules, but the selections allow you to enter database connection information for the selected modules.
   1. For Would you like to install or upgrade a database with this installation for either myMicros or iCare?, select No.
   2. For Will different features connect to the myMicros Database using different database IP Addresses, select Yes if you expect to use more than one IP/SID to connect to the Enterprise Back Office database. For example, select Yes in an Oracle Real Application Cluster (RAC) environment that does not use a virtual IP and when features such as Remote Transfer Agent connect to a different node. If you select No, you can still modify the connection strings, but you cannot view individual database information screens by feature.
   3. Select Yes or No for whether you will install Gift and Loyalty (iCare), Inventory Management (myinventory), and the weather service. The installation wizard shows setup and configuration screens for each application that you select Yes.
   4. For Will myLabor be used with this installation?, select Yes to install Labor Management.
6. On the Use existing Portal configuration page, make your selection based on your installation:
   1. If you want to install with a clean set of configurations, select No to install and configure a new installation set.
   2. If you are performing an upgrade and want to keep old settings, select Yes to use existing configurations. You can then select whether to configure the feature set on the Additional Features page.
7. On the Choose Install Set page, select Portal and other components that you want to install on this server.
8. On the Check if Cluster Environment page, select No.
9. On the WebLogic Info page, configure the application server settings:

   Table 3-16 Oracle WebLogic Application Server Information

   Field	Description
   WebLogic User Name and WebLogic Password	Create the login credentials for an administrator account on the WebLogic application server. The password must be eight to 20 characters, must not contain special characters, and must include at least one number.
   Local JVM Path	Verify the folder path to the local Java Development Kit installation. This install path must not contain spaces.
   WebLogic Admin Server Host Name and WebLogic Admin Server Port	Enter the hostname and port of the Oracle Business Intelligence server, typically 7001.
   App Server Host Name	Enter the hostname of the Reporting and Analytics WebLogic application server.
   Node Manager port	Enter the port used by the Node Manager, typically 9556.

10. On the Published URL page, enter the published site URL. What are Published Site URLs? contains more information.
11. On the Map Drive page:
    1. Create a mapped network drive to the drive containing the myMicros folder on the OBI server. For example, if you installed OBI on the E: drive, you can create the mapped drive Z:\ and enter the path as shown in the following image:

       Figure 3-3 Mapped Network Drive to OBI Server

       
    2. Enter the mapped drive root and the path to the myMicros installation folder. For example, Z:\myMicros\
12. (Upgrades only) On the Where would you like to store a backup copy of the existing installation? page, select the folder to store a backup of the installation.
13. On the SSL page, select Yes to enable SSL/Transport Layer Security.
14. On the Certificate Configuration - Portal page, fill out the form to install the signed certificate:
    1. Enter the Keystore Password, the Private Key Password, and the Alias that was used when generating the Certificate Signing Request.
    2. Click Choose and select the certificate file, and then click Next.

       Make sure the filepath includes the following components: folder_path/file_name.extension

    3. Verify the certificate information, and then click Next.
15. On the Database Information page, configure the connection to the Enterprise Back Office database:

    Table 3-17 Database Information

    Oracle Database	Microsoft SQL Server
    In the Database Type section, select Oracle, and then enter the database network port and SID. Enter the database login credentials. Enter the hostname of the database server. In the Preferred Cache Type drop-down list, select Oracle.	In the Database Type section, select SQL Server, and then enter the database network port. In the Additional Connection Parameters field, enter any required connection strings. Enter the database login credentials. Enter the hostname of the database server. In the Preferred Cache Type drop-down list, select Generic.

16. (InfoDelivery only) On the Repository Database Information page, configure the connection to the Business Intelligence Repository database (BiRepos):

    Table 3-18 Repository Database Information

    Oracle Database

    Microsoft SQL Server

    In the Database Type section, select Oracle, and then enter the database network port and SID. Enter the login credentials to the Business Intelligence Repository database. Enter the login credentials to the Quartz Job Scheduler database. Enter the hostname of the Business Intelligence Repository database server. The information is typically filled by the installation wizard. Enter the externally-facing address for access to Enterprise Back Office. This is typically the published URL for Reporting and Analytics.

    In the Database Type section, select SQL Server, and then enter the database network port. Enter the login credentials to the Business Intelligence Repository database. Enter the login credentials to the Quartz Job Scheduler database. Enter the hostname of the Business Intelligence Repository database server. The information is typically filled by the installation wizard. Enter the externally-facing address for access to Enterprise Back Office. This is typically the published URL for Reporting and Analytics.

17. (InfoDelivery only) On the InfoDelivery Configuration page, enter login credentials to the CE database.
18. (Admin Server only) On the Posting/Admin Database Information page, enter the address to the server hosting the Aggregate Database server.
19. (Admin Server only) On the Posting/Admin Mail Server page, enter the mail domain, SMTP port, and POP3 port for the IceWarp Mail Server to be used by the Admin Server.
20. (Master Server only) On the Master Mail Server page, enter the mail domain, SMTP port, and POP3 port for the IceWarp Mail Server to be used by the Master Server.
21. (InfoDelivery only) On the InfoDelivery Mail Server page, enter the hostname of the IceWarp Mail Server or the server to host the InfoDelivery service, and then enter the SMTP port.
22. (InfoDelivery only) On the Portal/InfoDelivery Settings - Font page, you can configure custom fonts for InfoDelivery as described in the following table:

    Table 3-19 Report Mail Font Configurations

    Field	Description
    Enable User Font	Select whether to allow using a custom font when rendering PDFs. You can then enter the path to the font, or click Choose to navigate to the font.
    Limit detail query days	Enter a date limit for executing audit/analysis detail queries. The Organization configuration can override this setting.
    Limit summary query days	Enter a date limit for executing audit/analysis summary queries. The Organization configuration can override this setting.
    New Line Style for infoDelivery CSV format	Select whether to use Windows, Unicode, or HTML line styling when formatting Report Mail items in CSV.
    Load reports by market segment	Select whether to load reports dynamically by appending the organization or role market segment to the template name.

23. (Admin Server only) On the Admin Server Configuration page, enter the login credentials for the Admin Server database and the CEDB.
24. (InfoDelivery only) On the InfoDelivery Configuration page, enter the infoDelivery email login credentials for sending and receiving emails.
25. (InfoDelivery only) On the InfoDelivery page, leave the Pentaho Solutions Directory blank.
26. (Gift and Loyalty only) On the iCare Configuration for Portal page:
    1. Enter the URL for Gift and Loyalty campaigning. This is typically http://Gift and Loyalty URL:80/offers/
    2. Enter the URL for Gift and Loyalty Stored Value. This is typically the hostname of Gift and Loyalty.
    3. Enter the URL for Gift and Loyalty for RTA downloads. This is typically the hostname of Gift and Loyalty.
    4. Enter the database login credentials for the Gift and Loyalty database. This is typically the MMSQL account.
    5. Enter the URL of the ExactTarget WSDL file.
27. (Labor Management only) On the myLabor Configuration for Portal page, you can change the port number used for non-secure connections and SSL connections. Do not change the syntax.
    1. Non secure port for myLabor: -Dhttp.browser.port=port
    2. SSL port for myLabor: -Dhttp.sslaccel.port=port
28. (Inventory Management only) On the myInventory Settings for Portal page, select the Inventory Management database server type, enter the address and port of the database server, and then enter the external-facing published site URL for Inventory Management.
29. (Alert Engine only) On the Portal Specific Settings - Mobile page, enter the login credentials for the Alert Engine server.
30. (Master Server only) On the Master Server Configuration page, configure the Master Server as described in the following table:

    Table 3-20 Master Server Configurations

    Field	Description
    RTA database login and RTA database password	Enter the RTA database login credentials for inserting and updating the RTA_Processed_job table. The account must have full permissions on the database/schema.
    COREDB login and COREDB password	Enter the COREDB login credentials for file transport. The account must have the same level of permissions on the Core database/schema.
    Email account name for the Errors Administrator and Email account password	Enter the e-mail account credentials for the Error Administrator.
    Merak 8.5 or higher	Select whether Merak 8.5 or higher is installed on the environment.
    Where is the Merak installation located?	If Merak is installed on the environment, enter the installation path.
    Server1 account password	Enter the password for the server1 login account.
    Cache type for the Master Service	Select the Master Service cache type from the drop-down list.

31. (Posting Server only) On the Posting Server Configuration page, configure the Posting server as described in the following table:

    Table 3-21 Posting Server Configurations

    Field	Description
    How many posting threads should run on the server simultaneously?	Enter the number of simultaneous posting threads. Entering a number greater than eight can lead to performance degradation.
    How many days of psLogs should be saved?	Enter the amount of days that the posting server preserves the Result sets and the entries in the RTA_Processed_job table.
    What directory should hold psLogs?	Enter the path to the folder where the posting server saves the logs in .zip format.
    Move History by location rather than full server?	Select or deselect whether to move history by location rather than moving history by server. If you deselect this option, the admin server stops posting for the duration of the move.
    Limit move history day range	Select or deselect whether to limit moving history by date. You should typically only use this option when you partition databases by date.
    What name would you like to use for Temporary Menu Items?	Enter the name the posting server uses for temporary menu items.
    What database user should posting use?	Enter the database account name for posting.
    What is the password for this user?	Enter the database account password for posting.
    Run alignment with definitions posting?	Select or deselect whether to run alignment while posting definitions. Select this option if the environment contains an aggregation engine.

32. (Alert Engine only) On the Alert Engine Configuration page, configure the Alert Engine as described in the following table:

    Table 3-22 Alert Engine Configurations

    Field	Description
    Push alert service username and Push alert service password	Enter the login credentials for the push alert service.
    Number of alert threads	Enter the number of alert threads.
    Portal DB User and Portal DB Password	Enter the Enterprise Back Office database login credentials.
    Core DB User and Core DB Password	Enter the core database login credentials.
    Location Activity DB User and Location Activity DB Password	Enter the location activity database login credentials.
    RTA DB User and RTA DB Password	Enter the RTA database login credentials.
    CE DB User and CE DB Password	Enter the CE database login credentials.

33. (Admin Server only) On the Admin Server Configuration page, configure the Admin Server as described in the following table:

    Table 3-23 Admin Server Configurations

    Field	Description
    Trailer to send in alerts from Admin Server	Enter trailer text in the four fields provided.
    Email account to send alerts from	Enter the email name, without the domain, that the Admin Server uses to send alerts.
    Number of hours before a location is considered out of contact	Enter the maximum number of hours before the Admin Server flags an unresponsive location.
    Email addresses to send long alert messages to	Enter the email name, without the domain, to which the Admin Server sends long alert messages. You can separate multiple addresses with a comma.
    Email addresses to send short alert messages to	Enter the email name, without the domain, to which the Admin Server sends short alert messages. You can separate multiple addresses with a comma.
    Email addresses to send copies of org alerts to	Enter the email name, without the domain, to which the Admin Server sends a copy of all alerts.
    Folder containing custom packages for Admin Server	Enter a folder path containing custom packages.

34. (Aggregation and Adjustment only) On the Aggregation and Adjustment Configuration page, configure the database connection to the Aggregation and Adjustment service as described in the following table:

    Table 3-24 Aggregation and Adjustment Service Login

    Field	Description
    Core database login and Core database password	Enter the core database login credentials.
    RTA database login and RTA database password	Enter the RTA database login credentials.
    Portal database login and Portal database password	Enter the Enterprise Back Office database login credentials.
    Location Activity database login and Location Activity database password	Enter the location activity database login credentials.
    Name for Analysis/Aggregation Instance	Enter a unique name for this instance of the analysis/aggregation service. The service inserts the name into the database to denote which service processed a job.
    Connection Cache Type	Select a connection cache type from the drop-down list.

35. (Weather Service only) On the Weather Configuration page, configure the weather service as described in the following table:

    Table 3-25 Weather Configurations

    Field	Description
    What is the database login for the Weather Service?	Enter the username for the database login, typically MSSQL.
    What is the database password for the Weather Service?	Enter the password for the database login.
    How many days of weather should be stored in the database?	Enter the number of days of weather information that should be stored and retained in the database. Enter 0 to disable database storage.

36. On the Review page, select your preferred review type:

    • Normal: Review the install folder, features, and disk space requirements.

    • Advanced: Review and edit individual variables in the installation files, then review the install folder, features, and disk space requirements.

37. Review the Pre-Installation Summary, and then click Install.

Verifying the Reporting and Analytics Application Server Installation

1. Check the installation wizard logs for error, exception, and fail:

   • root\temp\MM_Log.log

   • root\temp\MMInstaller.log

   • root\myMicros\Uninstall_myMicros\Logs\myMicros_Install_datetime.log

2. Perform the following checks in the Oracle WebLogic console:
   1. In a web browser, navigate to OBI server hostname:7001/console and log in using the WebLogic administrator account credentials created during the installation.
   2. Click Environment from the menu, and then click Servers. Verify that you see appServ1 as Running.

      The status may be set to Starting if you check the WebLogic console immediately after completing installation. Verify that the status changes to Running.

   3. Click Deployments from the menu, click Customize this table, and then select Exclude libraries when displaying deployments. Verify that the portal component is set to Active.
   4. In the Domain Structure, click bifoundation_domain, click Security Realms, and then in the menu, click myrealm, click Providers, click Credential Mapping, click saml2CMP, and then click Management. Verify that obiee is listed.
3. Verify the following Microsoft Windows services are running:

   • beasvc bifoundation_domain_appServ1

   • Oracle WebLogic NodeManager(path to Oracle Middleware wlserver installation)