Skip to Content

Below blog explains how to setup AFW (Automation Framework) and how to use some of the features with in AFW (Automation Framework). The main reason I started this blog, put all the content in one place , so new comers will be able to follow this blog to setup the AFW instead of searching through various documents or various posts. Hope this blog will help.

Why do I need to install AFW (Automation Framework)?

Automation Framework will help to automate some of the complex and repetitive BI tasks. This is the new tool introduced in BI 4.2 SP5 onwards which I found out this is more useful for repointing the Web Intelligence reports from UNV to UNX universes. Without this tool, we could not have done this change much easily. We can use standard templates as well as we can build custom templates using SDK.

How to setup Automation Framework in windows and change the source of the web intelligence report using AFW (Automation Framework).

If you are upgrading the environment from 4.x to 4.2 SP5, Automation framework will not be installed by default. After installing the 4.2 SP5, we need to modify the installer to add Automation framework.

Running the BI agent Service and Automation Framework from CCM:

To understand the Automation framework architecture, please refer the below link for BI Administration Console Guide

Login to Business objects server. Open command prompt in admin mode.

  1. Set JAVA_HOME=<INSTALL_DIR>\SAP Business Objects Enterprise XI 4.0\Winx64_64\SAPJVM
  2. CD <INSTALL_DIR>\AdminConsole\MessagingQueueBroker\bin\
  3. Startbroker.bat.
  4. Make sure the Apache ActiveMQ is running
  5. Open CCM, Start Automation Framework Service
  6. And Start BI agent service

Configure Enterprise Authentication for Automation Framework:

  1. Login to CMC, Authentication -> Double Click on “Authentication”
  2. In the Trusted Authentication section, make sure “Trusted Authentication” is enabled.
  3. Choose “New Shared Secret”. Choose “Download Shared Secret” . Select “update”
  4. Save the Shared Secret Key in the following Directory. <Install_dir>\AdminConsole\Automation Framework\Custom\cms_certificate

Accessing the Automation Framework URL:


How to add default templates if they are missing using Fresh Install or Modify install:

  1. When you login to AdminConsole , if you noticed Default templates are missing when you select new scenario, follow below steps to recover the Templates

To create those default templates manually through jar file execution by providing valid arguments.

Ensure JAVA Home path is set.

In CMC -> Application -> RESTful Web Service -> Properties provide valid Access URL and ensure that it is accessible from the machine where “Automation Framework” feature is installed.

Login to the machine where Automation Framework” feature is installed.

Open Command Prompt or Terminal and execute the below commands :

On windows:

set JAVA_HOME={BOE Installed Dir}\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\jre


cd {BOE Installed Dir}\SAP BusinessObjects Enterprise XI 4.0\java\lib

Execute the jar with 5 parameters :

CMS System Name

User name (a user with administrator rights)


Authentication type

Time Delay (In Milliseconds)

Example: java -jar myBoeCMS administrator password secEnterprise 0

Once you run the above jar, login to Automation Framework, make sure Default templates appear in the scenario section.


How to change the source of Web Intelligence report from UNV to UNX:

  1. Login to Admin Console.
  2. Click on “Landscape Management” to add Business Objects Platform
  3. Add System name, Access URL as “http://<Tomcat server>:8080/biprws or “http://<BOE Server>:6405/biprws , it is the same URL from CMC ->Applications -> Restful webservice URL
  4. Now click on home button to go back to main page. Click on “Automation Framework “ button to create a scenario.
  5. Click on Scenario, and + sign on the right top corner to add new scenario.
  6. On the workflow templates, Select “Standard “ templates.
  7. Drag “Logon”, Change web Intelligence source, Refresh Document, Logout icons to the right to create a scenario and save the scenario.
  8. Click on “Workflow template”, add the scenario from the previous step.
  9. Logon – Select the Landscape you want to logon to, Change Webi Intelligence Source – Select the webi document want to change it to,, Universe mapping -> select the UNV universe and UNX universe. And run the Task. It should change the source of the webi report from UNV to UNX.

