How to use BOBJ Server Groups when 360Eyes is installed in a clustered BOBJ environment

How to use BOBJ Server Groups when 360Eyes is installed in a clustered BOBJ environment

Symptom

This applies only if 360Eyes is installed on the BOBJ server and if running the 360Eyes jobs is done via the CMS or the BI Launchpad.

Typically, when installing 360Eyes within a BOBJ clustered environment, each member of the cluster needs to have the Adaptive Job Server enabled and started, in order to successfully run the 360Eyes jobs.
In this case, the 360Eyes folder set up at installation time and all its content MUST be copied to all cluster members.

In the case not all node members contain the 360Eyes folder, when running the 360Eyes jobs, you will be presented with the following error: 


The program failed to run and supplied the following information: java.lang.ClassNotFoundException: com.gbs.eyes.LaunchBOBJHandler

This is due to the job not having access to the required dependencies (i.e. 360Eyes.key, 360eyes.param file, libs, tools) contained in the 360Eyes folder.

The only downside of this approach is the high maintenance. When you update 360Eyes, you will need to replace the 360Eyes folder on the cluster members with the updated 360Eyes folder.

Note: this will have no impact on the BOBJ installation, it is only for 360Eyes.

Environment

  • 360Eyes
  • SAP BusinessObjects Business Intelligence 4.0
  • SAP BusinessObjects Business Intelligence 4.1
  • SAP BusinessObjects Business Intelligence 4.2
  • SAP BusinessObjects Business Intelligence 4.3


Resolution

  1. In the CMC, go to Servers > Server Groups and create a Create Server Group:


  2. Provide a name for this new Server Group, then click OK:


  3. Once created, right-click on it > Add Members:


  4. Move to the right the AdaptiveJobServer that corresponds to the node where you have set up 360Eyes.


  5. Click OK.

  6. Make sure this new Server Group is Enabled and Running:

  7. Go to All Folders > 360eyes jobs, and for all the jobs you will be running, right-click > Default Settings:


  8. Click on Scheduling Server Group > Under Only user servers in the selected group, select the Server Group you created:


  9. Save and Close.

  10. You can now run the 360Eyes jobs.
Keywords
cluster, Business Objects, distributed

Product

Product or Product version

  • 360Eyes

Languages

  • English

    • Related Articles

    • Configure 360Eyes to run on SAP Business Objects 4.3SP2

      Symptom You run 360Eyes using the 360Eyes GUI or Command-Line against an SAP Business Objects Environment 4.3SP2. or  java -Xmx1024m -cp "../libs/;*%SDK_LIB_FOLDER%/*" com.gbs.eyes.Launcher <job> <cms> <BO_user> <BO_user_passwd> <auth> <360Eyes_dir> ...

    • 360Eyes evolution: from "standalone" to 360Suite web application

      Context On the meta-level, 360Eyes is part of 360Suite, a suite a modules working with BusinessObjects environments to help BI administrators with their day-to-day activities. On a practical level, the 360Eyes module itself has known changes over ...

    • Does Apache Tomcat belongs to Product Support scope?

      Context Does Apache Tomcat belong to Product Support scope? Answer Apache Tomcat, a free open-source third-party Web application server, is bundled with 360Suite (a Wiiisdom product) for convenience of use, but is not considered part of the ...

    • 360Suite database configuration is not set when restarting Tomcat server

      Symptoms On application startup, a warning popup appears In the Administration console, the database configuration is empty even though is was setup previously Environment 360Suite Web Platform Linux server (all) Additional symptoms : tomcat logs In ...

    • How to use "Last Snapshot" filter to improve performance on 360Eyes reports

      It's always a good practice to use the Snapshot ID filter to prevent combining data from multiple snapshots, which could lead to incorrect results and fail to represent the system's current status. To accurately reflect the current status, you should ...