Skip to end of metadata
Go to start of metadata

 

  • Contents

 

Latest news

BI Platform
Latest up to date information and release specialties can be found in:
SAP Note 1653689 - SolMan 7.1 & 7.2: Managed Sys Setup - BI Platform 4.0
SAP Note 1975394 - SolMan 7.1 & 7.2: Managed Sys Setup - BI Platform 4.1
SAP Note 2330545 - Preparation for Managed Sys Setup - BI Platform 4.2

Explorer
If you want to set up the configuration for an Add-On to BI Platform like Explorer servers, just follow the steps as BOE.

Apache Tomcat
BI Platform 4.0 and 4.1 are linked to Apache Tomcat (ATC) Version 7, where BI Platform 4.2 is linked to Apache Tomcat (ATC) Version 8.
To perform setup for ATC 8 you can find the latest up to date information in:
SAP Note 1633036  SAP Solution Manager 7.1 E2E RCA Setup for Apache Tomcat

WebSphere
To perform setup for WebSphere you find the latest up to date information in:
SAP Note 1482727 - SAP SLD Data Supplier for IBM WebSphere Application Server

Troubleshooting:
For troubleshooting on RCA for BOE, please refer to
SAP Note 1722874- Troubleshooting Solution Manager Root Cause Analysis for BOE
Troublesooting wiki: Diagnostics Configuration Troubleshooting for BOE 4.X https://wiki.scn.sap.com/wiki/x/tAsLGg 

 

Architecture Overview and Setup Procedure

First of all we would like to give an architecture overview for better understanding of the different setup steps that are needed.

In general a BOE system consists of two main landscape objects: “BI Platform” system and “Web Application” system.
The BI Platform system can have some Add-Ons like Explorer, Predictive Analytics,… which will only result in additional entries in the System Landscape Directory (SLD) of Solution Manager. They are all part of the same technical system and the setup is the same as for a pure BI Platform system. If a BI Platform system is distributed to several hosts (cluster), all nodes on all hosts will be linked to one technical system of type “BOBJ” in Solution Manager. Each node needs a separate setup via AC Tool, but is handled by one ‘Managed System Configuration’ procedure in Solution Manager.

The Web Application System (WAS) can be used from different vendors. The default is Apache Tomcat, but Solution Manager supports also SAP J2EE, Oracle WebLogic and Websphere. The WAS System is designed as an own technical system in Solution Manager. If an Apache Tomcat is distributed on more than one host, each host will be handled as a single technical system of type “ATC” as it does not support a kind of cluster technology.

If you also use a SAP Data Services System (DS), this DS system is modelled as own additional technical system of kind ‘Unspecific Cluster’ in Solution Manager. It has its own SLD data supplier and has to be setup separately using AC Tool and Managed System Configuration.

In the pictures above and below you can see that the connectivity from SolMan to ATC and BOBJ system are done via agents. All JAVA components (processes) can use the ‘Byte Code Agent’ to send their data directly to APM Introscope (formerly known as Wily Introscope). As the BOBJ system has also other native components (C++), these processes use the embedded NCS library to send data to the SMD agent (Diagnostics Agent), located on the same host as the process. This communication is done via a ‘port’ that has to be configured on the SMD agent as well as on the BOBJ CMC with the same value (Default port value suggested is 6404). The SMD agent then forwards the data to APM Introscope. APM Introscope is a third party tool that is delivered together with Solution Manager and works as ‘data collector’ for all NON-ABAP systems that are connected to Solution Manager.
Please note: By default not all Management Modules for Introscope Enterprise Manager are copied to the <EM folder>/config/modules folder. This means that there might be missing metrics in Introscope. Make sure to copy the relevant Management Modules (SAP_BOBJ.jar) to the <EM folder>/config/modules folder of your Introscope Enterprise Manager. See the SAP Note 1579474

Perform adaption of BOE to Solution Manager in 4 Steps:

  • Install necessary agents
  • Send Landscape information to System Landscape Directory (SLD)
  • Configure Components using AC Tool
  • Execute Managed System Configuration on Solution Manager (MSC)

You have to manually install the “SMD Agent” and “SAP Host Agent” on each host where a component is running on, that you want to link to Solution Manager. Other agents, like the Byte Code agent of the BI Platform system are already delivered together with the BIP product, so you just have to configure them. The Byte Code Agents for a Tomcat System are not delivered with the product, they are deployed using a configuration tool called “AC Tool” that takes over all necessary steps that have to be done for the BOBJ and WAS system.

The System Landscape Directory (SLD) is a central part of Solution Manager. All systems linked to SolMan need to have an entry inside SLD that reflects the system landscape, e.g.: host, technical instances, software components, product versions, databases, …. Each system normally has a component called “SLD Data Supplier” that sends the data of the system to SLD. For BOBJ this is already part of the product and just has to be configured by AC Tool. For ATC the SLD Data Supplier needs to be installed and configured by AC Tool. The SLD Data Supplier of BOBJ and ATC sends the data after each system restart again to SLD.

SAP offers a tool to perform all setup steps of ATC and BOBJ. Some of those steps will be moved to the standard installation procedure of BOBJ, but until the tool is not completely integrated into the BIP setup, you can download it from SAP Note
2137275 AC Tool release NOTE

To use the tool you have to maintain property files and execute either all steps or single step of the setup procedure.
The features of the tool are constantly improved and therefore you should download the newest version and check the documentation that is attached to the SAP Note in detail.

 

For BOBJ the tool will logon to CMC and maintain placeholder settings, configure the SLD data supplier with the connection to the SLD system, it will substitute some files with newer versions (Part of the file download inside the note). For ATC it will install Byte Code Agent, configure JMX and some JVM parameters. Depending on the BOBJ version the correct Agent release will be used (BIP 4.2 requires Tomcat 8 and Introscope Agent 9). In addition it will install, configure and run SLD data supplier. For both systems you can enable Thread Dump Analysis (TDA) to be able to trigger and analyze a Thread Dump of the JAVA processes from Solution Manager.

