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 spended a lot of 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 ... | SCN 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 - SAP Help Background
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.
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
Details of the Line "Version": 1000.7.40.10.2.2015 ...
Main Version.SPS.PL.date
Running the BI-JAVA CTC template
Call the wizard directly with the following URL - http://server.domain.ext:<5<nr>00>/nwa/cfg-wizard
Checking the result
Now, that this hurdle is taken we have to check the the BI-JAVA configuration with the BI diagnostic tool or directly in the System Landscape of the EP.
And the Result in the BI Diagnostic tool (version 0.427)
Note 937697 - Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool
To get to this final state, you have to additionally check/correct the following settings in the NetWeaver Administrator forevaluate_assertion_ticket and ticket according SAP Note 945055. (The Note is not updated since 2007)
[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]
As we are now using assertion tickets instead of logon tickets, the RFC connection from ABAP to JAVA looks a bit different:
Activating the BEx Web templates
Ok. This is also now solved. Now that the BI-JAVA connection technically works, we can check if the standard BEx Web template 0ANALYSIS_PATTERN works correctly. Please remember that you have to at least once activate the necessary web templates once from the SAP BW-BC, otherwise follow the SAP Note
Note 1706282 - Error while loading Web template "0ANALYSIS_PATTERN" (return value "4")
Now you can call with tx. SE38 the Report RS_TEMPLATE_MAINTAIN_70 and choose as Template ID 0ANALYSIS_PATTERN
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.
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:
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
After applying the necessary Corrections to the SAP BI-JAVA EP Instance, also the tx. RSRT finally shows the correct output:
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})
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:
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 bring's a bit of a light into the successful BI-JAVA configuration
Best Regards
Roland Kramer, PM BW/In-Memory
"the happy one's are always curious"