Thursday, September 23, 2010

Enabling and disabling tracing in XI 3.1 for specific services without requiring a restart - UNIX

In order to activate traces on Unix, you have to create with a name following the array below and copy it in [BusinessObjects install folder]\bobje or the current working directory of the command that started your servers.

Process to monitor

File Name

AAAnalytics

AAAnalytics_trace.ini

AADMining

AADMining_trace.ini

AADashboard

AADashboard_trace.ini

AAMetrics

AAMetrics_trace.ini

AAProfiler

AAProfiler_trace.ini

AAQueryMgr

AAQueryMgr_trace.ini

AARepoMgt

AARepoMgt_trace.ini

AARules

AARules_trace.ini

AASPC

AASPC_trace.ini

CMS

boe_cmsd_trace.ini

ConnectionServer

ConnectionServer_trace.ini

EventServer

boe_eventsd_trace.ini

JobServerChild

boe_jobcd_trace.ini

JobServer

boe_jobsd_trace.ini

WIReportServer

WIReportServer.bin_trace.ini

crcache

boe_crcached.bin_trace.ini

crproc

boe_crprocd.bin_trace.ini

crystalras

boe_crystalrasd.bin_trace.ini

fccache

boe_fccached_trace.ini

fcproc

boe_fcprocd_trace.ini

fileserver

boe_filesd_trace.ini

The file should contain the following text lines.

active = true;
importance = xs;
alert = true;
severity = 'E';
keep = true;
size = 100 * 1000;
//log_dir="/var/logs"; Any other folder you might want, default: bobje/logging

Process to monitor

File Name

RESULT

AAAnalytics
XI 3.1 Name : DashboardAnalyticsServer

AAAnalytics_trace.ini

OK

AADMining
XI 3.1 Name : PredictiveAnalysisServer

AADMining_trace.ini
Correct Name :AADMining.bin_trace.ini

OK but not pick up logs folder
OK

AADashboard
XI 3.1 Name : DashboardServer

AADashboard_trace.ini

OK

AAMetrics
XI 3.1 Name : PMMetricsServer

AAMetrics_trace.ini

OK

AAProfiler
XI 3.1 Name : SetsProfileServer

AAProfiler_trace.ini

OK

AAQueryMgr
XI 3.1 Name : SetsQueryServer

AAQueryMgr_trace.ini

OK

AARepoMgt
XI 3.1 Name : PMRepositoryServer

AARepoMgt_trace.ini

OK

AARules
XI 3.1 Name : PMRulesServer

AARules_trace.ini

OK

AASPC
XI 3.1 Name : ProcessAnalysisServer

AASPC_trace.ini

OK

CMS

boe_cmsd_trace.ini

OK

ConnectionServer

ConnectionServer_trace.ini

OK

EventServer

boe_eventsd_trace.ini

OK

JobServerChild

boe_jobcd_trace.ini

OK

JobServer

boe_jobsd_trace.ini

OK

WIReportServer

WIReportServer.bin_trace.ini

OK

crcache

boe_crcached.bin_trace.ini

OK

crproc

boe_crprocd.bin_trace.ini

OK

crystalras

boe_crystalrasd.bin_trace.ini
boe_crystalrasd_trace.ini
boe_crystalras_trace.ini

NO
NO
NO

fccache

boe_fccached_trace.ini

OK

fcproc

boe_fcprocd_trace.ini

OK

fileserver

boe_filesd_trace.ini

OK

RESULTS: On UNIX some of the file names for the trace files must be different from those shown above as the process names are different on UNIX. The PM servers have different names in the XI 3.1 CMC than they are XI R2 name (both UNIX and Windows).

All tests included settings an alternate log directory.

Stopping tracing

To deactivate tracing (Windows and Unix) you will need to set the active variable (in .ini file)to false. Deleting the .ini file will not stop the tracing.

Once the ini file with the active variable set to false is read again (within a minute) you can remove the file.

Enabling and disabling tracing in XI 3.1 for specific services without requiring a restart - WINDOWS

You cannot activate traces by only modifying the default BO_trace.ini


Windows

In order to activate traces on Windows, you have to create a file with a name following the array below and copy it in [BusinessObjects install folder]\BusinessObjects Enterprise 12.0\win32_x86

Process to monitor

File Name

AAAnalytics

AAAnalytics_trace.ini

AADMining
AADMining : XI 3.1 Name PredictiveAnalysisServer

AADMining_trace.ini

AADashboard

AADashboard_trace.ini

AAMetrics

AAMetrics_trace.ini

AAProfiler

AAProfiler_trace.ini

AAQueryMgr

AAQueryMgr_trace.ini

AARepoMgt

