Sentinel Installation for Dummies

Sentinel Installation for Dummies


  1. Sentinel Database

    1.1. Service Pack 2

    1.2. Sentinel 6.0.0.0 SP2 Hotfix2

  2. Control Center / Correlation Engine

    2.1. Service Pack 2

    2.2. Sentinel 6.0.0.0 SP2 Hotfix2

  3. Sentinel Collector

    3.1. Service Pack 2

    3.2. Sentinel 6.0.0.0 SP2 Hotfix2

  4. Crystal Reports

    4.1. Installing Crystal for SQL Server 2005 with SQL Authentication

    4.2. Configuring ODBC for SQL Authentication

    4.3. Configuration for all Authentications and Configurations

    4.4. Patching Crystal Reports for use with Sentinel

    4.5. Report Installer on Windows:




1. Sentinel Database



Login as administrator user on Windows.
Start the install program by going to the install directory on the CD-ROM and , run setup.bat



Click the down-arrow and select one of the following language choices:





After reading the Welcome screen, click Next.



Read and accept End User License Agreement. Click Next.



Accept the default install directory or click Browse to specify your installation location. Click Next.



Select Custom. Click Next.



Select the components of Sentinel to install.



Select Microsoft SQL Server 2005 as target database server platform.



Select Windows Authentication



Specify the path for database



Select Install ASCII-only database.



Select Enable automatic database partitions to allow Sentinel Data Manager to handle database partitioning and archiving.




Users: esecdba, esecapp, esecadm, esecrpt
Password: Your password



Click Next. Summary screen with the features selected for installation will appear. Click Install.



Click Next. Summary screen with the features selected for installation will appear. Click Install.




















1.1. Service Pack 2



This Service Pack will apply the latest software fixes and enhancements to an existing installation of Sentinel 6.0 or Sentinel 6.0 SP1. Sentinel 6.0.0.0 must already be installed before applying this Service Pack, but SP1 is not necessary; SP2 is inclusive of all fixes and feature that are in SP1.

The Service Pack must be installed on all machines, client and server, with an existing Sentinel 6.0 or Sentinel 6.0 SP1 installation. This includes machines with Sentinel Server, the Correlation Engine, Sentinel Database, Collector Manager, Sentinel Control Center, Collector Builder, and Sentinel Data Manager.


To run the database patch script for database on MSSQL with SQL Authentication:


  1. Log into the database machine as the Windows Domain user that is the Sentinel Database User.


  2. Shut down the Sentinel Server processes (if this has not already been done).


  3. Extract the Service Pack ZIP file (if this has not already been done).


  4. Open a command prompt.


  5. Change directories to the following directory under the extracted Service Pack directory:

    db_patch\bin


  6. Enter the command:

    .\PatchDb.bat


  7. Follow the prompts and enter the following information:

    • Hostname or static IP address of the SQL Server Sentinel Database machine

    • SQL Server Database instance name, if any

    • Port number of the SQL Server database

    • Name of the SQL Server database to patch (ESEC by default).

    • 2 for the SQL Authentication option

    • Esecdba user’s password



    After you press Enter the final time, the script will verify the entered information and proceed if authentication is successful.


  8. Enter the language character set support option (1 for Unicode Database or 2 for ASCII Database). After you press Enter, the script will begin applying the database patch.




  9. After the script is done applying the patch, check for any errors. If there are errors, resolve the errors and re-run the PatchDb utility.




  10. After the patch runs with no errors, Sentinel services can be restarted.




1.2. Sentinel 6.0.0.0 SP2 Hotfix2




  1. Unzip the hotfix zip file.


  2. Stop the Sentinel service on this machine using the Windows Service Manager.


  3. Make a backup copy of ccsbase.jar, ccsapp.jar, dataobjects.jar, communications.jar, and contentinstaller.jar from %ESEC_HOME%\lib.

    ESEC_HOME is an environment variable that points to the directory where Sentinel is installed.

  4. Copy ccsapp.jar, ccsbase.jar, dataobjects.jar, communications.jar, and contentinstaller.jar from the unzipped hotfix folder into %ESEC_HOME%\lib.




  5. Follow the instruction on "Database Patch Installation on SQL Server" to patch SQL Server database.


  6. Start the Sentinel service on this machine using Windows Service Manager.


  7. For any Solution Packs that were created using a previous version of Sentinel, open them in Solution Designer and save again to include the updates in this hotfix. Then re-import the Solution Packs using Solution Manager.



