Tag: BOBJ

Custom Fonts in Design Studio

There are a lot of fonts which are supported by Design studio by default, but there are infinite varieties of fonts available in the internet and not all of them are supported by Design Studio directly. If you need to use one of the fonts in your design studio application, there is an easy way of doing so without having to install the font library on the end user’s computer. There are a lot of fonts which convert alphabets into images which can be used on the dashboards as images. Here is how to do so.

  1. Usually the default font types are supported on all browsers and don’t need any installations on the end user’s machines or any CSS scripting to add the font families. But for font types like “SAP-Icons” (this is a font type which converts unique texts to images you can use on the dashboards. Ex : https://openui5.hana.ondemand.com/iconExplorer.html)
  2. There are a lot of websites where you can look up for fonts you need but most of them are not free. I found one website which offers font types for free for commercial use as well.

    http://www.fontsquirrel.com/fonts/list/find_fonts

  3. Go into the website and download the .ttf file for required fonts. In the below example I am trying to add a new font called “Roman Caps”.

  4. To start adding a new font family to your design studio dashboard, you will need a .ttf file and .eot/.woff file as well.

    Note: .eot is a file type which is supported only in IE. If your target browser is anything other than IE, you might have to get the .woff file as well.

  5. Creating an .eot or .woff file can be done using a lot of websites for free available on google.
  6. Once you have the .eot and .ttf files ready, you have to upload these files to the repository folder and create a CSS file where you can import these 2 files.

  7. Now, to import the above 2 files into a CSS file and add the new font-family to your design studio dashboard put in the below code in your CSS file.

  8. With the above step, when you reference the .css file in your dashboard as custom CSS file, the new font face will be available for use in your dashboard.
  9. I used a text component to test if the new font type is working, and to do so, I created a CSS class in the .css file to use the new font family that I just imported.

  10. After I save the css file also and reference it in the dashboard and apply the CSS class to the text object here is the result I get.

  1. As a next step, I am exploring if I can use the same kind of CSS scripting to change the font types on charts and other components as well and I will update the post as soon as I find something.

Happy designing

Naveen Mamidi

Tek Analytics BI Practice

Fiori look Web I Interface – BOBJ 4.2 SP4

With BI 4.2 SP4, the new Fiori look BI Launchpad is introduced. The new portal is addition and is not replacing the classic BI launchpad.

This Blog is intended to walk through the options available while viewing a Webi report in New BI Launchpad. Once the user Logs into New BI Launchpad, all the documents will be shows as tiles.


Comparison (Look) with Old BI Launchpad


Below are the quick options available in the new interface for the end user.


By default, the report opens in normal interface and user can switch to advanced interface by choice. Below Screenshot shows the quick options available.

By Switching to Advanced interface, all the interactive options will be active. Users can quickly Rank/sort the data in the report


Changing Prompt values



Unlike classic BI launchpad , there is no in-built design applet for new version. There is an option to “Open in designer” which will takes you to Old version through Opendoc link



Thanks

Karthik Addula

Principle Architect

Fiorified BI Launchpad

Quick picks

Url to accesshttp://server:port/BOE/BILaunchpad

Security Changes – Yes, new right needs to be granted

Old Version – No confusions please, Classic BI launchpad still available and can be used for many advanced functions. In my opinion , new launchpad is strictly a consumer interface.

First Look


Changing preferences

Go to User profile > Click on settings



The setting are very similar to classic BI Launchpad.

    Users can set preferred Landing tab

    Pixels for web-based look

    Hide/show totals for Analysis OLAP

By default the landing page navigates to Home Tab (with Show all selected). Users can change the documents to view as below


Context Menu

Context menu of Tile/document can be launched by clicking the 3 dots at bottom on each tile, which lists all the properties of the document

Context menu is similar to right-click on report in classic BI. Below options available under the context menu


Working with Categories

Document tiles in new BI Launchpad can be grouped by categories.( Standard BOBJ categories). Security can be configured at CMC level. Documents can be tagged to categoris from context menu.


Once the document is assigned to a category . changing the landing page view to categories will display all categories .


Viewing standard BI folders

Once you login to BILaunchpad, select Folders Tab which displays all the folders for which the account has access to.


 

Bharat Sunkari

Managing Partner – Tek Analytics

 

 

Certificate not trusted warning – How to Import wildcard certificate into Tomcat (BOBJ web application server)

The document discusses on how to enable https on BOBJ web application server and import the wild card CA trusted certificate.

Enabling the https

Enabling https on the web application (Tomcat in this case) requires generation of key store and self-signed certificates using in-built keytool or openssl

Using command line navigate to <installdir>\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin

Run the below command, this will generate a keystore.jks file at keytool home directory, copy it to another folder say (C:/SSL)

keytool -genkey -alias tomcat -keyalg RSA –keystore keystore.jks

Export the .crt self-signed certificate using the below command

keytool –export -alias tomcat -keystore c:\SSL\Keystore.jks -file c:\ssl\tomcat.crt

A self-signed certificate tomcat.crt will be stored under C:\SSL folder.

Stop the tomcat

Open server.xml file. Location – <Tomcathome>/conf

Uncomment the https entry and add the below parameter.

keystoreFile= “location of keystore.jks file” keystorePass=”password”

Restart the tomcat, now https links to BI-Launchpad and CMC should work

https://server:httpsport/BOE/BI

https://server.httpsport/BOE/CMC

Importing the wild card certificate

By following the above process, https links will work as expected. However, a certificate not-trusted warning will appear on the browser which is expected. The reason for this is Tomcat certificate is self-signed but not CA signed

To overcome this error, you can create .CSR file and send it to CA providers , who in return provide certified CRT files. Use the below commands to import the same

Keytool –import –trustcacert –alias tomcat –keystore keystore.jks –file cacertified.crt

If you have root certificate, please import the same into root alias.

Most of time, internal CA have wildcard certificates for the domain already, importing those will be little bit tricky. Importing the wildcard certificate into same alias will give “Public keys mismatch error”. Please follow the below process to import.

Using Openssl tool convert the required wildcard.crt certificate into pfx format

openssl pkcs12 -export -in wildcard.crt -inkey wildcard.key -out C:\SSL\wildcard.pfx

the above command will generate a wildcard.pfx under C:\SSL folder.

Stop the tomcat and make the below changes to https entries

keystoreType =”PKCS12” keystoreFile=”wildcard.pfx” keystorePass=”password”

Restart the tomcat.

All set, now the tomcat will be using the internal wildcard certificate.

 Karthik Addula

Converting netweaver Analysis workbook to use BOBJ platform

Requirement – Converting Analysis for office workbook based of netweaver platform to use BOBJ platform.

By default, converting Bex workbook into analysis office uses netweaver connection, which means the workbook needs to be saved to ABAP server, limited broadcasting functionality and also it will be specific to one BW server ( For instance, if you want to have workbook with combined data from BW and hana in multiple tabs it is not possible)

This post explains the step by step procedure on how to change the bex workbook to use BOBJ BICS connection

First, converting the Bex workbook

Launch Analysis office. (TCODE RSAAOE) , Click File>Analysis>Convert Bex workbook

 

Select the workbook to be converted.

Step 2- AAO conversion

 

Click Ok, it automatically converts the workbook into AAO workbook

Step 3- AAO conversion

 

Save the work book ( save to BOBJ platform)

Step 4- AAO conversion

 

Second,  Accessing the workbook

Open the workbook from BOBJ Platform

try to refresh the work book

The workbook will prompt for BW credentials, even though single sign on is activated in BOBJ.  ( please sign in manually)

 

Third, Converting the workbook

Open the work book

Refresh by manually entering the BW password

Click on components in design panel and click edit data source name

Untitled

 

The olap connection box will pop-up ( as you already authenticated to BOBJ platform in Part 2 , step 1)

Select the Desired OLAP BICS connection

Select the the same bex query the workbook is using.

Now the workbook is successfully changed, you can now refresh the workbook via BOCS connection and also schedule the workbook through BOBJ Scheduler ( 4.1 sp4 and higher, need AAO add-on to be installed on server)

– Karthik Addula