Picture below shows action number 2 and 3 (step 8 and 9 of SAP Note 1653689), where the placeholder values are maintained in the CMC for the direct Introscope connection of the JAVA agents and for the NCS data port to SDM Agent:

 

After you did all the configuration steps on the managed systems (BOBJ and ATC), you have to perform the guided procedure inside Solution Manager called Managed System Configuration (MSC). Here you will for example link the SMD agents to the solution manager system, set the NCS port on SMD Agent side, define which actions the SMD agent should execute, tell the Host Agent to which folders in the file system he has access for reading logs, schedule the data extractor on Solution Manager side so that the data from APM Introscope is collected into Root Cause Analysis of SolMan, …

If you want to use System Monitoring, you have to execute “System Monitoring Setup” in addition for each technical system.

 

 

Installation of Diagnostics Agent on all hosts

If not already done so, SAP Host Control and a Diagnostics Agent needs to be installed on all hosts where BOE is installed.

Please refer to SAP Note 1833501 - Diagnostics Agent Installer Versions.

Auto configure BOBJ and ATC using AC Tool

 A description, how to manually perform the steps that are automatically executed by AC Tool, can be found in SAP Note 1653689 

Download the latest version of AC tool from SAP note:
2137275 AC Tool release NOTE

Extract the zip file and copy the directory to the host where your BOBJ or ATC system is located.
You have to perform AC Tool on each BOE and ATC host – so locating it on a shared network drive that can be mapped to each host would be recommended.
To setup BOE you first of all have to maintain the properties file ‘boe.properties’ in the ‘conf’ folder:

 

Configure AC Tool

The following screenshots and parameters are based on AC Tool version 2.31 – they may be different on other versions – please read the documentation ‘ACTool User Guide.pdf’ in the ‘doc’ folder for details.
Some of the parameters are only used in special cases, therefore we marked the parameters as {Mandatory} that have to be defined in each case, and the {Optional} parameters might not be necessary for your setup. Please check the description inside the properties file and the User Guide carefully.
If you are not allowed for security reasons to enter passwords into the properties file in readable format, you can use the silent mode to enter the passwords during the execution of AC Tool.

Enter the conf folder and choose the boe.properties file.

a)     BOBJ: Maintain logon data to your BOBJ CMC {Mandatory}:

 

 

boe.home" is the root installation of BOE system. Example:
UNIX: /usr/sap/<SID>adm/sap_bobj    ;
Windows C:\ProgramFiles (x86)\SAPBusinessObjects
Example:
If your BOE folder is “D:\BOBJ\SAP BusinessObjects Enterprise XI 4.0” you should enter “D:\BOBJ” as boe.home.

Please pay attention to use the different separators in different operation system.
You can leave it empty when you are in Windows, the value would be found by AC Tool from registry.
"boe.system" is the CMS host name + port of target BOE node. If you use the default port 6400 you can just enter the hostname, otherwise you have to specify both. Examples: localhost, cmshost:7400,@clustername.
Example:
You can use the same value as you use for “System” in the logon screen to CMC, here ‘mo-123456789:6400’:

"boe.user" is the CMS user account (Administrator Role)
"boe.password" the password of the account you entered
"boe.os.user" a user to restart BOE

 

b)     BOBJ+ATC: Maintain environment settings {Optional}

"unix.shell": Check whether this sh shell path or link exists in your running UNIX system
"download.folder": The folder is under the AC root folder <AC_APP_DIR>/downloads and it is default set with value empty.
Normally you don’t have to change it.

 

c)     BOBJ+ATC: Maintain installation settings for SAP host agent {No longer used}

Normally SAP Host agent is installed manually so you don’t have to change these settings. SMD and Host Agents should be installed before using AC Tool.

 

d)     BOBJ+ATC: Maintain SLD data Supplier settings {Mandatory}

"sld.connectkey.replace": If the parameter is true, it will overwrite the existing “connect.key” file with the information you provide. In this file the connect data to the SLD is stored. The file is used each time by sldreg command.
For the parameters host, port, user and password you should enter your own SLD server 's information.
Pay attention that the sld.server.port shall be range [80,443,1024…65535] and the parameter sld.server.https is a boolean value, type y or n for using https or not.

"boe.sld.manualtransfer": This parameter is for manually triggering the transfer of SLD data sld server once or not.
You can see detail information in Note 1653689 Step 6.1 - Enable SLD support.

 

e)     BOBJ: Maintain APM Introscope settings for JAVA servers {Mandatory}

 

These parameters are for enable APM Introscope for Java components, and these settings will apply to all SIA nodes.
For the parameters host and port you should enter your own APM Introscope Enterprise Manager's information.
If you have different settings for different nodes, you should change them manually in CMC.

f)     ATC: Maintain generic ATC settings {Mandatory}

 

These parameters are to enable sending NCS data from C++ processes to SMD Agent, and later on to APM Introscope
These settings will apply to all SIA nodes, so using host = 'localhost' is recommended.
For the port you have to enter the same value as you later on use in Managed System Configuration (MSC) as NCS port of the agent.
If you have different settings for different nodes, you should change them manually in CMC.

g)     ATC: Maintain generic ATC settings {Mandatory}

“tomcat.service.name” and “tomcat.service.port” is needed only for Windows.
The default BOE installed value is always set as "BOEXI40Tomcat" and the port is always set as "8080".
"tomcat.http": Switch on https access to Tomcat – then you have fill also the keystore and truststore parameters.

"tomcat.home" is tomcat install path and it is only used for UNIX operation system.
<INSTALL_DIR>/tomcat or <INSTALL_DIR> both works for the parameter tomcat.home.

"tomcat.running.mode.WindowService" is a parameter with boolean value. If you choose true Tomcat will run as a windows service.