To run the database patch script for database on MSSQL with SQL Authentication:


  1. Log into the database machine as user that has access to MSSQL database client tools.


  2. Shut down the Sentinel Server processes (if this has not already been done).


  3. Extract the Hotfix ZIP file (if this has not already been done).


  4. Open a command prompt.


  5. Change directories to the following directory under the extracted Hotfix directory:

    db_patch\bin


  6. Enter the command:

    .\PatchDb.bat

  7. Follow the prompts and enter the following information:



    • Hostname or static IP address of the SQL Server Sentinel Database machine

    • SQL Server Database instance name, if any

    • Port number of the SQL Server database

    • Name of the SQL Server database to patch (ESEC by default).

    • 2 for the SQL Authentication option

    • Esecdba user’s password



    After you press Enter the final time, the script will verify the entered information and proceed if authentication is successful.

  8. Enter the language character set support option (1 for Unicode Database or 2 for ASCII Database).



    After you press Enter, the script will begin applying the database patch.


  9. After the script is done applying the patch, check for any errors. If there are errors, resolve the errors and re-run the PatchDb utility.


  10. After the patch runs with no errors, Sentinel services can be restarted.








2. Control Center / Correlation Engine



Login as administrator user on Windows.
Start the install program by going to the install directory on the CD-ROM and , run setup.bat



Click the down-arrow and select one of the following language choices:



After reading the Welcome screen, click Next



Read and accept End User License Agreement. Click Next.



Click Browse to specify your installation location. Click Next.



Select Custom. Click Next.



Select the components of Sentinel to install.



If you select to install DAS, you will be prompted for: Serial Number License Key



If you chose to install Sentinel Control Center, the installer will prompt for the maximum memory space to be allocated to Sentinel Control Center. Enter the maximum JVM heap size (MB) you would want to be used only by Sentinel Control Center.



Click Next




If installing a component that will make a direct connection to the message bus or if installing Communication Server, you will be prompted for how to obtain the shared message bus encryption key: Generate random encryption key and save it, you’ll use it later.



Automatic Memory Configuration: Select the total amount of memory to allocate to Sentinel Server. The installer will automatically determine the optimal distribution of memory across components taking into account estimated operating system and database overhead.



Select Microsoft SQL Server 2005 as target database server platform.



SQL Server Configuration:




Click Next. Summary screen with the features selected for installation will appear. Click Install.









2.1.Service Pack 2



This Service Pack will apply the latest software fixes and enhancements to an existing installation of Sentinel 6.0 or Sentinel 6.0 SP1. Sentinel 6.0.0.0 must already be installed before applying this Service Pack, but SP1 is not necessary; SP2 is inclusive of all fixes and feature that are in SP1.



The Service Pack must be installed on all machines, client and server, with an existing Sentinel 6.0 or Sentinel 6.0 SP1 installation. This includes machines with Sentinel Server, the Correlation Engine, Sentinel Database, Collector Manager, Sentinel Control Center, Collector Builder, and Sentinel Data Manager.

To install the Service Pack:


  1. Login as an Administrator Windows.


  2. Extract the Service Pack zip file.


  3. Close all Sentinel applications running on this machine, including:


  4. Sentinel Control Center
    Sentinel Collector Builder
    Sentinel Data Manager

  5. Shut down Sentinel service running on this machine:
    On Windows, use Windows Service Manager to stop the “Sentinel” services.




  6. On the command line, return to the extracted Service Pack top level directory and run the service_pack script to start the Service Pack installer:

    .\service_pack.bat




  7. When prompted, press the <ENTER> key to start the Service Pack installation procedure.




  8. Repeat the steps above on every machine with Sentinel software installed. This is required for all machines with any Sentinel software, including Sentinel server and client software.


  9. This Service Pack also contains a mandatory patch to the Sentinel Database. Apply the database patch by performing the appropriate steps below for the database platform you are using.




