Fiorified BI Launchpad and Web Assistant in BOE 4....
Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Configure Web Assistant for Fiorified BI Launchpad (BOE 4.2 SP05),
Enable and use web Assistant in Fiorified BI Launchpad
Web Assistant feature available in Fiorified BI Launchpad from SAP BOE 4.2 SP05 and Onwards.
About Web Assistant:
The SAP Enable Now Web Assistant is a web-based help system to provide context-sensitive user assistance. It enables users to get started quickly and to find all relevant information in an easy way without having the need to leave the respective application. When clicking the help icon, the Web Assistant provides additional information directly on top of the current application screen.
The characteristics of the Web Assistant are:
Seamless: Can be used, exactly when the user needs it from within the application
Context-sensitive: Shows exactly what is needed for the user, depending on the current screen.
Guiding: Provides an interactive step-by-step process guidance
Configurations to enable Web Assistant in the Fiorified BI Launchpad:
After you install or upgrade to SAPBOE 4.2 SP5, you need to configure proxy settings for a user to be able to access Web Assistant in-app help in fiorified BI launch pad.
Enabling and using Web Assistant in Fiorified BI Launchpad:
If application is updated and user is logging into the application for the first time after update - User can see the new features by clicking on the popup appeared on the screen.
To enable Web Assistant in Fiorified BI Launchpad, simply click on the Help icon in the upper right hand portion of the screen:
An informational bar (carousel) will appear across the bottom of the screen, and elements that have in-app help will have a green circle (hotspot) on top of them:
To get help on the topic, simply click on the green circle (hotspot):
If user clicks on the elements present in the carousel area, It will connect to the corresponding hotspot.
To turn off the Web Assistant, simply click on the Help icon again, and the circles will disappear. You can hide the carousel at any time by clicking on the double downward facing arrows on the right hand side of the overlay.
Whether you hide or show the carousel is up to you. We anticipate that in the beginning, people will keep the carousel visible. This gives visibility to the user not just insight into the current control, but at least introductory information on adjacent controls which might also have in-app help. More advanced users, they may decide to hide the carousel altogether and focus on clicking on a circle as they need help.
Not all elements are documented with Web Assistant yet, the number of topics will expand over time until, just about everything important is covered this way.
Hi Bharath, is there something more which needs to be configured ? As I cannot make it to work ;
I have installed BI 4.2 SP5 on a (single-node) test-server
Fiori-launchpad is fully working
The test-server has access through the internet (I have configured our proxi-server and proxi-port-number in the configuration of Internet Explorer), and afterwards I could use this IE to browse the internet from that test-server
IP and Port number showed in videos is "Proxy host and Port number". Please check in your browser proxy settings where tomcat is deployed. Use command prompt to "ping" to proxy and update the same IP or host name in Tomcat java properties.
I have a split deployment with Apache httpd 2.4.39, Tomcat 9.05, and JRE 8.162. I can access to BO 4.2 SP05, but the web assistant kept giving me the same error:"The Web Assistant is not available. BILaunchpad may not have access to the internet or the proxy is not configured.”
I have tested the fix with the regular Apache Tomcat bundled with BO 4.2SP05 and it is successful. So, my guess is that there is something missing in the Apache config files.
Have you tested the fix on a split deployment scenario? Any help is appreciated. I have also opened a ticket with SAP support but no resolution so far.
I have done all the staps (web.xml configuration and tomcat - configuration), but I still get the error mesage :”The Web Assistant is not available. BILaunchpad may not have access to the internet or the proxy is not configured.”
I am not sure if you have experienced or heard this before, but I logged on to the Fiorified Launchpad and it enabled the Web Assistant automatically. This behavior has not happened until today.
Have you heard anything similar? It is odd, it logs you on, then web assistant just shows up.
Is there a setting to deactivate web assistant as default when logging on Fiorified BI Lauchpad? Default mode should be inactive. Currently, all users are seeing web assistant active when logging on.
this happens only if we call it over the launchpad.
it seems that the application can’t authenticate, if the proxy is requesting authentication.
one addition:
if we call both URLs over the Chrome in the server where tomacat is installed we also get 407 Error code but then Chrome reacts and send the Credentials and then it works.
when calling the Launchpad it calls the URL and get Error Code 407 and then nothing happens
it seems the application can't authenticate the User with only these 2 parameters
edit the file and search for _XRayAdapter.toggle(); and comment it ----> /*_XRayAdapter.toggle();*/
and then save and copy the file to the same directory tree under "....\work\Catalina\localhost\" ( ...\webapps\...... ----> ...\work\Catalina\localhost\....)
I am experiencing the same issue now in BI4.3 SP01 Patch400. I added the entries to Apache24 BOE file, with don't use a proxy to connect to the Internet, so I am able to get results from the two URLS mentioned above, but the Web Assistant does not work. I also made sure that the URLS are correct in web.xml. I ran out of ideas.
4.3 should work out of the box.
I have a ticket open with SAP support, but they just said that they don't support split deployment or any apache/tomcat configurations. --> No comments about it.
Any news when it comes to 4.3
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.