"tomcat.hostname.sld.url" is for any ACTool running host DN (Domain Name) resolution restriction. This parameter is limited only for ACTool sld data supplier URL local usage as
“http://$(tomcat.hostname.sld.url):$(tomcat.servcie.port)/sap.com~TomcatSLDDataSupplierWEB/sldsupplier?action=…”
In case localhost or short host name does not work for this URL (e.g. https), change it to a valid FQDN.
Normally this parameter should not be changed.

"tomcat.startup.path” and “tomcat.shtudown.path” specify the path values to the tomcat startup/shutdown shell script.
Make sure that your user boe.os.user which defined by JAVA_HOME can run these scripts.
If tomcat is default one, you should leave these parameters empty. Otherwise, manually change the path where scripts exists.

 

h)     ATC: Maintain Introscope Connection {Mandatory}

"wily.javaagent.install" – if true it will install a new wily agent in the install folder (no matter it is installed or not), else it will try to find a installed agent in it.

"wily.javaagent.installfolder"
Recommend use /usr/sap/ccms as wily install folder in UNIX and c:\usr\sap\ccms for Windows.
"wily.javaagent.folder"
Keep wily.javaagent.folder empty as the setup package of agent is already embedded in AC Tool package.

Provide host and port information of your enterprise manager in "wily.EM.host" and "wily.EM.port" – normally this should be the same APM Introscope EM that you used for BOBJ (“boe.cmc.introscope.host” and (“boe.cmc.introscope.port”).
6001 is a default number of EM port.

i)     ATC: Maintain JMX configuration {Mandatory}

Set your JMX user and password.
You provide user, password and port as credential, and you will be asked in MSC for the same values that you have specified here.
The password must not contain special characters.

 

j)     ATC: install and run SLD data supplier {Mandatory}

If this setting is 'true', AC Tool will install and run the SLD data supplier for Tomcat.
Normally you should not touch the default setting.
Just if you have to re-execute AC Tool (even several times), and you don't want to re-install the SLD data supplier each time you can set it to 'false'.

 

k)     BOBJ+ATC: Specify if you use older SolMan Versions {Optional}

You only have to maintain this if you use an older version of Solution Manager.
"solman.version" is the version of the solution manager you use.

 

l)     BOBJ+ATC: Specify the path to the SMDAgent {Optional}

Please enter the install path of smdagent.
This is only used if you setup a “BOLight” (BO using Remote Support Component).
In such a case AC Tool has to perform some configuration on the SMD Agent, which is normally done by Solution Manager.
Normally you should not touch the default setting.

 

m)     ATC: Specify the LONGSID of the ATC that should be used in SolMan {Mandatory}

Enter the long SID name for Tomcat technical system.
Note: The long SID of your BOBJ technical system can only be changed in LMDB, and not by the SLD data supplier.

 

n)     ATC: Trigger manual SLD transfer {Optional}

This parameter is for option to trigger manual transfer of "tomcat xml" to sld server once or not.
Do not touch default setting.

 

o)     BOBJ+ATC: Configure jvmmond for TDA {Optional}

 

These parameters are used to enable Thread Dump Analysis for the JAVA processes.
"jvmond.install.path" is install path for jre and the port is default set 1099 if there is no other application using this port.
You provide password and port as credential, and you will be asked in MSC for the same values that you have specified here.
The password must not contain special characters.

 

 

p)     BOBJ+ATC: Configure AC Tool running environment {Optional}

"console.verbose"
When silent mode is set, you can use this parameter to suppress the output to the screen.
If this parameter is set false, all console output will be disabled in silent mode.
However, you can still find all the same log in log files.
Do not touch default setting if you don't use silent mode.

q)     BOBJ+ATC: Configure restart settings {Optional}

In silent mode you can automatically restart BOBJ and ATC.
"boe.node.restart" for BOBJ and "boe.tomcat.restart" for ATC
Default no to touch this parameter.
If you would like to restart your BOBJ after setting up, make sure you has already specify the parameter boe.os.user as boe node running user.

r)     BOBJ+ATC: Set virtual host names {Optional}

"virtualHostName"
If you don't specify this parameter, it will automatically get short name of physic/logic host name.

s)     BOBJ: Set service name {Mandatory for Windows}

"boe.service.name"
If you are using UNIX operating system, keep it as default or empty.
When you are in Windows operating system, find your service in your Windows service list. As usual, the default BOBJ service is set like BOEXI40SIA<HostName>.

 

 

t)     BOBJ+ATC: Configure SAPOSCOL Process Monitoring {Optional}

"smdagent.windows.servicename"
This parameter is only used in Windows operating system.
You should find smdagent.windows.servicename in the service list, like SAPDAA_98.

"smdagent.restart"
If you set false here then you should restart smdagent manually.

 

u)     ATC: Remove users from jmxremote.password file {Obsolete}

There are restrictions on the file jmxremote.password. For security reasons only one user, specified as ‘boe.os.user’ will be the owner of the file.
No need to touch default setting.

v)     ATC: Use IBM JDK {Optional}

If you use a JDK from IBM you have to uncomment the "tomcat.ibmjdk.loggc" parameter

w)     BOBJ: Set parameters different per node or same for all nodes {Optional}

Some parameters have to be set different on each node. Therefore you have to run AC Tool for each node (host) separately. If you change the setting of this parameter to TRUE all nodes got the same values which might not work.
Normally you don’t have to touch the default setting.

x)     BOBJ+ATC: Enable sldreg SSL mode {Optional}

An environment variable SECUDIR is to set for BOE/Tomcat/DS runner or launcher
For ACTool can launch sldreg in condition of BOE Step 1 with "boe.sld.manualtransfer" = true and this variable has not been set, a new parameter in boe.peroperties is to adapt: “SECUDIR =”.
UNIX: you need to set this SCUDIR=$HOME/sec in boe.properties for ACTool working on root or sudo, $HOME is the user of BOE/Tomcat/DS;
Windows: This SECUDIR in boe.properties will not be used by ACTool; you need in any case set it for ACTool/BOE/Tomcat/DS runner.

 

 

