The following procedures must be followed for Crystal Reports Server to work with the Sentinel Control Center:
If the Sentinel Database is not on the same machine as the Crystal Reports Server, then you must install the Oracle Client software on the Crystal Reports Server machine. This additional step is not needed if the Sentinel Database is on the same machine as the Crystal Reports Server because in this case the required Oracle software is already installed during the Oracle database installation.
Login to the Crystal Reports Server machine as the root user
Create bobje group
groupadd bobje
Create Crystal user (the home directory in this example is /export/home/crystal, change if needed; the /export/home part of the path must already exist).
useradd –g bobje –s /bin/bash –d /export/home/crystal –m crystal
Create directory for Crystal Software:
mkdir –p /opt/crystal_xir2
Change the ownership of the Crystal Software directory (recursively) to crystal/bobje:
chown -R crystal:bobje /opt/crystal_xir2
You must grant permissions to the crystal user on the $ORACLE_HOME directory using an Access Control List (ACL). Assuming the crystal user is crystal and $ORACLE_HOME is /opt/oracle/product/10.2/db_1, the command to perform this is:
setfacl -m u:crystal:rx -R /opt/oracle/product/10.2/db_1
To verify that the ACL was set correctly, run the following command and check for “crystal” in the output:
getfacl /opt/oracle/product/10.2/db_1
Add the crystal user to the oracle group using the following command:
groupmod -A crystal oinstall
This enables the crystal user to communicate with the Oracle database and execute Oracle utilities like sqlplus and tnsping.
Change to the crystal user:su - crystal
The ORACLE_HOME environment variable must be set in the crystal user’s environment. To do this, modify the crystal user’s login script to set the ORACLE_HOME environment variable to the base of the Oracle software. For example, if the crystal user’s shell is bash and the Oracle software is installed in the directory /opt/oracle/product/10.2/db_1, then open the file ~crystal/.bash_profile (.profile on SLES) and add the following line to the end of the file:
export ORACLE_HOME=/opt/oracle/product/10.2/db_1
The LD_LIBRARY_PATH environment variable in the crystal user’s environment must contain the path to the Oracle software libraries. To do this, modify the crystal user’s login script to set the LD_LIBRARY_PATH environment variable to include the Oracle software libraries. For example, if the crystal user’s shell is bash, then open the file ~crystal/.bash_profile and add the following line to the end of the file (below where the ORACLE_HOME environment variable is set):
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
The PATH environment variable in the crystal user’s environment must contain the path to the Oracle software executables. To do this modify the crystal user's script to set the PATH environment variable to include the Oracle software executables. For example if the crystal user's shell is bash, then open the file ~crystal/.bash_profile and add the following line to the end of the file.
export PATH=$PATH:$ORACLE_HOME/bin
An entry must be added to the Oracle tnsnames.ora file with the Service Name esecuritydb that points to the Sentinel Database. To do this on the Crystal Reports Server machine:
Log in as the oracle user.
Change directories to $ORACLE_HOME/network/admin
Make a backup of the file tnsnames.ora.
Open the file tnsnames.ora for editing.
If the Sentinel Database is on the Crystal Reports Server machine, then there should already be an entry in the tnsnames.ora file to the Sentinel Database. For example, if the Sentinel Database is named ESEC, then an entry similar to the following will exist:
ESEC = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dev-linux02)(PORT = 1521)) ) (CONNECT_DATA = (SID = ESEC) ) )
If the Sentinel Database is not on the Crystal Reports Server machine, open the tnsnames.ora file on the Sentinel Database machine to find the entry described above.
Make a copy of that entire entry and paste it at the bottom of the tnsnames.ora file on the Crystal Reports Server machine. The Service Name part of the entry must be renamed to esecuritydb. For example, when the entry above is copied and renamed properly, it will look like:
esecuritydb = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = dev-linux02)(PORT = 1521)) ) (CONNECT_DATA = (SID = ESEC) ) )
Make sure the HOST part of the entry is correct (for example, make sure it is not set to localhost if the Crystal Reports Server and Sentinel Database are on different machines).
Save the changes to the tnsnames.ora file.
Execute the following command to check that the esecuritydb Service Name is configured properly:
tnsping esecuritydb
After the command is executed, you will get a message saying the connection is OK.
The Crystal Reports Server installer consists of two .iso files. During the installation, you will be prompted for the location of the second disk.
Log in as crystal user.
Change directories into disk1 of the Crystal installer.
Execute:
./install.sh
Select Language: English
Select New Installation.
Read and accept License Agreement.
Provide Product Keycode.
Provide install directory:
/opt/crystal_xir2
Select: User install.
Select: New Install.
Select: Install MySQL unless you plan to install the Crystal CMS database into an existing database.
Specify configuration information for MySQL:
Use default port 3306
Admin password
Specify more configuration information for MySQL:
Default DB Name: BOE115
User id: mysqladm
Password
Specify more configuration information for MySQL:
Local Name Server: <local machine’s hostname>
Default CMS Port Number: 6400
Select: Install Tomcat
Specify Tomcat configuration information:
Default Receive HTTP requests port: 8080
Default Redirect jsp requests port: 8443
Default Shutdown Hook port: 8005
Press Enter to confirm the default directory.
Press Enter to start installation.
Note the link to the CMS server, which will probably be something similar to this:
http://<hostname>:8080/businessobjects/enterprise115/adminlaunch/launchpad.html
NOTE:After Crystal Reports Server is installed, you must download and install the Sentinel Core Solution Pack, the Sentinel Core Solution Pack includes both report templates and files necessary to patch Crystal. The installation instructions are included in the Solution Pack documentation.on the Sentinel Content Web site.
To view Crystal Reports from the
tab of the Sentinel Control Center and to publish the reports from Solution Manager, several Crystal Enterprise files need to be updated to make them compatible with the browser.The following table lists the Crystal Reports Enterprise files and describes the purpose of each file. The Crystal Reports Enterprise files can be extracted from the crystal_patch.zip file, which is available as an attachment in the Sentinel Core Solution Pack under the control.
Table 8-1 Crystal Enterprise Files
To patch crystal reports server:
NOTE:Ensure that you have read the Sentinel Reports Release Notes before performing this task as there can be updated files, scripts, and additional steps that need to completed.
Log in to the Crystal Reports Server machine as crystal user.
Extract the Crystal Enterprise files from the crystal_patch.zip file to a local directory.
Create the directory structure esec-script/WEB-INF/lib at the following location:
/opt/crystal_xir2/bobje/tomcat/webapps/
In the patch directory under Sentinel Reports Distribution, copy all *.html and *.js files to the viewer file location, the default location is:
Copy all *.html and *.js files to the viewer file location, the default location is:
/opt/crystal_xir2/bobje/webcontent/enterprise115/viewer/en/
Copy all *.jsp files at:
/opt/crystal_xir2/bobje/tomcat/webapps/esec-script/
NOTE:The publish_report.aspx and delete_report.aspx files are available in the reports_patch\Tomcat directory of the Sentinel 6 SP2 distribution or in the Sentinel Reports distribution.
Set the permissions and ownership for the publish_report.jsp and delete_report.jsp files as following:
-rwxr-xr-x 1 crystal bobje
Copy all *.jar files:
From:
/opt/crystal_xir2/bobje/tomcat/webapps/jsfadmin/WEB-INF/lib/
To:
/opt/crystal_xir2/bobje/tomcat/webapps/esec-script/WEB-INF/lib
If Crystal was installed in a non-default location or as system install, modify the String BOBJHome setting in publish_report.jsp and delete_report.jsp files to the Crystal Reports installation path. For example:.
String BOBJHome = "/opt/crystal_xir2/bobje/enterprise115"
If Crystal was installed as the designated Crystal user into the default location, no changes should be necessary to this parameter.
Restart the Web Server and the Crystal Reports server.