How to execute 360Eyes jobs for other CMS?

How to execute 360Eyes jobs for other CMS?

Symptom

360eyes is installed either on a dedicated server or on a sandbox.

You want to extract metadata from a different BOBJ CMS and Audit DB.

Environment

  • 360Eyes
  • SAP BusinessObjects Enterprise XI 3.1
  • 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

There are 2 ways to point 360eyes to a different CMS. 

  1. Using the GUI. 
  2. Using the CMC and passing parameters.

1. Using the GUI

a) Modify the BOBJ Audit connection URL and credentials in the 360eyes.param file - available under 360eyes installation directory.


You can do that either by manually modifying the file, or by running the setup.exe from the installation package.


For a manual change - In order to to encrypt the password, please follow the steps detailed on page 43 of the installation guide: https://support.360suite.io/download/file/234

b) Navigate to the 360eyes installation directory.

c) Right-click and Edit the 360eyes_GUI_BI4.bat with a text editor, and ensure the path to the BOBJ SDK corresponds to the location of the BOBJ installation in your environment.


d) Right-click and "Run as Administrator" the 360eyes_GUI_BI4.bat file and provide the required information. Note: Always run the CMS job first against a new CMS, so all the dependencies are extracted before running report-centric and universe-centric jobs.



2. Using the CMC

You can pass all the parameters - for the alternative CMS + its BOBJ Audit - within the Arguments section of the Program Parameters for the 360eyes job.
a) Right-click on the 360eyes job, and select Default Settings.

c) Click on Program Parameters and append the content of the Arguments field. It will contain the path of the 360eyes folder on the disk - do not change this. Simply add parameters after that value.

You can find more information about Command Line jobs in the documentation.
An example, the Arguments to connect to my Training CMS and Audit DB would be as follows:
-TargetCms=sapbi2training -TargetCmsUser=Administrator -TargetCmsPass=password -TargetCmsAuth=secEnterprise -DBAUDURL=jdbc:jtds:sqlserver//MYSQLSR16:1433/BO_AUD42 -DBAUDuser=dba -DBAUDpass=password

In order to encrypt passwords, please follow the steps detailed here.

See Also


Keywords
corba

Product

Product or Product version

  • 360Eyes

Languages

  • English

    • Related Articles

    • How does 360Eyes work with a CORBA SSL Enabled CMS?

      Symptom This article will explain you how does 360Eyes work with a CORBA SSL Enabled CMS. Environment 360Eyes Microsoft SQL Server SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business ...

    • Identify 360eyes jobs on Windows servers

      Symptom How to find active 360Eyes jobs when they are running on a Windows platform? Environment 360Eyes SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business Intelligence 4.1 SAP ...

    • Recommendations for Running 360Eyes jobs

      Symptom Jobs can be run on a one-shot basis (i.e. for testing) or a scheduled tasks (i.e. best for production). As jobs are Business Objects objects, they can be easily scheduled using the Business Objects platform. If the -replaceMode=ADD flag is ...

    • 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> ...

    • How to set up 360eyes to run with Windows Task Scheduler

      Symptom How to set up 360eyes to run with Windows Task Scheduler ? Environment 360Eyes SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business Intelligence 4.1 SAP BusinessObjects Business ...