Archive

Archive for the ‘Business Objects Administration’ Category

Scheduling in Business Objects xi 3.1

Scheduling:

Introduction:

This feature from business objects is used to schedule reports to run at particular time and destination.This would be useful for the users in times if they don’t want to sit before the system and run the reports each and every time. There are many options on how scheduling can be done.We can specify the objects and times individually through scheduling options. Objects in the sense, it can be a crystal reports, web intelligence reports, desktop intelligence reports, and publications etc.

Scheduling Options:

Whenever a schedule occurs accordingly an instance will be created, instance title is the first option in scheduling, where we enter the title for that instance.

Recurrence option is used to set the recurrence pattern on how to run the objects repeatedly over a period of time. The recurrence options are like NOW, ONCE, HOURLY, WEEKLY etc. whenever we choose these options corresponding day and time settings will come as sub options, where we can set the time and day of week.

Notifications can be done whether the scheduled job has been run successfully or failed to run. The notifications can be an audit or an Email.

Formats available for output may differs for different object like , in crystal reports formats available are more than the output formats of web intelligence Report.

Destinations may be user’s inbox, a file location, FTP server and through email recipients. Each destinations can be configured individually or can take the option as “use the job server’s default” where it can take the setting from corresponding job server’s destinations.

Scheduling can be also done through events and calendar; where there are three events namely,

  • File
  • Custom
  • Scheduled

These options are used to trigger the schedule when some particular event happens. The other one calendar is used to schedule on custom days and months.

Events:

Events can be created in three types in business objects Enterprises 3.1 , as mentioned in scheduling they are

  • File
  • Custom
  • Schedule

Custom: This type of events is used for manual triggering from the user side. To create a custom event,

In CMC go to Events

Click new à new Event, select the typeand click OK.

File: This event keeps track of particular directory, when the file which is specified in the file event properties is created, the event will be automatically triggered.

For Example, C:/sample/test.txt is the file name specified in file event, if a file named “test.txt” is created in this directory will trigger the event.

Schedule:This type of event is used on some conditional basis like dependency reports.

For example, if report1.rpt runs successfully then run some group of reports.

Instance Manager:

This tool is used to view all the instances which are created on running a scheduled object by the job server.

The instances can be viewed on its status:

  • success
  • failure
  • pending
  • running

The instance can also be viewed in specified time and date, by using the “completion time” option from instance manger, where we can specify the time and date the object that has completed successfully.

The other way of viewing the instance is by selecting the history of individual objects, like for a report if history is selected, it will show the instance for that report alone.

Calendars:

This tool from CMC is used to create a basic custom calendar which would be used for scheduling purposes.

To create a new calendar and open calendars in CMC then,

Click Manage > New > New Calendar.

Type a name and description for the new calendar and Click OK

Run dates can now be added to the calendars. Add the new dates and save the calendar, now it is ready to be used for scheduling based on custom calendars.

Monitoring Probe in Business objects XI 3.1 sp3

To be aware of the state of a system or to determine the health check of Business Objects system, we need monitoring,

Monitoring in Business Objects can be done in System and application level,   which is focused on availability, functionality, and performance of Business Objects services.

 Steps in deploying a monitoring probe in BO:

  1. Download the Business Objects Enterprise Monitoring Add-on at http://labs.businessobjects.com (or) http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/409109ca-94f4-2b10-1f8e-dc3960c2771c
  2. The downloaded package has monitoring.zip file, Extract the zip file to the root directory in the following manner.
  • A monitoring.jar file to <BO_INSTALL_DIR>\common\4.0\java\lib
  • A monitoring.war file to <BOE_INSTALL_DIR>\BusinessObjects

Enterprise 12.0\java\applications

  • A monitoring folder to <BO_INSTALL_DIR> (the BusinessObjects root directory).

BO Installation

<BO_INSTALL_DIR> =” C:\Program Files\Business Objects\monitoring\”

<BOE_INSTALL_DIR> =” C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\”

