A recap …

Since the NetWeaver Release 7.0 the SAP JAVA or J2EE stack is a component within the SAP BW Reporting Architecture, and was building the foundation for the BW Integrated Planning (BW-IP) as well. I also quite some time, creating documents and giving the main input for the BI-JAVA CTC template which is described for 7.0x here РSAP NetWeaver 7.0 РSetting up BEx Web РShort and for 7.3x/7.40 here РNew Installation of  SAP BI JAVA 7.30 РOptions, Connectivity and Security
Then, not really recognized by the Audience (not even me … ūüėČ a unspectacular SAP Note was released –¬†Note 1562004 – Option: Issuing assertion tickets without logon tickets

which introduced and extension to the parameter login/create_sso2_ticket РSee also the SAP Help Background for that Topic.

btw: the activation for SSL together with the SAPHostAgent can be found in this SFG Document – SAP First Guidance – SAP-NLS Solution with SAP IQ

After understanding the impact, I have updated the Document – SAP NetWeaver BW Installation/Configuration (also on HANA) and didn’t give them much attention. The mayor difference in my active Implementation for SAP BW 7.3x and 7.40 and SAP Solution Manager 7.1 was: No SSO error at all, no connection problems between ABAP and JAVA stack anymore.

Unfortunately countless SAP Notes, SAP online help and SAP tools still referring to the old value – login/create_sso2_ticket = 2 but since 7.40 the “correct” value is now a system default: login/create_sso2_ticket = 3
btw: did you know, that the parameter is dynamically changeable in tx. RZ11? This allows you to switch the parameter during the usage of the BI-JAVA CTC template and continue the configuration successfully.

create_sso2_ticket.JPG

CTC_error.JPG

Finding out the BI-JAVA system status

the easiest way is to call the SAP NetWeaver Administrator http://server.domain.ext:<5<nr>00>/nwa and proceed to the “System Information” page

NWA_status.JPG

NWA_details.JPG

Details of the Line “Version”:

1000 7.40 10 2 2015 …
Main Version SPS PL Date

Note 1961111- BW ABAP/JAVA SPS dependencies for different NetWeaver release and BI JAVA patch updating relevant

Note 1512355 – SAP NW 7.30/7.31/7.40 : Schedule for BI Java Patch Delivery

Corrections are available via the usage of the standalone LVM tool at this time.

Note 2212081 – Fixes for post copy java automation

Use the standalone LVM tool as described here – SAP First Guidance – BW Housekeeping and BW-PCA

Running the BI-JAVA CTC template

Call the wizard directly with the following URL – http://server.domain.ext:<5<nr>00>/nwa/cfg-wizard

FUN.JPG

FUN_details.JPG

Checking the result

Now, that this hurdle is taken we have to check the BI-JAVA configuration with the BI diagnostic tool or directly in the System Landscape of the EP.

EP_SLD.JPG

And the Result in the BI Diagnostic tool (version 0.428)
Note 937697 РUsage of SAP NetWeaver BI Diagnostics & Support Desk Tool
Note 1903392 – Error: First RFC call failed, config not loaded

To get to this final state, you have to additionally check/correct the following settings in the NetWeaver Administrator for evaluate_assertion_ticket and ticket according SAP Note 945055. (The Note is not updated since 2007)

NWA_ticket.JPG

[trustedsys1=HBW, 000]
[trusteddn1=CN=HBW, OU=SSL Server, O=SAP-AG, C=DE]
[trustediss1=EMAIL=xxx, CN=SAPNetCA, OU=SAPNet, O=SAP-AG, C=DE
[trustedsys2=HBW, 001]
[trusteddn2=CN=HBW, OU=SSL Server, O=SAP-AG, C=DE]
[trustediss2=EMAIL=  , CN=SAPNetCA, OU=SAPNet, O=SAP-AG, C=DE]

Updating the Expired Certificates in BI-JAVA

When you encounter broken SSL trust because of expired trusted CA certificates in the SAP AS Java ‘TrustedCAs’ view of the keystore service, you have to update then accordingly. See the following SAP Notes for Details.
Note 1487183 – Update of issuer certificates in the TrustedCAs keystore
Note 1507996 – Update of Expired Trusted CA Certificates

Certificates_Keys.JPG

SSL.JPG

As we are now using assertion tickets instead of logon tickets, the RFC connection from ABAP to JAVA looks a bit different:

SM59_A_J.JPG

crosscheck as well with the entry for the default Portal in the ABAP Backend (tx. SM30 => RSPOR_T_PORTAL)
Note 2164596 – BEx Web 7.x: Field “Default Font” missing in RSPOR_T_PORTAL table maintenance dialog

RSPOR_T_PORTAL.JPG

Note 1981917 – BEx Web 7.3x: Support for multiple BI/BW master systems (ABAP)

Checking additional settings in the BI-JAVA configuration via the findings from this SAP Note (even it is SolMan related at this time). The following Note deals about the missing P4/P4S entries in the configuration
Note 2013578 – SMDAgent cannot connect to the SolMan using certificate based method – SolMan 7.10 SP11/SP12/SP13
Note 2012760 – Ports in Solution Manager for Diagnostics Agent registration
Note 1898685 – Connect the Diagnostics Agent to Solution Manager using SSL


Activating the BEx Web templates

Checking additional settings in the BI-JAVA configuration via the findings from this SAP Note (even it is SolMan related at this time). The following Note deals about the missing P4/P4S entries in the configuration

Note 2013578 – SMDAgent cannot connect to the SolMan using certificate based method – SolMan 7.10 SP11/SP12/SP13
Note 2012760 – Ports in Solution Manager for Diagnostics Agent registration
Note 1898685 – Connect the Diagnostics Agent to Solution Manager using SSL

 

BW-BC.JPG

Now you can call with tx. SE38 the Report RS_TEMPLATE_MAINTAIN_70 and choose as Template ID 0ANALYSIS_PATTERN

0ANALYSIS_PATTERN.JPG

Running BEx Web from RSRT

Ok. This only approves that the BEx Web Template can be called directly. But what happens when you call the web template or any query from tx. RSRT/RSRT2? you will encounter (as well I did) that this is a complete different story. Tx. RSRT has three different options to show the result of a query in a web based format, and we are interested in the¬†“Java Web”¬†based output

RSRT.JPG

The recently added “WD Grid” output is nice to use together with the new BW-MT and BW-aDSO capabilities with SAP BW 7.40 on HANA.

But what we see is this:

RSRT_error.JPG

Hmm? We checked the BI-JAVA connection and the standard BEx Web Template and still there is an error? Is there a problem with RSRT? Is the parameter wrong?

No. Recently (again not really recognized by the Audience again) another SAP Note was released which also has an impact to SAP EP 7.3x/7.40:
Note 2021994 РMalfunctioning of Portal due to omission of post parameters
In this context the following SAP Note is also important to consider:
Note 2151385 – connection with proxy
Note 2194634 – No theme displayed for Web Dynpro ABAP (in case of a fallback)
After applying the necessary Corrections to the SAP BI-JAVA EP Instance, also the tx. RSRT finally shows the correct output:

RSRT_output.JPG

If you encounter the following error:

“DATAPROVIDER” of type “QUERY_VIEW_DATA_PROVIDER” could not be generated

Cannot load query “MEDAL_FLAG_QUERY” (data provider “DP_1”: {2})

EP_error.JPG

This is solved by the SAP Note (to apply in the ABAP Backend) –

Note 2153270 – Setup Selection Object with different handl id

If the following error (“classic RSBOLAP018“) occurs, this can have different reasons, e.g. outdated BI-JAVA SCA’s, user or connectivity problem.

“RSBOLAP018 java system error An unknown error occurred during the portal communication”

Some of them can directly be solved with the following SAP Notes below. Best easiest way is to re-run the BI-JAVA wizard again with enough Authorization rights in the ABAP Backend (e.g. maintain table RSPOR_T_PORTAL).

RSBOLAP018_2.JPG

 

Note 1573365 – Sporadic communication error in BEx Web 7.X
Note 1899396 – Patch Level 0 for BI Java Installation – Detailed Information
Note 2002823 – User-Specific Broadcaster setting cancels with SSO error.
Note 2065418 – Errors in SupportDeskTool

More Solutions can be found here – Changes after Upgrade to SAP NetWeaver BW 7.3x


Finally …

On this Journey finding the real connection, I found also some helpful KBA which I added to the existing SCN Document –¬†Changes after Upgrade to SAP NetWeaver BW 7.3x¬†in the¬†7.3x JAVA¬†section. The good news here is: at the end the documents are very nice for background knowledge and where not needed almost at all, if you stick to the automated configuration.

So, of course the BI-JAVA – EP configuration is a hell of a beast, but you can tame it … ūüėČ

I hope this brings a bit of a light into the successful BI-JAVA configuration


Roland Kramer, PM EDW (BW/HANA/IQ), SAP SE
@RolandKramer
 

 

“the happy one’s are always curious”

 

To report this post you need to login first.

16 Comments

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

  1. Andy Silvey

    Hi Roland,

    really useful information, I first setup a Bi-Java in spring 2007, and in those days the only doco was the magic OSS Note 917950 and the three guides which were attached to it.

    How do you find time to do this with everything else you are working on ūüôā

    Thanks for useful hints, best regards,

    Andy.

    (0) 
    1. Roland Kramer Post author

      Hi,

      At this time already this Documentation was available – http://scn.sap.com/docs/DOC-32541#section8 and unfortunally the Note you mentioned started a big mess with the BI-JAVA configuration and is still mentioned in various Notes,etc.

      Well, as I have some “real BW systems” as reference I keep myself busy, as this what I think is part of my Job in PM in the BW ALM Area.

      Best Regards Roland

      (0) 
  2. Fabricio Pereira

    Hi Roland,

    That was a really interesting and well detailed blog about the BI Java components in the new NetWeaver 7.4.

    My question is more about changes in performance and what are the recommendations now for the usage of the Portal where the BI Java components are installed.

    In the past, SAP recommended us to have a separate installation for the BI Java components, mostly because of performance constrains… is that still the recommendation? Can we now install it in the same Portal we have ESS/MSS and SRM, for example?

    Thanks for this nice blog!,

    Fabricio

    (0) 
    1. Roland Kramer Post author

      Hi,

      Thanks for the Feedback.

      Since NetWeaver 7.30 the 1:1 Releation between SAP BW and BI-JAVA is gone. So you can have on EP/BI-JAVA Instance for different BW or additional components. e.g. ESS/MSS and SRM …

      Best Regards Roland

      (0) 
      1. Fabricio Pereira

        Hello Roland,

        Thanks for the fast response.

        Would you have any link to the documentation from SAP that supports it? I’m working in a project to upgrade our BW environment from 7.01 to 7.4 and it would be a plus to be able to consolidate the ESS/MSS Portal with the BI Java one. My main concern is the impact in the performance of the Netweaver Portal.

        Thanks,

        Fabricio

        (0) 
  3. Abhi S

    Hello Roland,

    Very well written and really useful blog. We have upgraded our Portal system from 7.0 to 7.4 and also BW system to 7.3.

    We have few BeX iViews and reports are displayed on portal as you mentioned in the blog. However, we are facing a weird problem. When ever we try to click on the standard buttons like, info, Export to Excel, save as, we see nothing happens. We get the infinite loop icon, but actually nothing happens

    Also, when we try to right click and see the context menu related to report, that is also not coming in Portal. However the same appears in BeX Analyzer tool.

    Any pointer would be highly appreciated. Thanks!

    Regards

    Abhi

    (0) 
      1. Abhi S

        Thanks for the pointers. I will ask BASIS to check if the latest patches are applied. Please expect more to come ūüôā

        Regards

        Abhi

        (0) 
          1. Abhi S

            Actually the issue is resolved. Anyone else who has this problem, there is a version mismatch for BI-JAVA. The BASIS fixed the issue by applying latest patch. Thanks for your pointers.

            ~Abhi

            (0) 
  4. Tony Price

    Roland –

    Great post, thanks for that!

    I am wondering if you can help with more information on BI Frontend Tools / BEx Tools for Solution Manager 7.1 SPS13. Delivered they are 3.x and we are looking to use the 7.0 functionality. In particular, we want to use the BEx Broadcaster to publish compliance reports. With the current version we can deliver a link by email, we want to utilize the PDF and XLS functionality. Any help is greatly appreciated! Wondering if we need to setup the Portal and BW connections… or can we just upgrade the functionality locally?

    Thanks,

    Tony

    (0) 
    1. Roland Kramer Post author

      Hi,

      I would woundering, too.

      As the Version of SolMan 7.1 contains NetWeaver 7.02 which is not a standalone BW Release probably you will have challenges to make thE BW-JAVA connection to work.

      Nevertheless it is worth a try …

      Best Regards Roland

      (0) 
      1. Tony Price

        Unfortunately, that is not going to work I discovered as the BW system you would need to connect with would require the exact same version of BI_CONT. We have a 7.4 BW landscape so that’s not an option. I guess we’re stuck with it.

        Thanks,

        Tony

        (0) 
        1. Roland Kramer Post author

          The BI_CONT Version is not from concern, as the necessary objects are delivered with the BW system.

          The Challenge is more the BI-JAVA stack for NetWeaver 7.02, but it looks like the LIFECYCLE MGMT TOOLS 7.02 are also updated automatically.

          Best Regards Roland

          (0) 

Leave a Reply