Contents1. StepByStep Checklist for missing EWA data for BO Enterprise XI 3.1.............................................4

2. StepByStep Checklist for missing EWA data for BI Platform 4.X...................................................11

3. KPI script.......................................................................................................................................20

3.1. KPI script return errors (SP1)................................................................................................20

3.2. KPI Script fails due to wrong variables:.................................................................................21

3.3. KPI Script fails due to double performed setup with different SID:......................................22

3.4. KPI Script fails when it is executed automatically but runs in remote OS console:...............23

3.5. KPI Script for BOE 4.0 fails when executed in remote OS console:.......................................24

3.6. KPI Script runs into timeout or runs very long:.....................................................................25

3.7. Test KPI Script for BOE 4.0 direct on OS level:......................................................................26

4. Extractors are scheduled also on MAI level for PPMSID “01200615320900003804” in SM 7.1.. .26

5. Missing WebI data (NCS) in E2E WA for BOE 4.X..........................................................................28

5.1. Wrong node names for the BOE system (‘_’ instead of ‘\’):.................................................28

5.2. Wrong NCS Metrics Settings in CMC.....................................................................................29

6. Missing CMS Tab in SM 7.0:..........................................................................................................31

7. How should Host Agent setup look like (BOE 4):..........................................................................32

8. Wrong Agent name for Tomcat – SAP Note 1540591 -> Tomcat Setup........................................33

9. Overload on Extraction via SOLMANDIAG....................................................................................36

10. Missing process information from SAPOSCOL..........................................................................39

11. How should workload data in Wily EM for BOE look like..........................................................41

11.1. Business Objects Enterprise XI 3.X....................................................................................41

11.2. SBOP BI Platform 4.X.........................................................................................................42

11.3. In WILY Investigator you see two nodes for a host (‘HOST’ and ‘host’)............................43

12. Missing WebI data (NCS) in Wily EM for BOE 3.1.....................................................................44

13. Switch on/off Transaction Trace for BOE 3.X does not work....................................................46

14. Missing BO 4.X System in SLD...................................................................................................47

15. Missing EWA for BOE 3.X systems in SolMan 7.0.....................................................................49

16. Corrupted Store in Change Reporting or parsing errors for DumpAllinXML(wi_srvadmin.jar script) for BOE 3.1................................................................................................................................50

17. OS Commands (e.g. DumpKPIs, DumpAllinXML) not working on BOE 3.1................................51

18. OS Commands (e.g. DumpKPIs, DumpAllinXML) not working on BOE 4.X running on UNIX different from Linux.............................................................................................................................52

19. JAVA Exception when executing OS Command DumpAllinXML................................................52

20. BI Monitoring: Select BO Jobs -> Error in Web Service Execution............................................53

21. Missing data / grey alerts in System Monitoring of BOE..........................................................55

21.1. FileRepositoryServer [Performance]: Fileserver Avg Read/Write Response Time............55

21.2. CMS [Performance]: CMS Logon Response time..............................................................58

21.3. CMS [Exceptions]: Number of failed BO Job Executions...................................................59

21.4. <All servers> [Availability]: Instance Availability...............................................................62

Structure=>Description:

Solution:

Example:

1. StepByStep Checklist for missing EWA data for BO Enterprise XI 3.1Central Setup Notes are: 1357901 SBOP Enterprise XI 3.11388247 SBOP Explorer XI 3.X1646341 EarlyWatch Alert for SAP BusinessObjects IDD/EIMSolMan 7.0 Setup Guide:https://service.sap.com/~sapidb/011000358700000074392009E

SolMan 7.1 Setup Wiki: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape

Is data available for BOE Server in WILY EM?Screenshots in Investigator of Systems with longSID: “B32” and “DEW_BOE”

………………….. Node name for Tomcat WAS is different – depending whether you have created the tomcat a) manually in LMDB with system type ‘UNSPECIFIC’ (node name= <SID>_WAS_<host> [B32_WAS_diagp001] below the ‘SAP Netweaver’ entry => see screenshot on the left side) or => This should only be used in Solution Manager Release 7.0b) via SLD data supplier with system type ‘ATC’ (node name= <host>_<port> [dewdfgwp00363_8005] below the ‘Tomcat’ entry => see screenshot on the right side) as described in SAP Note 1438005 => This should always be used in Solution Manager Release 7.1

Are there two host entries – one in capital and one in lower case letters for the same host?All data has to be linked to one host node in Wily Introscope Investigator which is written in lower case letters. You can force the lower case hostname also to be used by the Introscope agent by adding the following line into the Introscope agent profile:introscope.agent.hostName=<hostname>For BO 3.1 changes have to be performed directly in the profile (e.g. /usr/sap/ccms/wily/IntroscopeAgent.profile). Where the profile is located can be set in the startup parameters of MDAS and tomcat MDAS and Tomcat are using sames profile if it is manually setup like described in SAP Note 1357901 (path to tomcat config file is set in windows registry).For BO 4.X you have to add this into the file IntroscopeAgent.template located in the directory:<drive>: \Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wilyThis will correct the hostname used for the BOE server side java based agents.Additionally the Web App Server uses a java based Introscope agent for which you can set the hostname in the same way.The profile is located under <drive>:/usr/sap/ccms/wily.For Tomcat it is named: IntroscopeAgent_tomcat.profile.For Websphere it is named: IntroscopeAgent_websphere.profile.Do not try to change the hostname in SLD or LMDB! Hostnames have to be written in lower case letters in SolMan.

Is below the BOE-host entry a node “SAP HostAgent process” -> “SAP HostAgent SMD…”?-If there is more than one SMD Agent (‘SAPHostAgent SMD…’) you have to find the right one linked to your SolMan. Open the node “SAPHostAgent SMD...” -> “SelfMonitoring” -> “Solution Manager” -> Check values at “Host” and “Port”-If this node is not available please check first the settings for WILY EM Port and Host. Use AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> Application Resources -> ‘IntroscopeSAPAgent.profile’ -> Scope = SMD Agent of the BOE System -> Download.Maybe a restart of the SMD agent is necessary after changing some settings here.

Is there below a node “BOBJ ENTERPRISE” -> “<ShortSID>”? If this node is not available please check first the ncs.conf settings. Host and Port must fit to the settings in SAPAgentConfig.xml and NCSInstrumentLevelThreshold must be > 0.

Is below the <ShortSID> a node “BOE_KPIs”?If not, then the KPI script is not running. Execute the script manually in RCAWorkcenter -> Host Analysis -> -> Select the right host -> OSCommandConsole:System = <BOE System>; Group = BOE; Command = DumpKPIs => Send Command.-Check the parameter settings in AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.remoteos -> Scope = SMD Agent of the BOE SystemAll parameters have to be set and the names of the parameters must be:ENV_SID_<LONGSID>_BOE_AUTH_TYPE = ENV_SID_<LONGSID>_BOE_CMS ENV_SID_<LONGSID>_BOE_CMS_PWD ENV_SID_<LONGSID>_BOE_CMS_SE_PWD ENV_SID_<LONGSID>_BOE_CMS_USRENV_SID_<LONGSID>_BOE_DIROne example: for a parameter name with longsid = DEW_BOE => ENV_SID_DEW_BOE_BOE_AUTH_TYPE.Note: We have to have two times the “BOE” in the parameter name as it is part of the default BOE LONGSID and part of the default parameter name!-Check the content of AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> Application Resources -> ‘SAPAgentConfig.xml’-> Scope = SMD Agent of the BOE System -> Download.SocketDestination -> Port has to be set to the default: 59818. It is only changed if you have more than one SMD agent on the host. Then it has to be the same port value as written in “ncs.conf” file.-Check the content of AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> ‘SAPAgentConfig.xml’-> Scope = SMD Agent of the BOE System -> Download.command: bo.dump_kpis -> longsid has to be set to the right value “<LONGSID>” and prefix must be: “BOBJ ENTERPRISE|<ShortSID>”

Are below the <ShortSID> the nodes “WiReportServer_<…>.WebIntelligenceProcessingServer” and “ConnectionServer_<…>. ConnectionServer”-If the BOE3.1 system runs on UNIX we will not see this nodes as the processes sending this data are C++ processes that need the library “NCS.lib” inside which is not available for BOE 3.1 on UNIX. It is used only for BOE 3.1 on Windows and for BOE 4.X-If you run on windows and the nodes are missing check the following settings in file “ncs.conf” “instrument_level_threshold=10” -> if the value is 0 no data is send.“system_name= BOBJ ENTERPRISE|<SHORT_SID>”“agent_host=localhost”“agent_port=59818” -> has to similar to the value in ‘SAPAgentConfig.xml’

Is below the BOE-host entry a node “SAP Netweaver”All JAVA-type processes send their data to Wily via the ‘Introscope Agent’ that runs inside the JVM of the application. All the data from those applications are visible below the “SAP Netweaver” node.

Is below ‘SAP Netweaver’ a node for MDAS with the name: <LONG_SID>_BOE_<host>_MultiDimensionalAnalysisServicesServer?If this node is not available please check first the settings for WILY EM Port and Host. Use AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> ‘IntroscopeSAPAgent.profile’-> Scope = SMD Agent of the BOE System -> Download.A restart of the MDAS process is necessary after changing some settings here.Check the command line parameters of the MultiDimensionalAnalysisServicesServer. GoTo CentralManagementConsole of BOE -> Servers -> Service Categories -> Voyager. Check if the parameter for “Dcom.wily.introscope.agent.agentName” is set correct.:‘-Dcom.wily.introscope.agent.agentName=<SID>_BOE_<host>_MultiDimensionalAnalysisServicesServer "Note: <SID> at the beginning of the name is the <SHORT_SID> (3 characters)Example:"-server" "-javaagent:D:\usr\sap\CCMS\wily\Agent.jar" "-Dcom.wily.introscope.agentProfile=D:\usr\sap\CCMS\wily\IntroscopeAgent.profile" "-