Deploying the monitoring probes package on Windows

  1. Open the monitoring.bat file in a text editor from the directory, “C:\Program Files\Business Objects\BusinessObjects\monitoring\monitoring.bat”
  2. Edit the monitoring.bat file  in a text editor to check the BOE_HOME and JAVA_DIR variables are set to their root installation directories like below

@echo off

rem ———————————————————————————

rem —————- MODIFY THESE VARIABLES —————————–

rem —- BOE_HOME : root folder of your Business Objects Enterprise installation —

set BOE_HOME=C:\Program Files\Business Objects

rem —- JAVA_DIR : root folder of your JDK

set JAVA_DIR=%BOE_HOME%\javasdk

3. Save and Exit the file

Monitoring Probes

 There are eight monitoring probes that can be used to monitor different aspects of  BusinessObjects system:

  • CMS Logon Logoff probe
  • Crystal Reports Service through Page and Cache Server probe
  • Crystal Reports Service through Report Application Server probe
  • Desktop Intelligence Service probe
  • Web Intelligence Service probe
  • CMS Ping probe
  • CMS Cache probe
  • CMS Database Connection probe

2. Each probe can be activated by editing its configuration files according to BO. Locate the configuration file of CMS Logon Logoff probe in the following directory,

“C:\Program Files\Business Objects\monitoring\probes”

3. A xml file named template_probe1 is the configuration file for CMS Logon Logoff Probe, open the template_probe1.xml in a text editor and edit the following,

<!–Copyright (c) 2008 Business Objects. All rights reserved. Business Objects Confidential. Unauthorized reproduction or disclosure prohibited. If you believe this file was obtained or published without permission, contact Business Objects, Attn: Contracts bobjuser, 3030 Orchard Parkway, San Jose, California 95134.–>

<probeconfig user=’bobjuser’ password=’bobjpassword’ system=’servername’ authtype=’secEnterprise’ classname=’ProbeLogonLogoff’>

</probeconfig>

To this,

<probeconfig user=’Administrator’ password=” system=’dinesh-pc’ authtype=’secEnterprise’ classname=’ProbeLogonLogoff’> </probeconfig>

4. Similarly, edit the configuration files for all the eight probes.

Update the Monitoring.war file

1. Now, locate the updateWar.bat file in this directory “C:\Program Files\Business Objects\BusinessObjects\monitoring\updateWar.bat” and check the BOE_HOME variable is set to BO root installation directory, like below.

rem —- BOE_HOME : root folder of your Business Objects Enterprise installation —-

set BOE_HOME=C:\Program Files\Business Objects

2. Execute the updateWar.bat to update the monitoring file.

Running a monitoring probe

 To run the probe in command mode:

  • From the monitoring directory (C:\Program Files\Business Objects\Monitoring), run the monitoring command in command prompt as Monitoring.bat –probefile template_probe1.xml, calling the CMS Logon Logoff probe configuration file.

 To run the probe in web mode:

1. Stop the Tomcat service.

2. Copy the monitoring.war file from C:\Program Files\BusinessObjects\BusinessObjects Enterprise 12.0\java\applications to
C:\Program Files\Business Objects\Tomcat55\webapps\

3. Restart the Tomcat service.

4. Open a browser and logon to the following URL: http://servername:serverport/monitoring (http://dinesh-pc:8080/monitoring)

The monitoring probe for BO has been implemented in DINESH-PC which already had BOXI 3.1 SP3 Server installation.

 Further implementations:

The XML output representation of the monitoring probes can be exported through “XSL (Extensible Stylesheet Language) connectors” to other type of formats. The official supported monitoring solutions are IBM TIVOLI and Microsoft Operations Manager (MOM). The monitoring probe deployment has default connectors which are used to integrate with these monitoring solutions.

These are the connectors which were found in monitoring deployment in BO,

  • totext4tivoli.xsl
  • totext4mom.xsl

These XSL style sheet convert the xml based output of monitoring probe into the required format for integration with monitoring solutions.

  • IBM TIVOLI / MOM have to be integrated with the monitoring probe to get a graphical interface of monitoring, instead of this XML based probes.

 

%d bloggers like this: