Installing Reporting and Analytics

1. If you are installing Reporting and Analytics on different drive than Portal WebLogic AdminServer, change the drive letter for the following properties in the server microsConfig.properties file on Portal WebLogic AdminServer and then redeploy the portal using the WebLogic Admin server console:

   myInsightRootDir=Drive:/myMicros/myInsight

   reportDefPath=Drive:/myMicros/myInsight/org

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

2. Extract the following from the installation file archive. Do not extract the files to a folder structure that contains spaces.

   /Weblogic/

   Install_version.exe

3. Double-click Install_version.exe.
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 or database service name 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.
6. On the Use existing Portal configuration page:
   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 Managed Server.
8. On the WebLogic Info page, configure the application server settings:

   Table 4-5 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.
   WebLogic Admin Server Host Name and WebLogic Admin Server Port	Enter the name of the server that hosts Portal WebLogic AdminServer.
   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.

9. On the App Server name page, you can change the name of the Reporting and Analytics instance being installed if you want to apply a naming convention.
10. 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.
11. 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.

12. Review the Pre-Installation Summary, and then click Install.
13. Verify the installation as described in Verifying the Reporting and Analytics Installation.
14. Install patch 9.1.35 or higher.
15. For 9.1, 9.1 with OBIEE, and 9.1 New Tech Stack with Pentaho release installations and if Pentaho Interactive Reports are in use, install the Pentaho Patch Package.
16. For 9.1 New Tech Stack and 9.1 New Tech Stack with Pentaho release installation details, see WebLogic Configuration for Enterprise Back Office.

• Verifying the Reporting and Analytics Installation
  

Verifying the Reporting and Analytics 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, go to the console and log in using the WebLogic administrator account credentials created during the installation.
   2. Click Environment from the menu, and then click Servers.
   3. Start the HOSTNAME_appServ1 service, where:

      • HOSTNAME is the name of the host server.

      • appServ1 is the default name of the Reporting and Analytics application server instance. If you changed the default name when you installed Reporting and Analytics, that name appears instead of the default.

   4. 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.
3. Verify the following Microsoft Windows services are running:
   For the 9.1 or 9.1 with OBIEE release:

   • beasvc_bifoundation_<HOSTNAME>_appServ1.

   • Oracle WebLogic NodeManager (<Path to Oracle Middleware wlserver installation>)

   For the 9.1 New Tech Stack or 9.1 New Tech Stack with Pentaho release:

   • wlsvc bifoundation_domain_<HOSTNAME>_appServ1

   • Oracle Weblogic bifoundation_domain NodeManager