Dcom.wily.introscope.agent.agentName=DEW_BOE_dewdfgwp00363_MultiDimensionalAnalysisServicesServer" "-Djava.awt.headless=false -Xss1M -Dbobj.javaserver.home=D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0//java/server" "-Dcom.businessobjects.pjs.common.dir=D:/Program Files (x86)/Business Objects/common/4.0/java/lib/" "-Dcom.businessobjects.pjs.conf.file=D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0//java/server/conf/config.xml" "-Dorg.apache.geronimo.base.dir=D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0//java/server/platform" "-Djava.io.tmpdir=D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0//java/server/platform/var/temp" "-Dbusinessobjects.logs.home=D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0/logging/" -Xmx256m -Xconcgc -XX:CMSInitiatingOccupancyFraction=30 "-DXorg.apache.geronimo.gbean.NoProxy=true" -jar "D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0//java/server/bin/boeserver.jar" "-workdir" "D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise

12.0//java/server/work" "-Djava.library.path=D:/Program Files (x86)/Business Objects/BusinessObjects Enterprise 12.0/\win32_x86"A restart of the MDAS process is necessary after changing some settings here.Note: Details are described in the attachment “ISJavaAgentForBOE3x.pdf” of SAP Note 1357901.

Is below ‘SAP Netweaver’ a node for Explorer Servers?If SBOP Explorer XI 3.1 is used, it is running on top of BO Enterprise XI 3.1. All processes are JAVA based processes so we should see 4 entries below the SAP Netweaver node:<SID>_BOE_<host>_ExplorationServer<SID>_BOE_<host>_MasterServer<SID>_BOE_<host>_IndexServer<SID>_BOE_<host>_SearchServerThe agent name for these servers are not set directly in the command line parameters in CMC of BOE. They are set in dedicated ini-files for every server. Details are described in SAP Note 1388247. Note: <SID> at the beginning of the name is the <SHORT_SID> (3 characters).A restart of the explorer processes is necessary after changing some settings here.

Is data available for WebApplicationServer (WebAS) in Wily EM? WebAS = APACHE Tomcat

SolMan 7.0: Is below ‘SAP Netweaver’ a node ‘<SID>_WAS_<host>’?If Web Application Server Tomcat is used and you have specified the Tomcat technical system of type ‘UNSPECIFIC’, you will see an entry for the Tomcat data with a node name like: <SID>_WAS_<host>. The tomcat is also JAVA based. The name of the Node is defined in the registry key if tomcat runs on windows. If it runs on UNIX it is defined it is set as environment variable (setenv.sh). Note: <SID> at the beginning of the name is the <SHORT_SID> (3 characters)Note: Details are described in the attachment “ISJavaAgentForBOE3x.pdf” of SAP Note 1357901.

SolMan 7.1: Is below the BOE-host entry a node ‘Tomcat’ -> ‘<host>_<port>’?If Web Application Server Tomcat is used in SolMan 7.1 you will use technical system type ATC for this system. Then you will see a node named “Tomcat” and below a node named “<host>_<port>”.Note: Details can be found in Solman 7.1 Setup WIKI: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Apache+Tomcat+System+in+Solman+7.1

Is below the ‘<host>_<port>’ or ‘<SID>_WAS_<host>’ a node named ‘SAP BOE’ and ‘Tomcat’?For Tomcat you can define which profile is used in the ‘Tomcat configuration’ application. Windows: Start -> All Programs -> Tomcat -> Tomcat configuration -> Java -> Java Options:

In that profile (e.g. “/usr/SAP/ccms/wily/IntroscopeAgent_tomcat.profile”) the jar files that are used for instrumentation are defined - for BO Web App 3.1 we should have:“introscope.autoprobe.directivesFile=sap_typical.jar,sap_tomcat_typical.jar,sap_tomcat_full.jar,sap_boenterprise.jar”.These files should be available in folder ‘/usr/sap/ccms/wily’. Otherwise you have to update Wily Agent as described in SAP Note 1273028 to get the BOE and Tomcat instrumentation (jar files). The Wily Agent version can be checked in the log files ‘usr/sap/ccms/wily/log’.

WebAS = IBM WebSphere If Web Application Server IBM WebSphere is used, please check Sap Note: 1418638 Wily Introscope Agent for IBM

WebSphere Application ServerNote: Details can also be found in Solman 7.1 Setup WIKI:http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+IBM+WebSphere+in+Solman+7.1

WebAS = SAP J2EE Is below ‘SAP Netweaver’ a node like ‘<SID>_DVEBMGS89_server0?

If Web Application Server SAP J2EE Engine is used and you have specified the WAS technical system of type ‘JAVA’, you will see an entry for the SAP J2EE data with a node name like: <SID>_DVEBMGS89_Server0. This is the standard naming convention for setup of a J2EE engine. Note: Details are described in SAP Note 1357901.

Is the technical system setup correct in SolMan?As BO Enterprise XI 3.1 does not deliver his information to SLD, the technical system and product system has to be created manually in Solution Manager as described in the Setup Guide. BO 4.0 has an automatic delivery to SLD so the technical system is automatically available in LMDB.

Do the names of the BOE system components follow the naming rules?The systems of a BOE must follow dedicated naming rules to get all data in an EWAlert report. There will be one EWA scheduled for the BOE server system and we try to read data for the WebAS component into this EWA by reading data from the BW of the Solution Manager using a dedicated LONG_SID.

Are the technical system names o.k.?Check if the system names follow those rules:Business Objects Cluster component: LONG_SID = <SID>_BOEWeb Application Server (WebAs) component: LONG_SID = <SID>_WASNote: <SID> has to be the same for all systems. For SAP J2EE configurations only: The <SID> of the BOE cluster is determined by the <SID> of the SAP J2EE Engine!

Are the product system names o.k.?The name of the Product Systems must be identical to the name of the Technical Systems. Check in SMSY or LMDB Editor.Example for BO server:

Are the instance names o.k.?Check Naming rules for instances of technical system in SMSY:BOE_<hostname> for the BOE cluster componentWAS_<hostname> if WebAs = Tomcat, Websphere etc.JC<nn> / J<nn> / DVEBMGS<nn> / D<nn> if WebAs = SAP J2EE engine.For Tomcat WebAs only: The name of the instance in SMSY must correspond to the agent naming in Tomcat instrumentation.SMSY instance: WAS_<hostname>Tomcat instrumentation: <SID>_WAS_<hostname>If there are multiple Tomcat instances running on the same server, append numbers to distinguish the instancesExample for BO Server:

Are all relevant software components added to the technical system?Select the technical system of BO Server in SMSY or in LMDB Editor and check if all SCVs mentioned in the setup guide are listed:

Are all main instances flagged as diagnostics relevant?Select the product system of BO Server in SMSY and check if all main instances mentioned in the setup guide have the technical system assigned and are flagged as Relevant:

Note: Main instance ‘BOE WEB APPLICATION JAVA’ should only be relevant at the WebAS system, not at the BOE server system.

Is data available in Workload InfoCube for BO and WebAp systems? Is data visible in E2E WA?

Check in ‘Root Cause Analysis’ work center -> End-to-End Analysis -> Select BO server and WebAp system -> Workload Analysis -> Overview -> Dialog

Are the extractors running successfully and returning data? -Check in SolMAn 7.0 ‘Root Cause Analysis’ work center -> Extractor FWK Administration-> Managed System -> Select BO

server or WebAp system ID-> Check if extractors of Name=‘Workload Analysis (Introscope Data)’ are active and check the logs if they return data.-Check in SolMan 7.1 ‘SAP Solution Manager Administration’ work center -> Infrastructure -> Framework -> Extractor Framework -> Filter -> Select BO server and WebAp system IDs-> Check if extractors are active and check the logs if they return data.

If the extractor does not return any data and the entry in Wily seems o.k. you have to execute the extractor in SolMan backend. Use transaction SE37 and enter the extractor function module, RFC Target = SOLMANDIAG, set Uppercase/Lowercase=X and enter the other details from the extractor. You can copy them from table ‘E2E_ACTIVE_WLI’. Enter a timestamp as Required Records where you know that there is data in WILY EM. Example for BO WebAp Component:

Required Records input depends on the ‘date-format’ of the SolMan (19.07.2012 or 07/19/2012)

Execute the function module and check if there are entries in the EXTRACTOR_DATA table:

If not check the log of the SolMan JAVA stack by using transaction AL11 (make sure you do it on the same app server as you run the function module) -> Doubleclick on DIR_INSTANCE -> j2ee -> cluster -> server0 -> log. Sort the entries by last change date and time to get the most current changed file on top of the list. Open the most current ‘Default Trace…trc’ file and search for the SID of your system inside this trace file.

If you don’t find an entry you have to increase the log level of trace location ‘com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor’ to ‘DEBUG’ in Netweaver Admin Tool (NWA).If you still do not find a hint why no data is returned, you can additionally increase the log level of ‘com.sap.sup.admin.wily.jdbc.AgentMapper’ to ‘DEBUG’ to get information which agent name is expected.

Is an EW Alert scheduled for the BOE cluster system? Is the system assigned to a logical component?

Assignment can be checked for SolMan 7.0 in SMSY or for SolMan 7.1 in ‘SAP Solution Manager Configuration’ work center -> ‘Managed System Configuration’ -> select the right system and push ‘Configure System’. In Step 1 ‘Select Product’ push ‘Display Product System’. Mark the Product System and push ‘Where Used’ to see the logical components and the solution to where this system is assigned.In Step 8 ‘Create Logical Components’ check the rating and push ‘GoTo System Landscape’. You will be directed to ‘SMSY’ to create the logical components and solution assignment.