2.2. Sentinel 6.0.0.0 SP2 Hotfix2




  1. Unzip the hotfix zip file.

  2. Stop the Sentinel service on this machine using the Windows Service Manager.

  3. Make a backup copy of ccsbase.jar, ccsapp.jar, dataobjects.jar, communications.jar, and contentinstaller.jar from %ESEC_HOME%\lib.

    ESEC_HOME is an environment variable that points to the directory where Sentinel is installed.

  4. Copy ccsapp.jar, ccsbase.jar, dataobjects.jar, communications.jar, and contentinstaller.jar from the unzipped hotfix folder into %ESEC_HOME%\lib.




  5. Follow the instruction on "Database Patch Installation on SQL Server" to patch SQL Server database.

  6. Start the Sentinel service on this machine using Windows Service Manager.

  7. For any Solution Packs that were created using a previous version of Sentinel, open them in Solution Designer and save again to include the updates in this hotfix. Then re-import the Solution Packs using Solution Manager.




3. Sentinel Collector



Login as administrator user on Windows.
Start the install program by going to the install directory on the CD-ROM and , run setup.bat



Click the down-arrow and select one of the following language choices:





Read and accept End User License Agreement. Click Next.



Click Browse to specify your installation location. Click Next.



Select method of connection to the message bus



You are prompted to enter Communication Server port/host name information. Enter the required information and click Next.


  • Message bus port: The port the message bus is listening on. This option is only displayed if Direct Message Bus type communication was selected.


  • Communication Server hostname: The hostname or IP of the machine where the Communication Server component is installed





Import keystore previously generated



You will be prompted to specify the amount of memory (RAM) to allocate to Collector Manager. The installer will factor in operating system overhead when determining what allocation options to display. There are two ways to specify memory allocation:

Automatic Memory Configuration: Select the total amount of memory to allocate to Collector Manager.



Click Install






3.1. Service Pack 2



This Service Pack will apply the latest software fixes and enhancements to an existing installation of Sentinel 6.0 or Sentinel 6.0 SP1. Sentinel 6.0.0.0 must already be installed before applying this Service Pack, but SP1 is not necessary; SP2 is inclusive of all fixes and feature that are in SP1.

The Service Pack must be installed on all machines, client and server, with an existing Sentinel 6.0 or Sentinel 6.0 SP1 installation. This includes machines with Sentinel Server, the Correlation Engine, Sentinel Database, Collector Manager, Sentinel Control Center, Collector Builder, and Sentinel Data Manager.


To install the Service Pack:


  1. Login as an Administrator Windows.

  2. Extract the Service Pack zip file.

  3. Close all Sentinel applications running on this machine, including:

    Sentinel Control Center

    Sentinel Collector Builder

    Sentinel Data Manager

  4. Shut down Sentinel service running on this machine:

    On Windows, use Windows Service Manager to stop the “Sentinel” services.




  5. On the command line, return to the extracted Service Pack top level directory and run the service_pack script to start the Service Pack installer:

    .\service_pack.bat




  6. When prompted, press the <ENTER> key to start the Service Pack installation procedure.




  7. Repeat the steps above on every machine with Sentinel software installed. This is required for all machines with any Sentinel software, including Sentinel server and client software.

  8. This Service Pack also contains a mandatory patch to the Sentinel Database. Apply the database patch by performing the appropriate steps below for the database platform you are using.




3.2. Sentinel 6.0.0.0 SP2 Hotfix2




  1. Unzip the hotfix zip file.

  2. Stop the Sentinel service on this machine using the Windows Service Manager.

  3. Make a backup copy of ccsbase.jar, ccsapp.jar, dataobjects.jar, communications.jar, and contentinstaller.jar from %ESEC_HOME%\lib.

    ESEC_HOME is an environment variable that points to the directory where Sentinel is installed.

  4. Copy ccsapp.jar, ccsbase.jar, dataobjects.jar, communications.jar, and contentinstaller.jar from the unzipped hotfix folder into %ESEC_HOME%\lib.




  5. Follow the instructions on "Database Patch Installation on SQL Server" to patch SQL Server database.

  6. Start the Sentinel service on this machine using Windows Service Manager.




  7. For any Solution Packs that were created using a previous version of Sentinel, open them in Solution Designer and save again to include the updates in this hotfix. Then re-import the Solution Packs using Solution Manager.