AARepoMgt_trace.ini

AARules

AARules_trace.ini

AASPC

AASPC_trace.ini

CMS

CMS_trace.ini

ConnectionServer

ConnectionServer_trace.ini

EventServer

EventServer_trace.ini

JobServerChild

JobServerChild_trace.ini

JobServer

JobServer_trace.ini

WIReportServer

WIReportServer_trace.ini

busobj

busobj_trace.ini

crcache

crcache_trace.ini

crproc

crproc_trace.ini

crystalras

crystalras_trace.ini

designer

designer_trace.ini

fccache

fccache_trace.ini

fcproc

fcproc_trace.ini

fileserver

fileserver_trace.ini

The file should contain the following text lines.

active = true;
importance = xs;
alert = true;
severity = 'E';
keep = true;
size = 100 * 1000;
// Any other folder you might want, default [bobj]/BusinessObjects Enterprise 12.0/logging
//log_dir="C:/Temp";

WebIntelligence Rich Client

For the WebIntelligence Rich Client traces, you need to copy the WebIRichClient_trace.ini in "[BusinessObjects install folder]\"
The WebIntelligence Rich Client traces will be generated by default in the folder: "C:\Documents and Settings\\My Documents\My Business Objects Documents\LocData"

All tracing on Windows were started correctly using the above file names and were activated without requiring a restart
This included changing the log directory.

Business Objects tips/ qury builder

http://wwwbusinessobjectstips.com/tips/

http://blogshexaware.com/business-objects-boogle/business-objects-query-builder-part-ii/

http://blogs.hexaware.com/business-objects-boogle/business-objects-query-builder/

Wednesday, April 28, 2010

crpetrace parameters








The 7 option above can also be replaced with the following options
-crpetrace , means trace only CRPE functions
-crpetrace 1, means trace only CRPE functions
-crpetrace 2, means trace only CRPE background thread
-crpetrace 3, means trace both CRPE functions and CRPE background thread
-crpetrace 4, means trace internal CRPE diagnostics
-crpetrace 7, means trace CRPE functions and CRPE background thread and internal CRPE diagnostics

BO XI Audit DB setup

Following 6 tables are required to create a Audit report.

APPLICATION_TYPE,
AUDIT_DETAIL,
AUDIT_EVENT,
DETAIL_TYPE,
EVENT_TYPE,
SERVER_PROCESS

Query to pull the date:

SELECT AUDIT_EVENT.EVENT_ID,
AUDIT_EVENT.USER_NAME,
AUDIT_EVENT.START_TIMESTAMP,
AUDIT_EVENT.DURATION,
DETAIL_TYPE.DETAIL_TYPE_DESCRIPTION,
SERVER_PROCESS.SERVER_FULLNAME,
AUDIT_EVENT.ERROR_CODE,
AUDIT_DETAIL.DETAIL_TEXT,
EVENT_TYPE.EVENT_TYPE_DESCRIPTION
FROM
AUDIT_EVENT,
DETAIL_TYPE,
SERVER_PROCESS,
AUDIT_DETAIL,
EVENT_TYPE
WHERE ( AUDIT_EVENT.EVENT_ID=AUDIT_DETAIL.EVENT_ID ) AND ( AUDIT_EVENT.SERVER_CUID=SERVER_PROCESS.SERVER_CUID ) AND ( AUDIT_EVENT.EVENT_TYPE_ID=EVENT_TYPE.EVENT_TYPE_ID ) AND ( AUDIT_DETAIL.DETAIL_TYPE_ID=DETAIL_TYPE.DETAIL_TYPE_ID )


Universe Design:

Using -maxChildReqs Business Objects Enterprise XI R2 Report Job server settings

• The default report job server children for Windows have been changed in
BusinessObjects Enterprise XI from OUTPROC to MIXEDPROC. This
causes the report job server children to remain open longer after
processing (for the lesser of 100 jobs or 2 hours of not being used.). This
is now consistent with the UNIX report job servers and with the other
types of job servers included with BusinessObjects Enterprise.
The following lists information on job server settings:
• -maxJobs
Sets the maximum number of concurrent jobs processed by one job
server.
• -type
Presets the job server type. Can be OUTPROC or MIXEDPROC.
OUTPROC causes the job server children to shutdown after every
job (like CE10 report job servers), MIXEDPROC causes the job
server children to shutdown after every 100 jobs.
• -maxChildReqs
Sets the maximum number of jobs processed by one job server child
before it shuts down and restarts (in case you want a to use a
number between 1 [OUTPROC] and 100 [MIXEDPROC])
Job server children will also automatically shut down if left unused for a
period longer than 2 hours.


Example to use in Linux or Unix for BO XI R2:

Open the ccm.config file and change like below:

reportjobserverLAUNCH='"/bobje/enterprise115/generic/bobjrestart.sh" -protect "/bobje/enterprise115/linux_x86/boe_jobsd" -lib procreport -jsTypeDescription "Crystal Reports Job Server" -objectType CrystalEnterprise.Report -name xxxxxxxx.reportjobserver -ns xxxxxxxxx..com -type OUTPROC -loggingPath "/bobje/logging" -pidFile "/bobje/serverpids/xxxxxx_reportjobserver.pid" -restart -fg -maxChildReqs 1'


For XI R3 follow same instruction but do the changes from CMC to report job server.

For windows follow this video:

http://www.youtube.com/watch?v=WQ8R477SRIA

Friday, March 5, 2010

BO XI R2 Architecture Diagram

The client tier includes:
• InfoView
• Central Management Console (CMC)
• Central Configuration Manager (CCM)
• Publishing Wizard
• Import Wizard

Application Tier includes:
Java platform
•Windows .NET platform
The intelligence tier includes the following components:
• Central Management Server (CMS)
• Event Server
• File Repository Servers
• Cache Server

The processing tier includes:
• Job servers
• Report Job Server
• Program Job Server
• Web Intelligence Job Server
• Destination Job Server
• List of Values Job Server
• Desktop Intelligence Job Server
• Web Intelligence Report Server
• Report Application Server (RAS)
• Page Server

Data tier includes:
Semantic Layers
•Connection Server

BI Architecture diagram

Monday, March 1, 2010

Unable to find installed locale for en_US.UTF-8, en_US.utf8 .. While installing BO XI R2, BOXI 3.1(Linux)

Solution: Add following 2 lines to your bash profile

$ vi .bash_profile
LANG="en_US.utf8"
export LANG

logoff and login or type following command:

$ source .bash_profile





Enabling Auditing on Business Objects XIR2

1. Use ccm.sh to stop the CMS.

./ccm.sh –stop cms

2. Run cmsdbsetup.sh.

./cmsdbsetup.sh

3. Choose the selectaudit option, and then supply the requested information about your database server.

4. Run serverconfig.sh.

./serverconfig.sh

5. Choose the “Modify a server” option.

6. Select the CMS, and enable auditing. Enter the port number of the CMS when prompted (the default value is 6400).

7. Use ccm.sh to start the CMS. When the CMS starts, it will create the auditing database.

Enabling trace on Servers - Business Objects XIR2

1. Go to Directory bobje>

2. Open CCM.CONFIG file using vi editor (i.e., vi ccm.config)

3. Go to respective server line and add the –trace at the end of line like shown below.

4. Restart the server using command ./ccm.sh -start

Example:

cmsLAUNCH='"/bobje/enterprise115/generic/bobjrestart.sh" -protect "/bobje/enterprise115/linux_x86/boe_cmsd" -name xxxxxx.cms -loggingPath "/bobje/logging" -pidFile "/bobje/serverpids/boadmin_cms.pid" -restart -noauditor -fg -trace'

5. Look for Log files under >businessobjects>bobje>logging

Add, Delete or Modifying a Server in Business Objects XIR2 - Linux Environment

Path: /

./serverconfig.sh

---------------------------------------------------------

Business Objects

What would you like to do?

1 - Add a server

2 - Delete a server

3 - Modify a server

4 - List all servers in the config file

Select appropriate option to add, delete or modify the servers.

List of Servers:

cms (boe_cmsd)

pageserver (boe_pagesd)

cacheserver (boe_cachesd)

input (boe_filesd)

output (boe_filesd)

deskijobserver (boe_jobsd)

destjobserver (boe_jobsd)

lovjobserver (boe_jobsd)

reportjobserver (boe_jobsd)

programjobserver (boe_jobsd)

webijobserver (boe_jobsd)

eventserver (boe_eventsd)

ras (boe_crystalrasd)

webi (WIReportServer)

ConnectionServer (ConnectionServer)

fccacheserver (boe_fccached)

fcprocserver (boe_fcprocd)

After selecting the server it will ask for CMS name

Give the id and password for CMS: Ex: id: administrator password: xxxxxxxx

Start the server which you just added like below example:

./ccm.sh –start reportjobserver2

Enable the server after starting the server :

./ccm.sh -enable .reportjobserver2 -cms -username administrator -password xxxxxx -authentication enterprise

Sonarqube Upgrade from 9.4.4 to 9.9.4 LTS

 Issue:  1) Java hasbeen upgraded from 11 to Open JDK 17. And Sonarqube is upgraded from 9.4 to 9.9.4. 2) After the upgrade sonarqube servic...