Is the system part of a solution? Assignment can be checked for SolMan 7.0 in SMSY or for SolMan 7.1 in ‘SAP Solution Manager Administration’ work

center -> ‘Solution’ -> mark the line with the right solution to see the details (Logical components and Systems) assigned to it below in the table or click the solution name link to jump into ‘Solution Directory’.

Is an EWAlert scheduled for this system? SolMan 7.1: EWA schedule can be checked in: ‘System Monitoring’ work center -> Setup -> Earlywatch Alert and Services

Configuration -> Configuration for a single Solution. SolMan 7.0: EWA schedule can be checked in transaction ‘solution_manager’ -> Select the right solution -> Operations

Setup -> Solution Monitoring -> Earlywatch Alert

Is there content in the EWAlert report? SolMan 7.1: Check the EWA report in ‘System Monitoring’ work center -> Report -> Report View=SAP EarlyWatchAlert.

Select the right Product System and the last instance -> Push ‘Display HTML report’. SolMan 7.1: Check the EWA report in ‘SAP Engagement and Service Delivery’ work center -> Report -> Reporting

Tools=EarlyWatchAlert. Select the right solution and date-range -> Push ‘Search’. You can create a WORD report or display the HTML report.

SolMan 7.0: EWA content can be checked in transaction ‘solution_manager’ -> Select the right solution -> Operations -> Solution Monitoring -> Earlywatch Alert

2. StepByStep Checklist for missing EWA data for BI Platform 4.XCentral Setup Notes are: 1653689 SolMan 7.1: Managed Sys Setup - BI Platform 4.01646341 EarlyWatch Alert for SAP BusinessObjects IDD/EIM

SolMan 7.1 Setup Wiki: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape

Is data available for BOE Server in WILY EM?Screenshot in Investigator of a system with longSID: “DEW”

Are there two host entries – one in capital and one in lower case letters for the same host?All data has to be linked to one host node in Wily Introscope Investigator which is written in lower case letters. You can force the lower case hostname also to be used by the Introscope agent by adding the following line into the Introscope agent profile:introscope.agent.hostName=<hostname>For BO 3.1 changes have to be performed directly in the profile (e.g. /usr/sap/ccms/wily/IntroscopeAgent.profile). The path is defined in the startup parameters of MDAS and Tomcat MDAs and Tomcat are using same profile if it is manually setup like described in SAP Note 1357901 (path to tomcat config file is set in windows registry).For BO 4.X you have to add this into the file IntroscopeAgent.template located in the directory:<drive>: \Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wilyThis will correct the hostname used for the BOE server side java based agents.Additionally the Web App Server uses a java based Introscope agent for which you can set the hostname in the same way.

The profile is located under <drive>:/usr/sap/ccms/wily.For Tomcat it is named: IntroscopeAgent_tomcat.profile For Websphere it is named: IntroscopeAgent_websphere.profile.Do not try to change the hostname in SLD or LMDB! Hostnames have to be written in lower case letters in SolMan.

Is below the BOE-host entry a node “SAP HostAgent process” -> “SAP HostAgent SMD…”?-If there is more than one SMD Agent (‘SAPHostAgent SMD…’) you have to find the right one linked to your SolMan. Open the node “SAPHostAgent SMD...” -> “SelfMonitoring” -> “Solution Manager” -> Check values at “Host” and “Port”-If this node is not available please check first the settings for WILY EM Port and Host. Use AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> Application Resources -> ‘IntroscopeSAPAgent.profile’ -> Scope = SMD Agent of the BOE System -> Download.Maybe a restart of the SMD agent is necessary after changing some settings here.

Is there below a node “BOBJ ENTERPRISE” -> “<ShortSID>”? If this node is not available please check first the NCS settings.

Are the placeholder settings in CMC correct?The generic definition of the collection for NCS metrics can be found in “ncs.conf”. This file is generated automatically with every restart of the BOE cluster from data inside the CMC and from data inside the file “ncs.template”. Therefore you have to maintain the value in the placeholder section of the BOE cluster. Choose Servers->Nodes->right mouse click on the node and select ‘Placeholders’. Host and Port must fit to the settings in SAPAgentConfig.xml and NCSInstrumentLevelThreshold must be > 0 (normally to 10).The default value for port 59818 should be changed to 6404 if there are problems with the NCS communication.

Is below the <ShortSID> a node “BOE_KPIs”?If not, then the KPI script is not running. Execute the script manually in RCAWorkcenter -> Host Analysis -> -> Select the right host -> OSCommandConsole:System = <BOE System>; Group = BOE; Command = DumpKPIs => Send Command.-Check the parameter settings in AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.remoteos -> Scope = SMD Agent of the BOE SystemAll parameters have to be set and the names of the parameters must be:ENV_SID_<LONGSID>_BOE_AUTH_TYPE = ENV_SID_<LONGSID>_BOE_CMS ENV_SID_<LONGSID>_BOE_CMS_PWD ENV_SID_<LONGSID>_BOE_CMS_SE_PWD ENV_SID_<LONGSID>_BOE_CMS_USRENV_SID_<LONGSID>_BOE_DIROne example: for a parameter name with longsid = DEW_BOE => ENV_SID_DEW_BOE_BOE_AUTH_TYPE.Note: We have to have two times the “BOE” in the parameter name as it is part of the default BOE LONGSID and part of the default parameter name!-Check the content of AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> Application Resources -> ‘SAPAgentConfig.xml’-> Scope = SMD Agent of the BOE System -> Download.SocketDestination -> Port has to be set to the default: 59818 [Please use 6404 instead of 59818]. It is only changed if you have more than one SMD agent on the host. Then it has to be the same port value as written in “ncs.conf” file.-Check the content of AgentAdminWC -> Application Configuration -> com.sap.smd.agent.application.wilyhost -> ‘SAPAgentConfig.xml’-> Scope = SMD Agent of the BOE System -> Download.command: bo.dump_kpis -> longsid has to be set to the right value “<LONGSID>” and prefix must be: “BOBJ ENTERPRISE|<ShortSID>”

Is below the “SAP HostAgent…” a node “SBOB ENTERPRISE\<BO Clustername>”All C++ type processes send their data to Wily via the NCS library and the SMD agent. All the data from those processes are visible below this “SBOB ENTERPRISE\<BO Clustername>” node.

-If this is not visible please check first the NCS settings as described above.Check the following settings in file “ncs.conf” “instrument_level_threshold=10” -> if the value is 0 no data is send.“system_name= SBOB ENTERPRISE\<BO clustername>”“agent_host=localhost”“agent_port=59818” [Please use port 6404 instead of 59818] -> The values for port have to be similar to the value in ‘SAPAgentConfig.xml’

Is below the BOE-host entry a node “SBOB ENTERPRISE\<BO Clustername>”All JAVA-type processes send their data to Wily via the ‘Introscope Agent’ that runs inside the JVM of the application. All the data from those applications are visible below this “SBOB ENTERPRISE\<BO Clustername>” node.

Are below ‘SBOB ENTERPRISE\<BO Clustername>’ the nodes for Explorer Servers?If SBOP Explorer 4.X is used, it is running on top of BI Platform 4.X. All processes are JAVA based processes so we should see 4 entries below the “SBOB ENTERPRISE\<BO Clustername>” node:explorerExploration_<host>.ExplorerExplorationSeverexplorerMaster_<host>.ExplorerMasterSever explorerIndex_<host>.ExplorerIndexSeverexplorerSearch_<host>.ExplorerSearchSeverThe agent name for these servers are delivered via SLD data supplier of BI Platform / BI Explorer.

Is data available for WebApplicationServer (WebAS) in Wily EM? WebAS = APACHE Tomcat

Is below the BOE-host entry a node ‘Tomcat’?If Web Application Server Tomcat is used in SolMan 7.1 you will use technical system type ATC for this system. Then you will see a node named “Tomcat” and below a node named “<host>_<port>” (port is the service port of tomcat).Note: Details can be found in Solman 7.1 Setup WIKI: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Apache+Tomcat+System+in+Solman+7.1

Is below the ‘<host>_<port>’ a node named ‘SAP BOE’ and ‘Tomcat’?For Tomcat you can define which profile is used in the ‘Tomcat configuration’ application. Windows: Start -> All Programs -> Tomcat -> Tomcat configuration -> Java -> Java Options:

In that profile (e.g. “/usr/SAP/ccms/wily/IntroscopeAgent_tomcat.profile”) the jar files that are used for instrumentation are defined - for BO Web App 4.x we should have:“introscope.autoprobe.directivesFile=sap_typical.jar,sap_tomcat_typical.jar,sap_tomcat_full.jar,sap_boe_webapp.jar”.These files should be available in folder ‘/usr/sap/ccms/wily’. Otherwise you have to update Wily Agent as described in SAP Note 1273028 to get the BOE and Tomcat instrumentation (jar files). The Wily Agent version can be checked in the log files ‘usr/sap/ccms/wily/log’.Note: You have to remove sap_bo_enterprise.jar and use only sap_boe_webapp.jar as described in SAP Note 1540591. You must not have both jar files mentioned as introscope.autoprobe.directivesFile!

WebAS = IBM WebSphere If Web Application Server IBM WebSphere is used, please check Sap Note: 1418638 Wily Introscope Agent for IBM

WebSphere Application Server

Note: Details can also be found in Solman 7.1 Setup WIKI:http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+IBM+WebSphere+in+Solman+7.1

WebAS = SAP J2EE Is below ‘SAP Netweaver’ a node like ‘<SID>_DVEBMGS89_server0?

If Web Application Server SAP J2EE Engine is used and you have specified the WAS technical system of type ‘JAVA’, you will see an entry for the SAP J2EE data with a node name like: <SID>_DVEBMGS89_Server0. This is the standard naming convention for setup of a J2EE engine. Note: Details are described in SAP Note 1357901.