4. Crystal Reports




4.1. Installing Crystal for SQL Server 2005 with SQL Authentication



Launch Microsoft SQL Server Management Studio.
In the navigation pane, expand Databases.
Highlight and right-click Database and select New Database.
Under the Database name field, enter Sentinel_XI and click OK.



Exit Microsoft SQL Server Management Studio.

Insert the Crystal Reports XI R2 Server CD into the CD-ROM.
If Autoplay is disabled on your machine, run CRSXI_Autorun.exe.


Select the Crystal Reports setup language.

Click Install



Click Next



Read and accept End User License Agreement. Click Next.



Select Perform Server Installation, Click Next.



Product Keycode



Choose installation path D:\Program Files\Business Objects\



For install type, select Use an existing database server.



In the CMS Database Pane, click Browse.
Click the Machine Data Source tab. Click New.
Select System Data Source.
Click Next.



Scroll down and select SQL Server and click Next.



A new source will appear, click Finish.



In the New Data Source to SQL Server window, enter:
Name of your data source (Sentinel_XI)
Description (optional)
For Server, click the down arrow and select (local)

Click Next.



Select With SQL Server authentication, enter esecdba and the password. Click Next.



Check the Change the default database to: check box. Change your default database to Sentinel_XI.
Click Next.



In the Create a New Data Source to SQL Server window, click Finish.



Click Test Data Source. Click OK.






In the Select Data Source window, highlight Sentinel-XI and continue to click OK until you get to the SQL Server Login. Ensure that Use Trusted Connection is NOT selected. Click OK.



Click Next.



In the Web Component Adapter Type window, select IIS ASP.NET.



Click in Next.





Click Next



Click Finish to terminate installation




4.2.Configuring ODBC for SQL Authentication



This procedure sets up an ODBC data source between Crystal Reports on Windows and SQL Server. This has to be performed on the Crystal Server machine.

To Set up an ODBC data source for Windows:

  1. Go to Windows Control Panel > Administrative Tools > Data Sources (ODBC).

  2. Click System DSN tab and click Add.

  3. Select SQL Server. Click Finish.

  4. A screen appears prompting for driver configuration information:

    Data Source name, enter esecuritydb

    Description field (optional), enter a description

    Server field, (local).




    Click Next.

  5. In the next screen, select SQL Authentication. Enter esecrpt and password as the Login ID. Click Next.




  6. In the next screen select:

    Change the Sentinel database (Default name is ESEC)

    Leave all the default settings

    Click Next; click Finish.









  7. Click Test Data Source. On successful testing, click OK. Click OK until you exit.




4.3.Configuration for all Authentications and Configurations



The following procedures are required for Crystal Server to work with the Sentinel Control Center.


  1. Copy the web.config file from:

    C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Content to c:\Inetpub\wwwroot.




  2. Launch Internet Service Manager by clicking Start > Run. Enter inetmgr and click OK.





  3. Expand (local computer) > Web Sites > Default Web Site > businessobjects.



  4. On businessobjects, right-click > properties.




  5. Under Virtual Directory tab, click Configuration.




  6. You should have the following mappings. If not, add them. If you are going to add a mapping, do not click businessobjects or crystalreportsviewer11 nodes.






















    Extension Executable
    .csp C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
    .cwr C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
    .cri C:\Windows\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll
    .wis ...\BusinessObjects Enterprise 11.5



    Click OK to close the window.

  7. Restart IIS by expanding (local computer) > Web Sites > Default Web Site, high-light Default Web Site and right-click > Stop.


  8. Expand (local computer) > Web Sites > Default Web Site, high-light Default Web Site and right-click > Start Default.