y)     BOBJ+ATC: Use Wily Agent 10 {Optional}

If you use already APM Introscope EM Version 10, your Bytecode Agents also need to be on that version.
Version 10.1 is supported starting Solution Manager 7.2 SP03; (default is kept to 9.7)
Normally you do not have to touch this parameter.

z)     BOBJ: Enhance authorization of user SM_ADMIN for monitoring {Optional}

As described in SAP Note: 2266873 - How to configure XI4.1 CMS built-in user SM_Admin for BI/Job Monitoring

If you don’t want to use an “administrator” user, you can use user “SM_ADMIN” for monitoring, but only if authorization is enhanced.
This is done by setting these parameters and can be rolled back by un-commenting ‘UserToRemove=true’.

aa)     BOBJ: Setup BOLight {Optional}

For BOLight (BO using Remote Support Component) AC Tool has to perform some configuration on the SMD Agent, which is normally done by Solution Manager. Therefore it is important to define if the SMDAgent was installed by SWPM (Software Provisioning Manager) or not.

bb)     BOBJ: Set Symbolic link to correct directory {Mandatory for UNIX different than Linux}

SolMan Host Analysis/OSCommand support: Create file system symbolic link for BI install folder variations as they are different for the different UNIX types.
Follow instructions of SAP Note 1809048 AC Tool will set a symbolic link named “/sap_bobj/enterprise_xi40/linux_x64/jdk/bin"
that points to the 'bin' folder of your BI Platform - JVM (where your java.exe is located):
"<BOE_DIR>/sap_bobj/enterprise_xi40/<OS dependent part>/jdk/bin".
If you don't run on UNIX, different from LINUX you do not have to touch this parameter.

cc)     BOBJ: Support for Predictive Analytics 3 and Lumira {Optional}

To send the correct data to SLD for Lumira and PA3 you have to un-comment the mentioned parameters.
If you don't use LUMIRA or Predictive Analytics 3,  you do not have to touch this parameter.

dd)     BOBJ+ATC: Thread Dump Analysis – jvmmond {Optional}

If TRUE: jvmmond is not started when system restart – you have to start it manually.
This option is for jvmmon password security reason. More details in the AC Tool user guide.

 

ee)     ATC: Maintain the Introscope agent profile names {Optional}

Needed to setup other Systems like Hadoop by using AC Tool.
Normally the default should not be changed. More details in the AC Tool user guide.

 Execute AC Tool

When you finished maintaining all the parameters, you can execute AC tool to finish the set up session.
For all steps you need to execute AC Tool as root user (UNIX) calling "./run_actool.sh" or with administrator role (WINDOWS) running "run_actool.bat". 

 

Just following the steps and then all actions on the managed system are performed automatically.

To enter the passwords via stdin for security reasons, you can execute the program with arguments.
When you launch run_actool.sh[.bat] -boe.password -sld.server.password -jmx.password -jvmmond.password.
the user is invited to fill the passwords from stdin console. You don't have to write them in the properties file and they are also not seen in the AC Tool command line.
Launching run_actool.sh[.bat] -silentBOE
is designed for automation and does not expect any user input. It will suppress all output on the screen, just the final result and the log files will be written.
Launching run_actool.sh[.bat] -silentBOE -boe.password -sld.server.password -jmx.password -jvmmond.password
is a combination and the user has to input manually the passwords on the command line before AC Tool runs in silent mode.

Details can be found in the AC Tool User Guide.

After executing AC Tool please restart tomcat server.

Setting the EXTSID

There was the recommendation to use a naming convention for the Extended SID for Web Application System and BOBJ System, which was:

WAS:       <SID>_WAS (e.g. BOP_WAS)
BOBJ:     <SID>_BOE (e.g. BOP_BOE)

(<SID> must be identical to the SID chosen for the BOBJ system. If there are multiple Web Application Server systems connected to the same BOBJ system (e.g. for load balancing, scale out) then they shall be numbered like <SID>_WAS, <SID>_WAS1, <SID>_WAS2, … The extened SID has only 8 chars, so there is only one char for the “numbering”.)

This naming convention is only necessary for processing the EarlyWatch Alert with an old ST-SER software version.
As of SP 20 of Software Component ST-SER this naming convention is no longer necessary.

 

For Tomcat and WebSphere systems the extended SID can be defined in the SLD DS customization. See the Tomcat/WebSphere SLD DS setup documentation (notes: 1508421, 1482727) – by adding the line com.sap.sup.admin.sldsupplier.SYSTEM_ID = <SID>_WAS in the property file sldDataSupplier.properties of the SLD DS web application.

Another choice is to modify the extended SID in technical system editor, which is the only possibility to change the Extended SID for the BOBJ system.
Note: If you change the EXTSID of your BOBJ system you have to re-execute the ‘Managed System Configuration’ on Solution Manager if you executed this already.

Check the Technical System for BOE in LMDB

As long as Solman sync the landscape data from SLD to LMDB, you can find the auto created technical system for BOE in Solman.

In Solution Manager Work Center, go to SAP Solution Manager: Configuration. In the Technical System list, find out the technical system for BOE. The auto created BOE technical system will use the first character from BOE cluster name as the technical system name. Then you can go to technical system editor to check the integrity of technical system data.

In technical system editor, you are able to set the extended SID. Please make sure it applies the following naming convention pattern:

<SID>_BOE (e.g. BOP_BOE) – The <SID> is a 3 character system ID that is determined by the SID of the connected SAP J2EE system (in case the BO Web Applications are deployed on a SAP J2EE) or in case Tomcat or WebSphere is used can be chosen by the customer(and set identical in the Tomcat/WebShere SLD DS customizing).

The default extended SID is from the SLD data supplier which is the first 3 chars of the BO cluster name (which itself by default is built like <full qualified hostname>:<port>). The extended SID is then built in Solution Manager (LMDB) from the SID by either taking the same name or making it unique by adding a number filling to 8 chars (e.g. SID=BOP,  extended SID=BOP if no other BOP already exists or BOP00001 if already a BOP extended SID exists). This name is typically not very meaningfull why we recommend to change it in the Technical System Editor. This has to be done only once and the customer shall follow the naming convention above and can choose a SID that is meaningful for him.

Make sure the product version list here are set with diagnostic flag.

Go to the software node in the tree left hand, check whether the product instances are listed according to your BOE system installation. Make sure the “Diagnostic Relevant” flags are set properly and make sure each Product Version has the corresponding Software Component Versions listed below.  If you recieve an error stating that there is no diagnostic template, make sure you have only selected those product instances that are diagnostics relevant.  For a list of diagnostic relevant product instances for SBOP BI PLATFORM 4.0, refer to Maintenance of Product in the System Landscape#SAPBusinessObjectsEnterprise.


Go to Technical Instance node, check the application servers name, host, type and pathes. Make sure each Server has corresponding Software Component Version listed below.


Then switch to Central Management Servers, check the CMS server name, host and pathes.


Then go to Host node, make sure proper host info has been listed here. Missing host data can cause managed system setup failure.


  

Managed System setup for BOE 4.X

Select the Technical System for BOE, and then click Configure System.


 
There are 10 steps for setting up the managed system for BOE 4.X. Just some steps are critical for us.
 

 
    In the first step, we should configure the Product System and logical component for this technical system. You can find the assigned product system is empty, click "Display Technical System Software" to jump to Technical System Editor.

** in newer solman SPs, you can use the "create automatically" option for product system creation.

 

 In the Technical System Editor, change to "Edit" mode first then click "Assign to Product System" button.

 

In the popup dialog, input the Product System name with naming convention <SID>_BOE, for this example, VMW_BOE. Click "Create" to create this product system.

Then installed product instances are listed, click those with (SMP) ending instances, in this example, check "Enterprise Servers(SMP)" box as assigned and then close the dialog. 


  
Click the root node of Navigation Tree, select Product Systems Tab and check the created product system is there. If it is correct, save and close to leave the Technical System Editor.
 

 
Then create logical component for your BOE system.

** For solman lower than sp9, logical compoent is created in SMSY rather than LMDB. Please not that this is not vlaid in Solution Manager 7.2, since there is no SMSY

** If product version of "SBOP BI Platform 4." is not available in SMSY when you create loigcal component, implement SAP Note 1891049. 

"Specifically the following steps need to be implemented:
Step A - Download SBOP_BI_PLATFORM_41.zip attached to SAP Note 1603103. The archives contain the required XML files.
Step B - Call the report RS_SMSY_PPMS_XML_UP_DOWNLOAD with the option Upload = 'X'. Select the XML file that you just downloaded from the note, and load the required data into your system.
Go to transaction SE38, enter the report name “RS_SMSY_PPMS_XML_UP_DOWNLOAD” and choose to execute the program. On the next screen enter “X” for upload, and then select “All Products”, “Download All Components” and hit Execute. Select the downloaded xml file “SBOP_BI_PLATFORM_41.xml” and then you should find the products / components uploaded successfully – check details in the logs. Return to SMSY and create the Logical Component – you should now find the appropriate product in SMSY and Logical Component creation will be a success. If the data is still not there immediately after the upload,  please wait some time to get the data synchronized to SMSY internally in the system."

For solman from sp9, logical component is created in LDMB as the following screenshot.

Choose the system role. choose the product instance that the logical component is assigned. (in our case, SMP)

In our case, we use a logical component that is already created before. if you don't have one, create a new logical component.

After creating the product system and logical component in step1, this step is green.


Second step is critical. First we need to go to edit mode, then execute all prerequisites checks. Make sure the prerequisites return green result. The errors here may mostly related to missing diagnostic flag setting for the technical system or other technical system setup issue, you may need to go back to the technical system editor to fix it. 


Push next.

In step three, you need to assign a Diagnostic Agent to the managed system. In most case it will assign an Agent to you automatically, otherwise you can switch to SLD Agent Candidates and choose an agent from SLD. Make sure the agent is running well.


Push next.

In step 4, at least you need to input the Common Parameters. Select an Introscope EM. If you do not have a Load Balancer for your BOE installation, then the host should be the host where you install your web application server, and the port number should be the http port for your web application server.

And you need to enter the boe credentials as below. make sure the boe user has the admin access.


 Push next.

In Step 5, LMDB already enters the parameter for you. You need to make sure the Install Path and Log Path are correct configured by LMDB.


 
Push next.

Step 6 is also critical, you click the Execute All. In our case, the status for Extractor Setup and Introscope Host Adapter are interested for us. Make sure the results for them are green.


Push next.

In step 7, nothing to do, go ahead to next step.


Push next.  the step 8 in the screenshot is no longer available in newer solman SPs

In step 9, mark configuration check and push Execute All. Check the log. Make sure you can pass the Configuration Check.


 

Push next.

In last step 10, check the Status of the different setup steps you performed. The managed system setup complete.


 

Managed System setup for Web Application Server with BOE 4.X Web Application

Apache Tomcat

For detail please refer to wiki: Managed System Setup of Apache Tomcat System in Solman 7.1

As the SLD data for Tomcat Server has been reported by SLD data supplier, you can find the auto-created technical system for web application servers in Solution Manager.

There are also 10 steps for managed system setup. Some of them are critical for us.

The first step is to select product. If "Assigned Product System" is empty, click "Display Technical System Software" goto Technical System Editor.

In the Technical System Editor, change to "Edit" mode first, then click "Assign to Product System" button.

Input the Product system name with naming convention <SID>_WAS, for this example VMW_WAS and then click "Create" button.

Check all product instances as assigned.

 

 Save the changes and close the Technical System Editor.

 

Click "Refresh" button to see product system is assigned. 
Push next.