Note: From SP5, there is no need to use restful webservice URL link to WACS server, you can connect to Tomcat server, since Restful service is part of Tomcat.

Refer the SAP KB article: 2585147

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Ravi Pai

    Hi Jawahar


    For some reason drag drop in UNV and UNX box is not working (unable to drop) on my system. Did you face this issue as well ?




  2. Ravi Pai

    Same, using IE 11. I even tied manual input of values of two universes but that failed

    We upgraded from SP4 to SP4 Patch1 and eventually on SP5

    1. Jawahar Konduru Post author

      What is failing? Task is failing.. Can you check your restful webservice URL? is it pointing to 8080 or 6405? I had similar issue when I tried to use 8080, after changing the port to 6405, it worked. Task completed successfully.

      1. Vytautas Thienel

        Hi Jawahar Konduru

        I get the same issue as Ravi described.

        P.S. The universe folder selected to BI Audit just to demonstrate the issue. The same issue appears for all Universe Folders.

        Web Service Properties:

        RESTful Web Service Properties:

        Where the is the IP address of the BO server

        I have created a test report based on UNV and tried to test the conversion to UNX. See the steps below for more information:

        Do you have any idea what can be causing this issue and what could be the solution?

        Thank you in advance,


  3. Vytautas Thienel


    See the steps below how to setup Automation Framework in Unix environment:

    1. Install the Automation Framework
    2. Configure enterprise authentication for Automation Framework. Refer to Configuring Enterprise Authentication for Automation Framework for more information.
    3. JAVA_HOME

    In Unix (for single session otherwise /etc/profile):

    • export JAVA_HOME=<INSTALL_DIR>/sap_bobj/enterprise_xi40/linux_x64/sapjvm
    • export PATH=$JAVA_HOME/bin:$PATH

    4. Start ActiveMQ Brokerexport (run

    • JAVA_HOME=<INSTALLDIR>/sap_bobj/enterprise_xi40/linux_x64/sapjvm
    • cd <INSTALLDIR>\AdminConsole\MessagingQueueBroker\bin\

    5. Start the Automation Framework Service

    • Repeat step 3 when using a new terminal session – Export (JAVA_HOME)
    • Run <INSTALLDIR>/AdminConsole/Automation Framework/

    6. Start the Agent

    • Repeat step 3 wehn using a new terminal session – Export (JAVA_HOME)
    • Run <INSTALLDIR>/AdminConsole/Agent/

    7. Follow SAP Note 2566764 to add the default templates.

    • Example: java -jar myBoeCMS administrator password secEnterprise 0


    In addition, to read more how to work with Automation Framework:



    1. Vytautas Thienel

      Hi Jawahar,

      Thanks for the quick reply.

      I am using IE 11.321.14393.0 Java 8 Update 171. I have tried to do the same using Mozilla and I could not map the universes.

      When starting the Automation Framework Service and the Agent I have noticed in ActiveMQ Broker “Disallowing use of vulnerable protocol”.

      INFO  [org.apache.activemq.artemis] AMQ241002: Artemis Jolokia REST API available at http://localhost:8161/jolokia
      INFO  [org.apache.activemq.artemis.core.server] AMQ221053: Disallowing use of vulnerable protocol 'SSLv2Hello' on acceptor 'ssl-acceptor'. See for more details.
      INFO  [org.apache.activemq.artemis.core.server] AMQ221053: Disallowing use of vulnerable protocol 'SSLv2Hello' on acceptor 'ssl-acceptor'. See for more details.
      INFO  [org.apache.activemq.artemis.core.server] AMQ221052: Deploying topic jms.topic.executeWorkflowList
      INFO  [org.apache.activemq.artemis.core.server] AMQ221052: Deploying topic jms.topic.taskTimeOut

      In the Automation Framework logs I have found the following errors:

      AMQ119017: Consumer is closed
      |Agent Registration Fail: Landscape in which the current agent belongs to is not yet registered in BI Adminstration Console (or) landscape exist without any connection. Kindly register landscape, If already registered create atleast one connection and then try again

Leave a Reply