Skip to Content

This was an SAP webcast last week.

Full disclaimer – I am not using this functionality

/wp-content/uploads/2014/09/1fig_540419.png

Figure 1: Source: SAP

Figure 1 shows the type of connectivity between BW and Web Intelligence.

/wp-content/uploads/2014/09/2fig_540420.png

Figure 2: Source: SAP

Size the system correctly; this cannot be emphasized enough the SAP speaker said.

SAP speaker said to size yourself or hire SAP Consulting services

Go to https://service.sap.com/sizing then go to Sizing > Sizing Guidelines > Analytics

It is updated; latest update was in February of this year and is relevant to SAP BusinessObjects Web Intelligence

/wp-content/uploads/2014/09/3fig_540421.png

Figure 3: Source: SAP

The number processing servers and  how many concurrent connections are important considerations per Figure 3

Single processing server per machine; ensure disk cache is available – no limit in memory

/wp-content/uploads/2014/09/4fig_540422.png

Figure 4: Source: SAP

Out of box, you need to better size APS, the SAP speaker said

/wp-content/uploads/2014/09/5fig_540423.png

Figure 5: Source: SAP

Request time out – mimics the amount of time it waits to hear back from a service/server when it gets the data back

Regarding the safety belt see SAP BusinessObjects Increasing Stability by Setting Limits on Max. Retrievable Cells From SAP BW into Web Intelligence Using BICS

/wp-content/uploads/2014/09/6fig_540424.png

Figure 6: Source: SAP

Upgrade, the speaker said to see more performance improvements

/wp-content/uploads/2014/09/7fig_540428.png

Figure 7: Source: SAP

SAP speaker said “Don’t use ConnectionServer32” listed in Figure 7

/wp-content/uploads/2014/09/9fig_540429.png

Figure 8: Source: SAP

Implementation of lean was not fully achieved until BI4.1 SP02 patch 1

/wp-content/uploads/2014/09/10fig_540430.png

Figure 9: Source: SAP

For me, bullet number 3 was new (“determine the actual error being thrown by WebI rather than the error reported to the end user”)

/wp-content/uploads/2014/09/11fig_540437.png

Figure 10: Source: SAP

Run query using RSRT back in BW


Run query through Analysis OLAP/BEx Analyzer – issue is with BW/BICS and not WebI

/wp-content/uploads/2014/09/12fig_540438.png

Figure 11: Source: SAP

Not all features of a BEx Query are supported by Web Intelligence

Look up SAP Note 1869560 – see http://service.sap.com/sap/support/notes/1869560

/wp-content/uploads/2014/09/13fig_540439.png

Figure 12: Source: SAP

Error is thrown when WebI processing server encounters an error when communicating another service, as shown in Figure 12

/wp-content/uploads/2014/09/14fig_540440.png

Figure 13: Source: SAP

See note below:

http://service.sap.com/sap/support/notes/1861180

Reproduce error while have End to End trace

/wp-content/uploads/2014/09/15fig_540441.png

Figure 14: Source: SAP

Do a more refined search; capture root cause error and search for that

Speed up processing of incident – include trace files

Provide raw file to SAP Support – “Do not filter it”, the SAP speaker said

/wp-content/uploads/2014/09/19fig_540442.png

Figure 15: Source: SAP

Figure 15 is a summary.

Full disclosure – I am not using BW with Web Intelligence but these are things you can do with most of the tools when working against BW.

Consider attending SAP TechEd && d-code .  Join ASUG for the ASUG SAP TechEd Pre-conference HANDS-ON: SAP BusinessObjects BI 4.1, SAP BW and SAP BW on SAP HANA – All in One Day, October 20th.  This includes exercises for BW and Web Intelligence. Register today

Also see:

Stay Ahead : Attend TechEd && d-code – Win Big SAP BI BusinessObjects HANA Hands-on Sessions

The roadmap Integration of SAP BusinessObjects BI Suite with SAP BW and SAP ERP was just updated as well (SMP logon required)

To report this post you need to login first.

2 Comments

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

Leave a Reply