The second step is critical for us. In this step, we check the prerequisites by switch to edit mode and execute all.


Check the log if there is any error message.


Click the show to see the detail error info and then fix the problem, make sure you the check result are green.


Push next.

In step 3, we assign the Diagnostic Agent to technical system.


Push next.

In step4, we enter system parameter.


Push next.

In step 5, we enter landscape parameters by switch to edit mode. Here is a parameter “BOWA Log Path” which always has to be set manually. It is the directory where BOE web application logs are written to and by default is the home directory of the user that runs the web application server (on Windows and with Tomcat this typically c:).

On Windows:


 
On Unix:


Push next.

In step 6, switch to edit mode, and then execute all automatic activities. Make sure the status of Extractor Setup and Introscope Host Adapter are green.


Push next.

In step 7, go ahead to next step.


Push next.

In step 8, go ahead to next step.


Push next.

In step 9, click Execute All. Make sure you can pass the Configuration Check.


Push next.

In last step 10, the status of all steps is displayed for you. The managed system setup completed.

IBM WebSphere

For detail please refer to wiki: Managed System Setup of IBM WebSphere in Solman 7.1

Oracle WebLogic

For detail please refer to wiki: Managed System Setup of Oracle WebLogic in Solman 7.1

SAP J2EE Server

TBD.

Setup of the BOE Database system 

For detail refer to wiki: How to perform the Database configuration for BOE 4.0 and 4.1 in Solman 7.10

Wily Introscope setup for BOE 4.0

Please refer to Note 1540591 - Wily Introscope Setup for SAP BOE 4.0

Make sure the Agent profile is configured correctly when you setup Wily Agent for the Web Application Server where BOE Web App is deployed.

Find the line of directive file configuration in the <IntroscopeAgent>.profile. This file is in Wily Agent folder, default it is /usr/sap/ccms/wily :
introscope.autoprobe.directivesFile=…
Append the “sap_boe_webapp.jar” in this line if it hasn't beed appended, and make sure no "sap_bo_enterprise.jar" in this line
introscope.autoprobe.directivesFile=…,sap_boe_webapp.jar

Note:
1. You should remove the pre-configured sap_bo_enterprise.jar in directives file configuration "introscope.autoprobe.directivesFile". It can not coexist with sap_boe_webapp.jar here. That file is for BOE 3.x version.
2. Starting with release 8.2.4.x and all 9.x releases of the EM, the Management Module for BOBJ (SAP_BOBJ.jar) get installed to folder <EM folder>/sap/extra_modules.You need to copy the jar files to the deployment folder of the EM <EM folder>/deploy. More detail can be found in SAP Note 1579474.

3.If you are using the edition after solution manager 4.1 sp05. Metrics in Wily Introscope might incomplete because the edition of you IS agent(Java agent) is not proper.

To solve this problem, you should to update your IS agent upper than 9.5.6.1 including 9.5.6.1(eg. 9.5.6.1 & 9.7.1). You can download the latest version of Isagent from SMP or you can use ACtool to re-setup your IS Agent. Please refer Note 2209163 for detail information about this problem.

If you want to download the latest IS agent you can refer Note 1438005. Please note that Introscope Enterprise Manager version should always be equal or higher than the ISAgent version. Please see the Introscope Release Notes:
2071100  Introscope 9.5 Release Notes
2138309  Introscope 9.7 Release Notes for changes and open issues


Thread Dump Analysis Supportability

Thread Dump Analysis for Java instances of BOE Server is supported.
Please refer to Note 1608714 for the configuration details.

 

 

 

  • No labels