Is the technical system setup correct in SolMan?As BI Platform4.X has an automatic delivery to SLD so the technical system is automatically available in LMDB.

Do the names of the BOE system components follow the naming rules?The systems of a BOE must follow dedicated naming rules to get all data in an EWAlert report. There will be one EWA scheduled for the BOE server system and we try to read data for the WebAS component into this EWA by reading data from the BW of the Solution Manager using a dedicated LONG_SID.

Are the technical system names o.k.?Check if the system names follow those rules:Business Objects Cluster component: LONG_SID = <SID>_BOEWeb Application Server (WebAs) component: LONG_SID = <SID>_WASNote: <SID> has to be the same for all systems. For SAP J2EE configurations only: The <SID> of the BOE cluster is determined by the <SID> of the SAP J2EE Engine!

Are the product system names o.k.?The name of the Product Systems must be identical to the name of the Technical Systems. Check in SMSY or LMDB Editor.Example for BO server:

Are the instance names o.k.?Check Naming rules for instances of technical system in SMSY:BOE_<hostname> for the BOE cluster componentWAS_<hostname> if WebAs = Tomcat, Websphere etc.JC<nn> / J<nn> / DVEBMGS<nn> / D<nn> if WebAs = SAP J2EE engine.For Tomcat WebAs only: The name of the instance in SMSY must correspond to the agent naming in Tomcat instrumentation.SMSY instance: WAS_<hostname>Tomcat instrumentation: <SID>_WAS_<hostname>If there are multiple Tomcat instances running on the same server, append numbers to distinguish the instancesExample for BO Server:

Are all main instances flagged as diagnostics relevant?Select the product system of type “SAP Business Object cluster” in LMDB technical system editor (transaction LMDB) and check if all main instances mentioned in the setup guide have the technical system assigned and are flagged as ‘Diagnostics

Relevant’:

Note: Main instance ‘BOE WEB APPLICATION JAVA’ should only be relevant at the WebAS system, not at the BOE server system.

Is data available in Workload InfoCube for BO and WebAp systems? Is data visible in E2E WA?

Check in ‘Root Cause Analysis’ work center -> End-to-End Analysis -> Select BO server and WebAp system -> Workload Analysis -> Overview -> Dialog

Are the extractors running successfully and returning data? -Check in SolMan 7.1 ‘SAP Solution Manager Administration’ work center -> Infrastructure -> Framework -> Extractor

Framework -> Filter -> Select BO server and WebAp system IDs-> Check if extractors are active and check the logs if they return data.

If the extractor does not return any data and the entry in Wily seems o.k. you have to execute the extractor in SolMan backend. Use transaction SE37 and enter the extractor function module, RFC Target = SOLMANDIAG, set Uppercase/Lowercase=X and enter the other details from the extractor. You can copy them from table ‘E2E_ACTIVE_WLI’. Enter a timestamp as Required Records where you know that there is data in WILY EM. Example for BO WebAp Component:

Required Records input depends on the ‘date-format’ of the SolMan (19.07.2012 or 07/19/2012)

Execute the function module and check if there are entries in the EXTRACTOR_DATA table:

If not check the log of the SolMan JAVA stack by using transaction AL11 (make sure you do it on the same app server as you run the function module) -> Doubleclick on DIR_INSTANCE -> j2ee -> cluster -> server0 -> log. Sort the entries by last change date and time to get the most current changed file on top of the list. Open the most current ‘Default Trace…trc’ file and search for the SID of your system inside this trace file.

If you don’t find an entry you have to increase the log level of trace location ‘com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor’ to ‘DEBUG’ in Netweaver Admin Tool (NWA).If you still do not find a hint why no data is returned, you can additionally increase the log level of ‘com.sap.sup.admin.wily.jdbc.AgentMapper’ to ‘DEBUG’ to get information which agent name is expected.

Is an EW Alert scheduled for the BOE cluster system? Is the system assigned to a logical component?

Assignment can be checked for SolMan 7.1 in ‘SAP Solution Manager Configuration’ work center -> ‘Managed System Configuration’ -> select the right system and push ‘Configure System’. In Step 1 ‘Select Product’ push ‘Display Product System’. Mark the Product System and push ‘Where Used’ to see the logical components and the solution to where this system is assigned.In Step 8 ‘Create Logical Components’ check the rating and push ‘GoTo System Landscape’. You will be directed to ‘SMSY’ to create the logical components and solution assignment.

Is the system part of a solution? Assignment can be checked for SolMan 7.1 in ‘SAP Solution Manager Administration’ work center -> ‘Solution’ -> mark the

line with the right solution to see the details (Logical components and Systems) assigned to it below in the table or click the solution name link to jump into ‘Solution Directory’.

Is an EWAlert scheduled for this system? SolMan 7.1: EWA schedule can be checked in: ‘System Monitoring’ work center -> Setup -> Earlywatch Alert and Services

Configuration -> Configuration for a single Solution.

Is there content in the EWAlert report?

SolMan 7.1: Check the EWA report in ‘System Monitoring’ work center -> Report -> Report View=SAP EarlyWatchAlert. Select the right Product System and the last instance -> Push ‘Display HTML report’.

SolMan 7.1: Check the EWA report in ‘SAP Engagement and Service Delivery’ work center -> Report -> Reporting Tools=EarlyWatchAlert. Select the right solution and date-range -> Push ‘Search’. You can create a WORD report or display the HTML report.

3. KPI script

3.1.KPI script return errors (SP1)

Description:Check if F:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\ KPIScript.jar is available.

Solution:

Example:

Manifest in KPI_SCRIPT.jar: (in 3.1 version there are some libraries missing)

Manifest-Version: 1.1Ant-Version: Apache Ant 1.7.0Created-By: 1.4.2_08-b03 (Sun Microsystems Inc.)Product-Name: KPIScript (C)Main-Class: com.sap.kpi.KPIScriptClass-Path: lib/cecore.jar lib/celib.jar lib/ceplugins_core.jar lib/cesession.jar lib/corbaidl.jar lib/ebus405.jar lib/logging.jar lib/aspectjrt.jar lib/ceaspect.jar lib/TraceLog.jar lib/bcm.jar lib cecore.jar celib.jar ceplugins_core.jar cesession.jar corbaidl.jar ebus405.jar logging.jar aspectjrt.jar ceaspect.jar TraceLog.jar bcm.jar .

3.2.KPI Script fails due to wrong variables:Description:The Command „DumpKPIs“ is calling the “KPIScript.jar” (D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib) und this executes everything that is mentioned in “E:\Program Files\Business Objects\common\4.0\java\KPIQuery.xml”.KPI script fails on some servers. The reason why it fails on hosts 20-22 is that you have entered a wrong value in the connection parameters.

Solution: Please change the setting in SolMan Agent Administration for all hosts/agents for the variable ENV_SID_BOP_BOE_BOE_CMS (LONGSID = BOP_BOE) to “st-w1018:6400”. This change has to be performed in Solution Manager -> AgentAdministration -> Applications Config -> com.sap.smd.agent.application.remoteosIt is not necessary to have different entries here, as all can connect to the same CMS.

To avoid extraction the KPI data for every CMS server and therefore getting wrong data we would have to delete the action from SAPAgentConfig.XML (HostAgentSetup).

The value of ENV_SID_BOP_BOE_BOE_CMS is set different - depending on the host, here it is set to “st-w1020:6400”.But on “st-w1020” there is no CMS server active, so it cannot connect to “st-w1020:6400”.On the hosts “st-w1018 and “st-w1019” there is a CMS and therefore it works on those hosts.

3.3.KPI Script fails due to double performed setup with different SID:

Description:KPI script is not working. In the log file of the agent you still can see the variables. The problem is that the customer did the setup several times with different SIDs. For every SDI there is an Action written to the “SAPAgentConfig.xml” file. Unfortunately the action has the same name “boe_kpis”. Now the newest SID is on top, but the last action in the xml file “wins” and so he tries to perfom the action for the old SID and cannot find the fitting parameters.

Solution: Remove the entry for the old SID from the file “SAPAgentConfig.xml”. Download the file, remove the entry and upload it again to the right agent.

Example: Error message in the Agent log:################### Jun 3, 2011 1:36:43 AM [Thread[boe_kpis,5,main]] Error com.sap.smd.wily.hostagent.action.RemoteOsCommandAction - doRun(): Exception reading command output [EXCEPTION] com.sap.smd.plugin.remoteos.exception.CommandExecutionException: Error executing OS command [command:..\..\..\javasdk\bin\java -jar "%BOE_DIR% \common\4.0\java\KPIScript.jar" -cms %BOE_CMS% -user %BOE_CMS_USR% - pass %BOE_CMS_PWD% -auth secEnterprise] [sessionId:boe_kpis_1307054203732]: Working directory is not consistent: C:\usr\sap\SMD\SMDA97\SMDAgent\%BOE_DIR%\common\4.0\java; nested exception is: java.io.FileNotFoundException: Working directory is not consistent: C:\usr\sap\SMD\SMDA97\SMDAgent\%BOE_DIR%\common\4.0\java at com.sap.smd.plugin.command.cmd.AbstractOsCmd.execute (AbstractOsCmd.java:176)

Remoteos configuration of the agent : The variables are defined for SID(Longsid!!) =”BES”:

There are two entries for action ‘boe_kpis’ in SAPAgentConfig-.xml. One for SID=”BES” and one for SID=”BO_”. The right SID is ‘BES’, but he tries to execute the action for SID = “BO_” – so he cannot find the values for the variables which are defined for SID=”BES”.

3.4.KPI Script fails when it is executed automatically but runs in remote OS console:

Description:KPI script is only working when you execute it manually in the remote OS command console. In the log file of the agent you still can see the variables – he cannot resolve the names. The problem is that the customer did a setup with a different SID or LONGSID. So there is a different SID mentioned in the action section of “SAPAgentConfig.xml” file than we have in the RCA, and so he tries to perform the action for the old SID and cannot find the fitting parameters.

Solution: Correct the entry for the LONGSID in the file “SAPAgentConfig.xml”. Download the file, change the entry and upload it again to the right agent.

Example: System LONGSID = “PBO_BOE”Wrong setting in SAPAgentConfig.xml, probably due to an older setup with a different LONGSID=”PBO_CMS” instead of “PBO_BOE”.

The KPI script runs if you execute it manually (sapos command console) on the CMS servers as it takes the right LONGSID that fits to the variables:

3.5.KPI Script for BOE 4.0 fails when executed in remote OS console:Description:KPI script cannot be executed in Remote OS command console. Error: Invalid Input.

Solution: Execute Setup Step 8 from SAP Note: 1653689 SolMan 7.1: Managed Sys Setup - BI Platform 4.0And copy the content of the attached BOE4_scripts.zip to the right place in your BOE Cluster system.

Example:

3.6.KPI Script runs into timeout or runs very long:Description:KPI script runs very long due to many entries in the CMS database that have to be read, e.g. hundred-thousand WebI reports

Solution: Analyze the root cause of the time out by running the KPI script in OS-Command console with the ‘–debug’ option and check which metric takes most of the time. (-help shows the possible input parameters). Maybe you have to comment this metric in the script to overcome the timeout.

Example:

3.7.Test KPI Script for BOE 4.0 direct on OS level:Description:You want to execute the KPI script directly on OS level

Solution: How to execute manual kpi script (Windows)

1. Switch to directory where “KPIScript.jar” is located (normally it is in “%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\”)

2. Set the variables3. Execute the script4. In case of trouble use –debug option (use –help for further options)

Example: Open CMD consolecd D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\libSet BOE_DIR=D:\Program Files (x86)\SAP BusinessObjectsSet BOE_CMS=localhost:6400Set BOE_CMS_USR=administratorSet BOE_CMS_PWD=******..\..\win64_x64\jdk\bin\java -jar KPIScript.jar -cms %BOE_CMS% -user %BOE_CMS_USR% -pass %BOE_CMS_PWD% -debug

4. Extractors are scheduled also on MAI level for PPMSID “01200615320900003804” in SM 7.1

Description:The problem is that there was an error during transport of changes in the E2E_TEMPLEXTR table in our development system. Therefore we have double entries in the extractor definition table in SP1. For BOBJ then extractors are scheduled on SVC level (correct) and on Main Instance level (wrong).Solution: Implement the summary Note 1552585 that delivers a note with a report that should delete the entries from the E2E_TEMPLEXTR table.As a workaround you can delete the entries for the BOBJ system manually from the E2E_ACTIVE_WLI table.

Example:

Solman_setup -> Implement summary note that consist the note that fixes that problem.

5. Missing WebI data (NCS) in E2E WA for BOE 4.X

Description:The generic definition of the collection for NCS metrics is available in the file “ncs.conf”. This file is generated automatically with every restart of the BOE cluster from data inside the CMC-Placeholders and from data inside the file “ncs.template”. If you want to change something these are the two places to change. Afterwards please restart the BOE cluster and the SMD agent. For testing the restart of one server may be enough to see if something changes in WilyIntroscope.

5.1.Wrong node names for the BOE system (‘_’ instead of ‘\’):

Description:The names of the nodes in Wily are defined in the “ncs.conf” file. With BOE 4.0 the file is created automatically with every restart. Therefore manual changes in the file make no sense.

Solution: In BOE4.0 you have to maintain the template “ncs.template” and change the name there. Restart the BOE system as well as the agent after such a change. In the meantime we corrected the entry in the config.xml so that we get data independent if the node name contains ‘_’ or ‘\’.

Example:

For NCS data: In file WIN: “F:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf\ncs.template” UNIX: “…/sap_bobj/enterprise_xi40/conf/ncs.template Change:system_name=SBOP ENTERPRISE_%ClusterName%tosystem_name=SBOP ENTERPRISE\%ClusterName%

Afterwards restart the BOE system as the new “ncs.conf” file has to be created with the new system name

For JAVA data:In file: “F:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\IntroscopeAgent.template”Change:introscope.agent.customProcessName=SBOP ENTERPRISE_%ClusterName%tointroscope.agent.customProcessName=SBOP ENTERPRISE\\%ClusterName%Afterwards restart the BOE system as the JAVA processes have to reload the new system name

Also restart the SMD agent afterwards!!!

For the WebAS node it is depending on the type of WebAs. For tomcat you have to change the agent name in the registry key. For BOE 3.1 see SAP Note 1357901.

5.2. Wrong NCS Metrics Settings in CMC

Description:The generic definition of the collection for NCS metrics can be found in “ncs.conf”. This file is generated automatically with every restart of the BOE cluster from data inside the CMC and from data inside the file “ncs.template”. Solution: Therefore you have to maintain the value in the placeholder section of the BOE cluster. Choose Servers->Nodes->right mouse click on the node and select ‘Placeholders’Please use port value 6404 instead of 59818.

6. Missing CMS Tab in SM 7.0:

Description:If you open RCA Workcenter and select Workload Analysis for a BOE 3.X System on Solution Manager 7.0 then you miss the ‘CMS’ Tab.

Solution:

In the config.xml of SolMan 7.0 before SP 26 the “DataView” area is missing, so we collect the KPIs, but we do not display them.The customer has to upgrade to SP26 to see the KPI section.

Example:

Config.xml:…<MainInstance Name="CENTRAL MANAGEMENT SERVER" MI_PPMS_ID="3" P_PPMS_ID="01200314690800000337">

<DataViews><ViewGroup Name="BOE KPIs">

<View Name="General KPIs"><Variable Name="ObjectType" Value="BOE_KPI_GENERAL"/><WebTemplate Name="E2E BOE KPIs"/>

</View>….

7. How should Host Agent setup look like (BOE 4):

Description:What is important in the file SAPAgentConfig.xml Solution: Socket Destination

Port=59818 [Instead of 59818 please use port 6404] (if there are several agents running on one logical host you must have different ports for each agent and update the “ncs.conf” file with all ports)Action for KPI script:

Longsid must be the same as the longsid in the landscapeOnly one entry allowed – remove all entries with the wrong longsids (with every

WilyHostAgent setup for a different longsid there will be an entry added)

Example:

8. Wrong Agent name for Tomcat – SAP Note 1540591 -> Tomcat Setup

Description:

Solution:

If Tomcat(32Bit) run on Windows(64Bit) then the registry key is on a different place (Wow6432Node)

Node name in registry is normally: “BOEXI40Tomcat” if the tomcat was installed by BOBJ.

On windows it seems that the name of the service is similar to this registry key. There are two ways to double-check or find the name of the right node in registry:

1. Use: Start -> Tomcat -> Tomcat Configuration -> Service Name should be the right name

2. Or in Service Manager (services.msc) select service ‘Apache Tomcat 6...’ -> Properties -> Service Name should be the right name

9. Overload on Extraction via SOLMANDIAGDescription: We see very often overload situation on the data extraction – in most cases on SOLMANDIAG source (Check Job log) of the batch job

Solution: Job log of batch job ‘EFWK Resource Manager’ has to run every minute!Check if there are enough resources defined on ABAP for SOLMANDIAG and on JAVA Connection Pool. Normally the settings on the EM need not to be changed.Sometimes it also helps to increase the number of worklist items on ABAP side.

a) ABAP stack:

b) JAVA stack

Solman_setup -> Basic Configuration-> Specify User&Connectivity Data-> SolutionManger Internal Connectivity->Create RFC Connectivity (WEBADMIN)

Here you can define the “Java Connection Pool” setting: (A good starting point is a value of 16)

c) There is also a setting on the WILY EM that is set per default to 2 connections that can be handled.

10. Missing process information from SAPOSCOLDescription: There is no data about processes visible in Wily EM and E2E WAIn case of problems check if service/process “SAPHostCtrl” is running. Check the log file \usr\sap\PRFCLOG\dev_coll for details.

Solution: Check content of file “procmon.ini” in folder \usr\sap\PRFCLOG\procmon.Enable SAPOSCOL process monitoring as described in SAP Note 1357901 -> 6.2 Enable Saposcol process monitoring