4.4.Patching Crystal Reports for use with Sentinel



In order to view Crystal Reports from the Sentinel Control Center’s Analysis tab, several Crystal Enterprise files need to be updated to make them compatible with the browser.

To patch Crystal Reports:













File NameDescription
calendar.js
calendar.html
Displays a popup calendar when you are selecting a date as a parameter to a report.
grouptree.htmlDisplays the Loading... message while reports are loading.
exportframe.htmlDisplays the window that allows you to export a report for saving or for printing.
exportIce.htmlFile used by Sentinel when exporting a report for saving or for printing.
GetInfoStore.aspFile used to query the Crystal Server
GetReports.aspFile used by Sentinel Control Center to establish a connection with Crystal Server
and display the report list.
GetReportURL.aspFile used to support hyperlinks between reports.
helper_js.aspA call file used by GetInfoStore.asp.
publish_report.aspxUsed to publish reports directly from a Solution Pack to the Crystal server when a
control is installed.
delete_report.aspxUsed to remove reports directly from the Crystal server when a control is uninstalled.



  1. Download the Sentinel report patches.
    NOTE: It is strongly encouraged that the Sentinel Reports Release Notes be reviewed before performing this task. There may be updated files, scripts and additional steps.

  2. From within the Sentinel Reports Distribution, go to the “patch” directory and copy all *.html and *.js files to the viewer file location, default is:

    C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Web Content\Enterprise115\viewer\en




  3. From within the Sentinel Reports Distribution, go to the “patch” directory and copy all *.asp and *.js files to: C:\inetpub\wwwroot




  4. NOTE: Your web folder may be on a different drive or in a different location than specified above.

  5. Create a Sentinel subdirectory in the Crystal installation directory. In a default installation, the path will be:

    C:\Program Files\BusinessObjects Enterprise 11.5\Web Content\Enterprise115\WebTools\Sentinel

  6. Place the publish_report.aspx and delete_report.aspx in the Sentinel directory.




  7. Open the web.config file in the Crystal install directory for editing.




  8. Add two new entries to the <assemblies> section of the web.config file for Enterprise.PluginManager and Enterprise.Desktop.Report. The following example shows a sample <assemblies> section:



    <compilation defaultLanguage="c#" debug="false">
<assemblies>
<add assembly="CrystalDecisions.Enterprise.PluginManager, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Enterprise.Desktop.Report, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.CrystalReports.Engine, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.ReportSource, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Shared, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Web, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Enterprise, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Enterprise.Framework, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Enterprise.InfoStore, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
<add assembly="CrystalDecisions.Enterprise.Shared, Version=11.5.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" />
</assemblies>
</compilation>





4.5.Report Installer on Windows:



Go to D:Program Files\Business Objects\2008-01-10_SENTINEL_6.0.0.0_REPORTS




  1. Open a command line prompt.

  2. Navigate to the folder where the reports were unzipped:

    <Extracted_Directory>\

  3. Enter the following command:

    .\ReportInstaller.bat




  4. Enter the computer name of the system where the Crystal Management Server is installed. If installing on the local machine, do not use 127.0.0.1 or localhost. Instead, enter the DNS name or IP address.




  5. Enter the password for the Administrator user in Crystal Management Server (CMS).




  6. Enter the path to an existing directory where your EsecCrystallog.log file should be located. This log file will have entries of publishing and scheduling events written during installation. The installer will not create folders for you.





  7. Enter the action you wish to take: publish, schedule or both (schedules and publish).




  8. Type of database MS SQL.

  9. If using a Microsoft SQL Server database, you will be prompted to select Windows Authentication or SQL Server Authentication.

  10. If scheduling reports, you will be asked for the Sentinel database password for the esecrpt database user for SQL authentication or the Novell Report User for Windows authentication will appear.





Successful Installation



Good luck!!

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments

4.4.Patching Crystal Reports for use with Sentinel

  • 1. Download the Sentinel report patches.



From there, you may want to refer to the Solution Pack "Sentinel-Core_6.1r1.spz.zip"


Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2008-06-11 20:02
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.