14 Comments

  1. The link to note 1653689 in part:

    Auto configure using AC tool

    Please go through SAP Note 1653689, download the 5 files (AC_part1.RAR, AC_part2.RAR, AC_part3.RAR, AC_part4.RAR, AC_part5.RAR), and unzip the AC_part1.RAR archives.

    After unzipping the archives, you should see the follow structures.

     

    does not work outside from SAP.

     

  2. Dear Experts,

    I read this note "1608714" and downloaded all attached files. But i could not found AC Tool (autoconfigure.exe). Please help me.

    Thanks.Regards

  3. Former Member

    Hi All,

    The content about AC Tool in this WIKI is out of date, and our expert will update it soon, for the AC Tool details you can refer to the Note : 2137275. For BOE Manual configuration please refer to the Note : 1653689, 1975394, 1648380 (different BOE version).

    autoconfigure.exe will not supported anymore, please refer to the Guide of AC Tool to use the tool.

    Best regards,

    Leo.

  4. Hi @all

    Is it only possible to monitor the SAP BO Environment 4.1 with Apache Tomcat or is there a possibility to do this with SAP BO on Netweaver?

    Kind regards,

    Mario

    1. Former Member

      Hi Mario,

       

      This wiki is for BOE integration with solution manager.

      It is possible for BOE 4.0,4.1 with tomcat, websphere, weblogic.

       

      Best Regards,

      Luo, Frank

       

      1. Hi Frank

        Thanks for your answer.
        Okay then there isn't a possibility to monitor the BOE in the SAP Solution Manager if the BOE and the Solution Manager is running on Netweaver?!

        Kind regards,
        Mario

         

  5. Former Member

    Hi all,

     

    When I tried to perform the step "Extractors Setup" when managed the BIP system in Solman 7.1, the following error occured.

     CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 500 : Internal Server Error")
     
     CX_SOAP_FAILURE : Error when processing Web service call

     CX_SOAP_CORE : Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 500 : Internal Server Error")

    Actually I have uploaded all the extractors into solman system in note 1849781 - Missing RCA Extractor for BOE 4.1 in Solman7.1 up to and including SP13 . Would you please let me know how could I troubleshoot this error?

     

    Thanks and best regards

    Eric

     

     


     

    1. Hi Eric,

      This is an error in the Java stack of the Solution Manager. You can troubleshoot it as follows:

      1) Reproduce the error.

      2) Call transaction SOAMANAGER, check the traces and you will find in which Solution Manager instance it happened.

      3) Open SOLMAN_WORKCENTER > Root Cause Analysis > System Analysis > Log Viewer > Choose the Solution Manager Java Stack. In the new screen you select the instance you found in step #2, then check the logs of the server node, here you find more details about the error. If you have not performed the managed system configuration for the Solution Manager, you may have to check the defaultTrace file directly.

      4) These errors are usually related to ICM or web dispatcher. If you're using web dispatcher, go in the System Preparation in SOLMAN_SETUP, step "Configure Connectivity" and disable it. Then test again, if it works now, then we narrow down the problem to the webdispatcher. In this case, check the logs of the webdispatcher. If it still doesn't work, check the dev_icm of the instance affected. If there are no errors around the same timestamp in the dev_icm, probably the call passed by the ICM successfully and therefore no log was generated. Then there might be errors in the Java stack and the web services used. You may open the NWA Java Administration (http://<SOLMAN>:<port>/nwa ) > Administration > Choose "failed applications" in the combo box, if there's any application failed, restart it.

      Other details are provided with note 1822831. Besides that, there are many different causes, so, make a search for error you find in the log viewer/defaultTrace and you may find KBAs explaining it, there are different ones for each cause. You can also post more details here and I may help.

      Here go some of the KBAs talking about similar issues:

      1852733 - Unsupported xstream found ( "HTTP Code 500 : Timeout ") while running manage system config using SOLMAN_SETUP - SAP Solution Manager 7.1
      1837656 - Extractor Setup returns "CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 500 : Timeout")" - Solution Manager 7.10
      1663549 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 401 : Unauthorized") during SOLMAN_SETUP
      2151624 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 502 : notresolvable") during SOLMAN_SETUP
      2163526 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 504 : Connection Timed Out") during SOLMAN_SETUP

      You may notice that many of them provide a change in the proxy settings in transaction SICF as solution, please check that even if the error you find is a little bit different than the ones in the KBAs.

      Regards,
      Daniel.
       

  6. Former Member

    Dear All,
    I noticed the error 'Error while trying to invoke method collectData of class com.sap.sup.admin.bwextract.E2eEAEventLogExtractor. See defaultTrace for details' in the extractor framework at all extractors with name 'EXCEPTION ANALYSIS (EVENT LOG)'
    Does someone know which trace is meant? I updated extractors by note 1849781, but that didn't work. Does someone have an idea for solution?
    1. Former Member

      Dear all, I think Note 2349248 will probably help.

  7. Former Member

    Dear All,

    I'm getting an error while executing the AC Tool at step 1 > BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster

    When I run the check for this step it was completed successfully. 

    Script 1. BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster SUCCESS

    2017/05/23 15:07:42.383000|==| | |11284| 1| |||||||||||||||console output:------------------------------XXXXXXXXXXXXX 2017-05-23 15:07:42 Execute Start ------------------------------

    Getting a below error message in command line.

    ------------------------------ XXXXXXXXXXXXX 2017-05-23 15:13:20 Execute Start ------------------------------

    ---------- BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster ----------
    [INFO] Keep original connect.key file.

    Exception in thread "Thread-1" java.lang.NoClassDefFoundError: com/rsa/crypto/jcm/ModuleLoader
    at com.rsa.cryptoj.o.cq.<clinit>(Unknown Source)
    at com.rsa.cryptoj.o.co.<clinit>(Unknown Source)
    at com.rsa.jsafe.CryptoJ.isFIPS140Compliant(Unknown Source)
    at com.businessobjects.bcm.internal.BcmRsaLib.initialize(BcmRsaLib.java:214)
    at com.businessobjects.bcm.internal.BcmRsaLib.<clinit>(BcmRsaLib.java:289)
    at com.businessobjects.bcm.BCM.<clinit>(BCM.java:1158)
    at com.crystaldecisions.enterprise.ocaframework.BCMInitializer.run(BCMInitializer.java:29)
    at java.lang.Thread.run(Thread.java:812)
    Caused by: java.lang.ClassNotFoundException: com.rsa.crypto.jcm.ModuleLoader
    at java.net.URLClassLoader.findClass(URLClassLoader.java:444)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:490)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:376)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    ... 8 more
    Exception in thread "main" java.lang.NoClassDefFoundError: com/businessobjects/bcm/BCM : cannot initialize class because prior initialization attempt failed
    at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.establishConfidentialChannel(ConfidentialChannelService.java:189)
    at com.crystaldecisions.sdk.occa.security.internal.ConfidentialChannelService.createConfidentialChannel(ConfidentialChannelService.java:149)
    at com.crystaldecisions.sdk.occa.security.internal.CCMap.locateCCItem(CCMap.java:63)
    at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:845)
    at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:805)
    at com.crystaldecisions.sdk.occa.security.internal.LogonService.userLogon(LogonService.java:210)
    at com.crystaldecisions.sdk.occa.security.internal.SecurityMgr.userLogon(SecurityMgr.java:166)
    at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody0(SessionMgr.java:454)
    at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon_aroundBody1$advice(SessionMgr.java:517)
    at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon(SessionMgr.java:1)
    at com.sap.ac.transaction.steps.boe.BOEUtil.getBOEConnectionConsole(BOEUtil.java:257)
    at com.sap.ac.transaction.boe.TransBOEConsole.connectBOE(TransBOEConsole.java:4516)
    at com.sap.ac.transaction.boe.TransBOEConsole.CreateCMSProperties(TransBOEConsole.java:5321)
    at com.sap.ac.transaction.boe.TransBOEConsole.enableSLDForBOCluster(TransBOEConsole.java:213)
    at com.sap.ac.transaction.boe.TransBOEConsole.<init>(TransBOEConsole.java:4995)
    at com.sap.ac.console.ConsoleBOE.performAction(ConsoleBOE.java:26)
    at com.sap.ac.console.base.BaseConsole.chooseSteps(BaseConsole.java:183)
    at com.sap.ac.console.base.BaseConsole.chooseActionType(BaseConsole.java:103)
    at com.sap.ac.console.base.BaseConsole.config(BaseConsole.java:41)
    at com.sap.ac.entry.ConsoleModeLauncher.process(ConsoleModeLauncher.java:254)
    at com.sap.ac.entry.ConsoleModeLauncher.main(ConsoleModeLauncher.java:236)
    Caused by: java.lang.NoClassDefFoundError: com/rsa/crypto/jcm/ModuleLoader
    at com.rsa.cryptoj.o.cq.<clinit>(Unknown Source)
    at com.rsa.cryptoj.o.co.<clinit>(Unknown Source)
    at com.rsa.jsafe.CryptoJ.isFIPS140Compliant(Unknown Source)
    at com.businessobjects.bcm.internal.BcmRsaLib.initialize(BcmRsaLib.java:214)
    at com.businessobjects.bcm.internal.BcmRsaLib.<clinit>(BcmRsaLib.java:289)
    at com.businessobjects.bcm.BCM.<clinit>(BCM.java:1158)
    at com.crystaldecisions.enterprise.ocaframework.BCMInitializer.run(BCMInitializer.java:29)
    at java.lang.Thread.run(Thread.java:812)
    Caused by: java.lang.ClassNotFoundException: com.rsa.crypto.jcm.ModuleLoader
    at java.net.URLClassLoader.findClass(URLClassLoader.java:444)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:490)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:376)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
    ... 8 more

    Log file > X:\SAP_ACTool\logs\ac_5040_2017_05_23_15_12_53_745_trace 

    2017/05/23 15:12:53.745000|==| | | 5040| 1| |||||||||||||||actool version: 2.40.0
    2017/05/23 15:12:57.901000|==| | | 5040| 1| |||||||||||||||Load file X:\SAP_ACTool\conf\boe.properties successfully!
    2017/05/23 15:12:57.901000|==| | | 5040| 1| |||||||||||||||Load property file 'boe.properties' successfully!
    2017/05/23 15:13:05.261000|>=|W| | 5040| 1| |||||||||||||||console output:[WARN] You have inputed an invalid value ''back'', please input again.
    2017/05/23 15:13:20.198000|==| | | 5040| 1| |||||||||||||||Could not find the property key 'virtualHostName'. Please check whether it is mandatory.
    2017/05/23 15:13:20.214000|==| | | 5040| 1| |||||||||||||||console output:------------------------------ XXXXXXXXX 2017-05-23 15:13:20 Execute Start ------------------------------

    2017/05/23 15:13:20.214000|==| | | 5040| 1| |||||||||||||||console output:---------- BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster ----------
    2017/05/23 15:13:20.214000|==| | | 5040| 1| |||||||||||||||console output:[INFO] Keep original connect.key file.

    2017/05/23 15:13:20.230000|==| | | 5040| 1| |||||||||||||||File checked existed:R:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\version\version.txt
    2017/05/23 15:13:20.230000|==| | | 5040| 1| |||||||||||||||Detect BI 4.x Server installed on R:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\

    2017/05/23 15:13:20.230000|==| | | 5040| 1| |||||||||||||||Try to connect to BOE CMS...wait a moment
    2017/05/23 15:13:20.339000|<<| | | 5040| 1|{|||||||||||||||CrystalEnterprise:getSessionMgr
    2017/05/23 15:13:20.417000|<<| | | 5040| 1|}|||||||||||||||CrystalEnterprise:getSessionMgr: 00.078
    2017/05/23 15:13:20.417000|<<| | | 5040| 1|{|||||||||||||||SessionMgr:logon
    2017/05/23 15:13:20.792000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:20.933000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.141] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer._is_a#localhost:3936:8348.9983:1]
    2017/05/23 15:13:20.933000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.027000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.094] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer.newService#localhost:3936:2704.9984:1]
    2017/05/23 15:13:21.027000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.073000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.046] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer._is_a#localhost:3936:9960.9985:1]
    2017/05/23 15:13:21.073000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.089000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.016] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer.queryEx3#localhost:3936:6436.9986:1]
    2017/05/23 15:13:21.105000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.136000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.031] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer.free#localhost:3936:4924.9987:1]
    2017/05/23 15:13:21.136000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.136000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.000] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer.newService#localhost:3936:5632.9988:1]
    2017/05/23 15:13:21.152000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.167000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.015] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer._is_a#localhost:3936:4896.9989:1]
    2017/05/23 15:13:21.167000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.183000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.016] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer.newService#localhost:3936:5104.9990:1]
    2017/05/23 15:13:21.183000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.198000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.015] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer._is_a#localhost:3936:3708.9991:1]
    2017/05/23 15:13:21.198000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.214000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.016] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer._is_a#localhost:3936:5620.9992:1]
    2017/05/23 15:13:21.214000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.214000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.000] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer.newService#localhost:3936:5696.9993:1]
    2017/05/23 15:13:21.214000|==| | | 5040| 1|{|||||||||||||||START OUTGOING CALL Outgoing: FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1]
    2017/05/23 15:13:21.230000|==| | | 5040| 1|}|||||||||||||||END OUTGOING CALL Outgoing: SPENT [00.016] FROM [BIPSDK.SessionMgr:logon#XXXXXXXXX:5040:1.2:1] TO [cms_XXXXXXXXX.CentralManagementServer._is_a#localhost:3936:11512.9994:1]
    2017/05/23 15:13:21.230000|<<| | | 5040| 1|}|||||||||||||||SessionMgr:logon: 00.813

     

    Please could anyone help to fix this issue.

    Thanks in advance!!!!

    Regards

    Pav.

  8. Thanks for this wonderful wiki. Please consider to adjust for part I)

    l)     BOBJ+ATC: Specify the path to the SMDAgent {Optional} → should be Mandatory