Example:$PROC# Unix process names## BOE 4.0 processes#java USER=* MTE_CLASS=BOE MTE_NAME=JavaProcesses CUSTOM_GROUP=BOE#boe_cmsd USER=* MTE_CLASS=BOE MTE_NAME=CMS CUSTOM_GROUP=BOE#boe_crcached.bin USER=* MTE_CLASS=BOE MTE_NAME=CrystalCacheServer CUSTOM_GROUP=BOE#AADashboard USER=* MTE_CLASS=BOE MTE_NAME=DashboardServer CUSTOM_GROUP=BOE#boe_eventsd USER=* MTE_CLASS=BOE MTE_NAME=EventServer CUSTOM_GROUP=BOE#boe_crprocd USER=* MTE_CLASS=BOE MTE_NAME=CrystalProcessingServer CUSTOM_GROUP=BOE#boe_crprocd.bin USER=* MTE_CLASS=BOE MTE_NAME=CrystalProcessingServer CUSTOM_GROUP=BOE#boe_crystalrasd USER=* MTE_CLASS=BOE MTE_NAME=CrystalRAS CUSTOM_GROUP=BOE#boe_crystalrasd.bin USER=* MTE_CLASS=BOE MTE_NAME=CrystalRAS CUSTOM_GROUP=BOE#boe_crystalras USER=* MTE_CLASS=BOE MTE_NAME=CrystalRAS CUSTOM_GROUP=BOE#boe_xcprocd USER=* MTE_CLASS=BOE MTE_NAME=XcelsiusProcServer CUSTOM_GROUP=BOE#boe_filesd USER=* MTE_CLASS=BOE MTE_NAME=FileServer CUSTOM_GROUP=BOE#ConnectionServer USER=* MTE_CLASS=BOE MTE_NAME=ConnectionServer CUSTOM_GROUP=BOE#boe_xccached USER=* MTE_CLASS=BOE MTE_NAME=XcelsiusCacheServer CUSTOM_GROUP=BOE#WIReportServer USER=* MTE_CLASS=BOE MTE_NAME=FileServer CUSTOM_GROUP=BOE#boe_jobsd USER=* MTE_CLASS=BOE MTE_NAME=JobServer CUSTOM_GROUP=BOE#AAAnalytics USER=* MTE_CLASS=BOE MTE_NAME=DashboardServer CUSTOM_GROUP=BOE## other relevant process names to be added here:## Windows process names##Process USER= MTE_CLASS= MTE_NAME= CUSTOMGROUP=tomcat6.exe* USER=* MTE_CLASS=BOE MTE_NAME=Tomcat CUSTOM_GROUP=BOEsia.exe* USER=* MTE_CLASS=BOE MTE_NAME=Sia CUSTOM_GROUP=BOECMS.exe* USER=* MTE_CLASS=BOE MTE_NAME=CMS CUSTOM_GROUP=BOEcrproc.exe* USER=* MTE_CLASS=BOE MTE_NAME=JobServer CUSTOM_GROUP=BOEJava.exe* USER=* MTE_CLASS=BOE MTE_NAME=Java CUSTOM_GROUP=BOEAADashboard.exe* USER=* MTE_CLASS=BOE MTE_NAME=DashboardServer CUSTOM_GROUP=BOEcrcache.exe* USER=* MTE_CLASS=BOE MTE_NAME=CrystalCacheServer CUSTOM_GROUP=BOEcrproc.exe* USER=* MTE_CLASS=BOE MTE_NAME=CrystalProcessingServer CUSTOM_GROUP=BOEEventServer.exe* USER=* MTE_CLASS=BOE MTE_NAME=EventServer CUSTOM_GROUP=BOEfileserver.exe* USER=* MTE_CLASS=BOE MTE_NAME=FileServer CUSTOM_GROUP=BOEWIReportServer.exe* USER=* MTE_CLASS=BOE MTE_NAME=FileServer CUSTOM_GROUP=BOEcrystalras.exe* USER=* MTE_CLASS=BOE MTE_NAME=CrystalRAS CUSTOM_GROUP=BOEAAAnalytics.exe* USER=* MTE_CLASS=BOE MTE_NAME=DashboardServer CUSTOM_GROUP=BOEJobServer.exe* USER=* MTE_CLASS=BOE MTE_NAME=JobServer CUSTOM_GROUP=BOExccache.exe* USER=* MTE_CLASS=BOE MTE_NAME=XcelsiusCacheServer CUSTOM_GROUP=BOEConnectionServer.exe* USER=* MTE_CLASS=BOE MTE_NAME=ConnectionServer CUSTOM_GROUP=BOEConnectionServer32.exe* USER=* MTE_CLASS=BOE MTE_NAME=ConnectionServer CUSTOM_GROUP=BOEjava.exe* USER=* MTE_CLASS=BOE MTE_NAME=JavaProcesses CUSTOM_GROUP=BOE$

Where can you find it in Wily EM:

11. How should workload data in Wily EM for BOE look like

11.1. Business Objects Enterprise XI 3.X Description: Pitfalls: Node names seems to include the longsids:

BOE LONGSID = “B32_BOE”WAS LONGSID = “B32_WAS”

But the names are created via ‘<SID>_<Instance>_<server>’, where SID is the “short SID” and “instance name” is a fixed value (‘BOE_<host>’ or ‘WAS_<host>’) and server is the server name.

Below BOBJ Enterprise there is only the <Short-SID> as Node and below is the node “BOE_KPIs”.The WIReportServer.. and the other native components reporting via NCS may be located below the ‘<Short-SID>’ node or directly below the ‘BOBJ ENTERPRISE’ node (default) – both will work for the extraction.

Solution: This is how the entry in WILY EM should look like:

11.2. SBOP BI Platform 4.X Description: Pifalls:Node names with ‘_’ instead of ‘\’ between “SBOP ENTERPRISE” and “boe cluster name”. The ‘_’ between cluster name and port is o.k.

Solution: This is how the entry in WILY EM should look like.

11.3. In WILY Investigator you see two nodes for a host (‘HOST’ and ‘host’)

Description: In the Investigator you see two nodes for the same host – one in capital letters and one in small letters. The host agent nodes are located below the host with lower case letters and the java agent nodes are reporting to the hosts with capital letters.

The hostname should be delivered from outside discovery (into SLD and LMDB) in lower case. Wily Introscope uses the operating sytem hostname if not otherwise defined in the Introscope agent profile and on Windows the OS hostname is typically upper case. Even the case is irrelevant for the functionality of RootCauseAnalysis and monitoring, you should try to have all data linked to one host node in Wily Introscope Investigator.

Solution: You can force the lower case hostname also to be used by the Introscope agent by adding the following line into the Introscope agent profile:introscope.agent.hostName=<hostname>You have to add this into the file IntroscopeAgent.template located in the directory:<drive>: \Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wilyThis will correct the hostname used for the BOE server side java based agents.Additionally the Web App Server uses a java based Introscope agent for which you can set the hostname in the same way.The profile is located under <drive>:/usr/sap/ccms/wily.For Tomcat it is named: IntroscopeAgent_tomcat.profile For Websphere it is named: IntroscopeAgent_websphere.profile.Do not try to change the hostname in SLD or LMDB!

Example:

12. Missing WebI data (NCS) in Wily EM for BOE 3.1

Description: There is no data for WebI in WILY, E2E WA and EWAlert. In Wily you only see Zombie Account data.

Solution: Check “NCS” configuration file in directory

Win: “C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86”UNIX: For BOE 3.1 on UNIX we cannot monitor WebI, as the NCS.lib for the C++ Components is not used/available for 32 Bit UNIX

Check the following settings in “ncs.conf” “instrument_level_threshold=10” -> if the value is 0 no data is send.“system_name= BOBJ ENTERPRISE|<SHORT_SID>” ->e.g.: “BOBJ ENTERPRISE|B32” or “system_name= BOBJ ENTERPRISE” -> The default is without a <SHORT-SID> node. Both options are o.k.. A <Short-SID> node is only mandatory if you have installed more than one BOBJ systems on a host.“agent_host=localhost”“agent_port=59818” [Please use port 6404 instead of 59818] -> This is the default used. This value needs only be changed if you have more than one SMD agent on the host. Then you need different ports per SMD agent – the value must be similar to the value set in file “SAPAgentConfig.xml” of the different agents (see chapter “How should Host Agent setup look like”).

Example:

When there are problems with the NCS data delivery we can sometimes see the following message in the “<server>_ncs.trc” files of some servers:

You should also check the AgentApplication.log

13. Switch on/off Transaction Trace for BOE 3.X does not work

Description: You want to switch on/off the Transaction Trace functionality for BOE 3.X by executing the script ‘Introscope_TT_on’ or ‘Introscope_TT_off’ in remoteos application. This script wants to set a registry entry in the windows registry. This entry is not set when you execute the script. There is no error message in the log.

Solution: You have to add the agent user (e.g.: SAPServiceDAA) to the administrators group of the server.Don’t forget to restart the agent service or the complete server after granting this user admin rights!You have to check which variables the scripts in command.xml are using. You will see the variables also in the agent application log. Verify that these variables are set correct in the agent REMOTEOS administration.

Example:

Agent log:

Jul 12, 2011 2:47:07 PM [Thread[Thread-4,5,main]] Info filter 1 applied on [bo.introscope.tt_off]Jul 12, 2011 2:47:07 PM [Thread[Thread-4,5,main]] Info Remote OS Command: regedit -s "%BOE_DIR%\BusinessObjects Enterprise 12.0\win32_x86\TransactionTraceOnOff\TransactionTraceOff.reg" - working directory is: D:\usr\sap\DAA\SMDA97\SMDAgent\. - charset is: defaultJul 12, 2011 2:47:07 PM [Thread[Thread-4,5,main]] Info Remote OS Command: property 'oscommand.join.threads' activatedJul 12, 2011 2:47:07 PM [Thread[Thread-4,5,main]] Info Remote OS Command: property 'oscommand.join.threads' activated

14. Missing BO 4.X System in SLD

Description: You cannot perform the managed system setup as the system is not visible in the list for technical systems. The system is also not visible in the SLD.

Solution: The SLD registration of the BOE 4 system is performed after every system restart. It creates the “bobjslddsoutput.xml” file containing the landscape and afterwards sends this to the SLD.It is using the connection data to the SLD from the file ‘connect.key’. Very often the “connect.key” file is missing in the folder: 'C:\Program Files\SAP\hostctrl\exe\' (Windows).In case of problems there are two log files: D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\bobj-sld-ds\ bobjsldds.log => Here all activities of creating the xml file are loggedIn sub-folder: D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\bobj-sld-ds\log \ sldreg_<timestamp>.log => here the sldreg activities are logged.If the log files in the subdirectory are empty the sldreg has failed – very likely due to a missing key file.Details can be found in the Admin guide of BOE4 (Managing system landscape directory registration).http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf

Example:

Log of a successful executed sldreg:

Wed Mar 09 10:59:25 2011 SLD Registration Program [7.20.4] (Feb 14 2011) [Non-Unicode]Wed Mar 09 10:59:25 2011 Using XML 'D:\Program Files (x86)\SAP BusinessObjects\\SAP BusinessObjects Enterprise XI 4.0\java\lib\bobj-sld-ds\bobjslddsoutput.xml_BOE4COE' data input fileWed Mar 09 10:59:25 2011 Parsing XML document.Wed Mar 09 10:59:25 2011 Supplier Name: BusinessObjectsEnterpriseSystemWed Mar 09 10:59:25 2011 Supplier Version: 1.0Wed Mar 09 10:59:25 2011 Supplier Vendor: Wed Mar 09 10:59:25 2011 CIM Model Version: 1.6.10Wed Mar 09 10:59:25 2011 Using destination file 'C:\Program Files\SAP\hostctrl\exe\connect.key'.Wed Mar 09 10:59:25 2011 No key file 'C:\Program Files\SAP\hostctrl\exe\connect.key.key' used.Wed Mar 09 10:59:25 2011 Use encryted destination file 'C:\Program Files\SAP\hostctrl\exe\connect.key' as data sourceWed Mar 09 10:59:25 2011 HTTP trace: falseWed Mar 09 10:59:25 2011 Data trace: falseWed Mar 09 10:59:25 2011 Using destination file 'C:\Program Files\SAP\hostctrl\exe\connect.key'.Wed Mar 09 10:59:25 2011 No key file 'C:\Program Files\SAP\hostctrl\exe\connect.key.key' used.Wed Mar 09 10:59:25 2011 Use encryted destination file 'C:\Program Files\SAP\hostctrl\exe\connect.key' as data sourceWed Mar 09 10:59:25 2011 ******************************Wed Mar 09 10:59:25 2011 *** Start SLD Registration ***Wed Mar 09 10:59:25 2011 ******************************Wed Mar 09 10:59:25 2011 HTTP open timeout = 420 secWed Mar 09 10:59:25 2011 HTTP send timeout = 420 secWed Mar 09 10:59:25 2011 HTTP response timeout = 420 secWed Mar 09 10:59:25 2011 Used URL: http://ldcist7:58900/sld/dsWed Mar 09 10:59:25 2011 HTTP open status: true - NI RC=1Wed Mar 09 10:59:25 2011 HTTP send successful.Wed Mar 09 10:59:26 2011 Return code: 200 --- Return message: (OK)Wed Mar 09 10:59:26 2011 HTTP response: Success. HTTP status code: 200Wed Mar 09 10:59:26 2011 ****************************Wed Mar 09 10:59:26 2011 *** End SLD Registration ***Wed Mar 09 10:59:26 2011 ****************************Wed Mar 09 10:59:26 2011 Data send status: true

Create the “connect.key” file in case it is missing. Execute via cmd console:c:\Program Files\SAP\hostctrl\exe>sldreg -configure connect.key=>Then you are asked for user, pw, host, port of the SLD you want to connect to.

Manual execution of the sld-registration via cmd console “D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\lib\bobj-sld-ds\runbobjsldds.bat –config sldparserconfig.properties!!Attention: Manual Execution may lead to problems at BOE systems with more than one NODE in the cluster – Therefore please check carefully the data that arrived in SLD or restart the BOE cluster so that the data is sent automatically!!

BO Cluster in SLD:SLD -> Administration ->Content Maintenance->Subset: “Classes with Instances” ->Class: “SAP_BOCluster”OrSLD->Home ->CIM Instances ->Subset: “Classes with Instances” ->Class: “SAP_BOCluster”

15. Missing EWA for BOE 3.X systems in SolMan 7.0

Description: You do not see a processed EWA for your BOE system in Solution Manager.

Solution: 1. First check if the BOE system is part of your solution. GoTo “SOLUTION_MANAGER“ -

>“Solution Landscape Maintenance”-> Check the list of logical components and ensure that the system (logical component of the system)is assigned to the solution and check the right role (DEV,QA;PROD) of your system. All roles ( DEV, QAS, PRD, … ) of your BOE systems should be in one logical component.

2. Check if the BOE System (LONGSID) is in the table of systems in ‘EarlyWatch Alert Administration’. GoTo “SOLUTION_MANAGER“->“Operations Setup”-> “Solution Monitoring” -> “EarylWatch Alert” -> “Earylwatch Alert Setup” and there check the table of systems. If the system is not visible a "Complete System Data Replication" of SMSY is necessary. This is described in SAP Note “1000599” section 4.

3. If the system is there, but the session is not processed, please implement SAP Note „1513289“, and trigger “SM:EXEC SERVICES” => afterwards the EWAs will be processed(additionally HW Information of Windows OS that was missing is now part of the EWA report). Goto “SOLUTION_MANAGER“->“Operations”-> “Solution Monitoring” -> “EarylWatch Alert” and check the list of EWAs.

Example:

‘EarlyWatch Alert Administration’:

16. Corrupted Store in Change Reporting or parsing errors for DumpAllinXML(wi_srvadmin.jar script) for BOE 3.1

Description: You see error messages in the log or you find corrupted stores in the change reporting. The problem is that an old version of the “wi_srvadmin.jar” had coding errors and created an XML that could not be encoded and lead to corrupted log stores

Solution: Replace the wi_srvadmin.jar attached to SAP Note 1357901 and follow the instruction of the Note (Chapter 11.2) or upgrade the BOE version to 3.1 Sp4.

Example: Corrupted store display:

17. OS Commands (e.g. DumpKPIs, DumpAllinXML) not working on BOE 3.1

Description: You see error messages like:Exception in thread "main" java.lang.NoClassDefFoundError:com/bo/repo_proxy/RepoAccessExceptionat com.businessobjects.server.shell.Interpreter.<init>(Unknown Source)at com.businessobjects.server.shell.Main.main(Unknown Source)

Normally the script ”wi_srvadmin.jar” is located in folder “%BOE_DIR%\common\4.0\java”. In older SPs of BOE the script “wi_srvadmin.jar” was delivered in folder “/usr/sap/SMD/boe_script” with a wrong version (not working) and therefore it does not find the right libraries.

Solution: For BOE 3.1 Supportpackage < 2Copy the “wi_srvadmin.jar” attached to SAP Note 1357901 into folder “/usr/sap/SMD/boe_script” and replace the commands.xml that uses this path and that uses different pathvariables. This is all described in the SAP Note.

For BOE 3.1 Supportpackage >= 2Copy the “wi_srvadmin.jar” attached to SAP Note 1357901 into folder “%BOE_DIR%\common\4.0\java” and follow the instruction of the Note. This jar includes a new manifest that loads also the libraries in the “lib” subfolder.

Example: OSS message 1030028/2011

18. OS Commands (e.g. DumpKPIs, DumpAllinXML) not working on BOE 4.X running on UNIX different from Linux

Description: To execute the SAP delivered scripts, we are using the JVM that is also used by the BI Platform system. Unfortunately the path to this JVM (java.exe file) is different for every OS:"<BOE_DIR>/sap_bobj/enterprise_xi40/<OS dependent part>/jdk/bin"We have to set a fix path to the JVM of BI Platform inside the script definitions of ‘Commands.xml’. For UNIX we can have only one path and implemented the solution for Linux. If the BI Platform system runs on a different OS than WINDOWS or LINUX, the scripts fails.Additional side effects are:1.)You might find many erros in agent log file of kind: [[OsStore:bo40.dump_all_xml]][[ScriptExtractor] unable to execute os-command [bo40.dump_all_xml]: Error executing OS command [command:./java -jar "%BOE_DIR%/sap_bobj/enterprise_xi40/java/lib/coarsegrain.jar" -console] [sessionId:collect_bo40.dump_all_xml_1354666390650]: Working directory is not consistent: /usr/sap/PQ0/sap_bobj/enterprise_xi40/linux_x64/jdk/ bin; nested exception is: java.io.FileNotFoundException: Working directory is not consistent: /usr/sap/PQ0/sap_bobj/enterprise_xi40/linux_x64/jdk2.)

2.)Some config stores like "bo40.dump_all_xml" are NOT available

Solution: Follow instructions of SAP Note 1809048.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"This has to be performed on every host where your BI Platform 4.X system is installed.

19. JAVA Exception when executing OS Command DumpAllinXML

Description: When you execute the OS Command DumpAllinXML you get error messages like:java.lang.NullPointerException java.lang.NullPointerException at com.businessobjects.sdk.coarsegrain.srvadmin.internal.ServerAdminMgr.dumpAllServersHelper(ServerAdminMgr.java:398) at com.businessobjects.sdk.coarsegrain.srvadmin.internal.ServerAdminMgr.dumpAllServers(ServerAdminMgr.java:524) at com.businessobjects.sdk.coarsegrain.srvadmin.internal.ServerAdminMgr.dumpAllServers(ServerAdminMgr.java:422) at com.businessobjects.sdk.coarsegrain.shell.internal.CommandDefinitions$DumpAllCommand.run(Comman

dDefinitions.java:852) at com.businessobjects.sdk.coarsegrain.shell.internal.CommandDefinitions.runCommand(CommandDefinitions.java:66) at com.businessobjects.sdk.coarsegrain.shell.internal.Interpreter.executeCommand(Interpreter.java:27) at com.businessobjects.sdk.coarsegrain.shell.internal.Interpreter.executeCommand(Interpreter.java:12) at com.businessobjects.sdk.coarsegrain.shell.internal.Console.run(Console.java:53) at com.businessobjects.sdk.coarsegrain.shell.internal.Main.main(Main.java:48)

Solution: There are Central Management Server processes that are in an undefined state. GoTo CMC of the BOE system and check the servers list. If there are any Central Management Servers that are ‘Stopped’ but ‘Enabled’ and have a name like ‘…temp…’ -> delete them.

20. BI Monitoring: Select BO Jobs -> Error in Web Service Execution

Description: When trying to get jobs from BO system in BI Monitoring you receive the following error message:

Executing the script ‘List Jobs’ returns: “Command line parameters are not valid”

Check entry in commands.xml for script ‘ListJobs’:

Wrong entry in commands.xml:<Cmd key="bo40.list_jobs" name="ListJobs" desc="Display all BO jobs"><OsCmd ostype="WINDOWS" stdin="%BOE_CMS% %BOE_CMS_USR% %BOE_CMS_PWD% %BOE_AUTH_TYPE% %BOE_CORBA_SSL_ENABLED% %BOE_CORBA_SSL_CERT_DIR% %BOE_CORBA_SSL_TRUSTED_CERT% %BOE_CORBA_SSL_CERT% %BOE_CORBA_SSL_KEY% %BOE_CORBA_SSL_PASSPHRASE% %BOE_CORBA_SSL_FIPS_ENABLED%" exec=".\java -jar &quot;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\bobjnormal.jar&quot; -console" path="%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk\bin" param="true" runtime="600"/><OsCmd ostype="UNIX" stdin="%BOE_CMS% %BOE_CMS_USR% %BOE_CMS_PWD% %BOE_AUTH_TYPE% %BOE_CORBA_SSL_ENABLED% %BOE_CORBA_SSL_CERT_DIR% %BOE_CORBA_SSL_TRUSTED_CERT% %BOE_CORBA_SSL_CERT% %BOE_CORBA_SSL_KEY% %BOE_CORBA_SSL_PASSPHRASE% %BOE_CORBA_SSL_FIPS_ENABLED%" exec="./java -jar &quot;%BOE_DIR%/sap_bobj/enterprise_xi40/java/lib/bobjnormal.jar&quot; -console" path="%BOE_DIR%/sap_bobj/enterprise_xi40/linux_x64/jdk/bin" param="true" runtime="600"/></Cmd>

Correct entry (correct exec directory and ‘&quot’ everywhere):<OsCmd ostype="WINDOWS" stdin="&quot;%BOE_CMS%&quot; &quot;%BOE_CMS_USR%&quot; &quot;%BOE_CMS_PWD%&quot; &quot;%BOE_AUTH_TYPE%&quot; &quot;%BOE_CORBA_SSL_ENABLED%&quot; &quot;%BOE_CORBA_SSL_CERT_DIR%&quot; &quot;%BOE_CORBA_SSL_TRUSTED_CERT%&quot; &quot;%BOE_CORBA_SSL_CERT%&quot; &quot;%BOE_CORBA_SSL_KEY%&quot; &quot;%BOE_CORBA_SSL_PASSPHRASE%&quot; &quot;%BOE_CORBA_SSL_FIPS_ENABLED%&quot;" exec="..\..\win64_x64\jdk\bin\java -cp &quot;%SMD_AGENT_HOME%\applications.config\com.sap.smd.agent.application.e2emai.bobj\bobjnormal.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\cesession.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\cecore.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\celib.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\logging.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\aspectjrt.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\ceaspect.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\TraceLog.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\ebus405.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\corbaidl.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\cryptojFIPS.jar;%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\bcm.jar&quot; com.sap.bimon.bobj.JobRetriever -console" path="%BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib" param="true" runtime="900"/>

Additionally File “bobjnormal.jar” was missing in the agent config folder:\usr\sap\<DAA>\<SMDA98>\SMDAgent\applications.config\com.sap.smd.agent.application.e2emai.bobj

21. Missing data / grey alerts in System Monitoring of BOE

Metrics are pushed from Wily EM to SolMan. StepbyStep Check:

GoTo “Technical Monitoring” workcenter -> ‘System Monitoring’o Select your BOBJ system and open the system monitoring screen.o Open the different instances/servers in the detail area and check for grey metrics.o Drill down to the lowest level to see where the grey alert comes from.

GoTo “Technical Monitoring” workcenter and call the link ‘Alerting Directory Browser’o Open ‘Technical System monitoring’ -> Open the BOBJ systemo Click on the right server and scroll to the top of the screeno Mark the line with the ,metric you are interested ino Select the ‘Data collection’ tab and check if the values for the parameters make

sense “Collection Hosts” should be filled with the host name “Introscope path” should contain the path to the metric in Wily EM

o Select the ‘Threshold’ tab to check the thresholds for this metrico Select the ‘Others’ tab to get the ‘Metric ID’ and the ‘Managed Object ID’

GoTo “Solution Manager Administration” workcenter -> ‘Framework’ -> ‘Agent framework’ -> ‘Agent Admin’ -> ‘All Agents’

o Choose tab ‘Application Configuration’ -> ‘com.sap.smd.agent.application.e2emai’ -> ‘Application Resources’ -> ‘MAI/ISMetricCollectionDefinition.xml’

o Select the right agent (if necessary) and download the fileo Search for the entry with the same ‘Metric ID’ and ‘Managed Object ID’ (Collector

Context). Check if the values are the same as you can see in ‘Alert Directory Browser’ Use transaction ‘SE38’ and run report ‘AC_ALRT_ANALYSIS_TOOLS’ -> ‘Show metric

Details’. Enter the ‘Managed Object ID’ (Context ID) and select ‘Context Description’ and ‘Display metrictypes’ to get the definition of the metric displayed.

Use transaction ‘SE16’ and enter table ‘ACE_DB_EVENT’. Search for entries with the same ‘Metric ID’ (Metric Type ID) and ‘Managed Object ID’ (Context ID). Check the values that are delivered from Wily EM to Solution Manager.

If there is no data inside the ABAP table, check if data is available in WILY EM. Open “Workcenter” or “Webview” to display data of WILY EM. Open the path mentioned in “Introscope path” of this metric and check if the path is correct.

If data is available in WILY but not in ABAP, increase the trace level of WILY EM to ‘DEBUG’ as described in SAP Note 1751225 and check the log file entries.

21.1. FileRepositoryServer [Performance]: Fileserver Avg Read/Write Response Time

Description: When checking system monitoring you see some grey alerts for Input/OutputFileRepositoryServer.

First of all you have to check if the data is available in WILY.In Technical Monitoring workcenter open the System monitoring application for your BOE system and check for grey alerts.

Use the link to open Alerting directory browser.

Choose ‘Technical System Monitoring’ and open the right BOE technical system. There open the instance where you see grey alerts, and choose the metric that is grey. Switch to ‘Data collection’ tab and check the ‘Introscope path’ of this metric.

Open this path in Wily Investigator and check if the data is available there:

The reason for a grey metric here is that there is a node ‘Frontends’ added between the ‘fileserver…InputFileRepository’ node and the ‘BIP’ node. Therefore the data cannot be found.This issue is solved with new Content version (e.g. version 10 for SolMan SP7), and uploaded to SMP at 17.1.2013. You can update the content in Solman Setup –> Technical monitoring –> System Monitoring -> Update Content.

Afterwards you can check the new content in the template maintenance of System monitoring. You have to switch to expert mode to see the ‘Data Collection’ tab. There you should see a ‘(Frontends)’ before the ‘BIP’ in the PATH_NAME for “T BOE File Repository Service”.

After the content update the new templates have to be assigned and activated again in the ‘Setup Monitoring’ step.

21.2. CMS [Performance]: CMS Logon Response time

Description: When checking system monitoring you see some grey alerts for the CMS server.

CMS Logon Response time is missing:

The Logon metrics are located below the ‘Frontend’ node which is not expected in the metric definition of MAI.

Solution:

Exchange the “CMS.lst” file attached to NOTE 1653689 as described in the note.

[Frontends]BIP::CMS:QueryBIP::CMS:QueryBatch[]BIP::CMS:Query_WhereClauseBIP::CMS:Query_OrderByClauseBIP::CMS:Query_SelectClauseBIP::CMS:LogonBIP::CMS:LogonWithToken

21.3. CMS [Exceptions]: Number of failed BO Job Executions

Description: When checking system monitoring you see some grey alerts for the CMS server.

CMS-> Exception – Number of failed BO Job execution:

Metric missing in Wily “Failed Jobs (Delta)”

The ‘Delta’ metrics are calculated by a script in WILY EM. Check if the script is available:Script: “BOE_CreateDeltaMetrics.js” located in the WILY EM folder -> Scripts

If the script is there, set the value “var debug=1;” at the beginning of the script and check the debug information in the newest “IntroscopeEnterpriseManager.log” in the log directory of Wily EM.

The script only enters a new value in Wily EM if the ‘difference is > 0’. This means if there is no change in the number of ‘FailedJobs’, we will not create values for ‘FailedJobs (Delta)’. If this happens over a longer time we would even not see this matric at all in Wily EM. Finally: if we do not have Delta values, we will see grey metrics in system monitoring for this metric.

Solution:This situation above is not a bug – it works as designed and it should not happen in a productive system. If you need to have a green traffic light in system monitoring, even when no deltas are created, you would have to change manually the script:Remove the ‘if (difference > 0)’ before the ‘javascriptResultSetHelper.addMetric…’ command line.This would be a customer modification which is not tested and supported by SAP.

21.4. <All servers> [Availability]: Instance Availability

Description:

BOE server availability –> the metrics for the server names that have space in them comes in as grey, whereas the same for server names that do not have a space in them comes in fine. For example, “BOPSAPBOPA2.APS_Monitoring” -> works whereas“BOPSAPBOPA2.APS Monitoring” -> does not work.

In landscape browser we have instance names with blanks, e.g. BOPSAPBOPA1.APS Connectivity:

In WILY the instance names are displayed without blanks, e.g. BOPSAPBOPA1.APSConnectivity:

Solution:

In wily Introscope the nodes of those instances are displayed without the blanks, but in LMDB the instance names are displayed with blanks. This leads to the fact that we will not find the instances in Wily and cannot extract the data – so we have grey metrics. Therefore please do not use instance names with blanks - rename them with an underscore.