4.3 SP2 Patch5 - biprws Deployment on Websphere

[sumitkumar_gadeela]

Hi All,

We upgraded from 4.2 SP8 to 4.3 SP2 Patch5. On 4.2 SP8 we were on Classic old version of BI launchpad, this is first time on Fiori launchpad.

We have WebSphere on different server and F5 load balancer url. When we launch the F5 url, we get "404 Error" message.

Error:

POST https://businessobjects.info.com/biprws/logon/token 404 (Not Found)

GET https://businessobjects.info.com/biprws/internal/v1/settings/allsettings?appCuid=Ac7UIwmYafpFuhiiw6F... 404 (Not Found)

RequestDispatcher.js:7 Uncaught ReferenceError: BILaunchpadApp is not defined

at RequestDispatcher.sendRequest (RequestDispatcher.js:7:1623)

at Object.sendRequestToTimeoutManagerFilter (Pinger.js:7:4913)

at Object.ping (Pinger.js:7:5152)

at <anonymous>:1:47

Steps:

1.)When we launch the CMC url from F5,https://businessobjects.info.com/BOE/CMC, it works fine, there is no SSO, can login with our LDAP credentials.

2.)We have Trusted Authentication enabled for the users for SSO,

Retrieving_Method=HTTP_HEADER ; Name Parameter=CT_REMOTE_USER

3.) we checked the option "Use Relative URL Path" for Restful Service and dswsbobje Webservice in CMC ->Applications

4.)We also tried unchecking this option and giving F5 load balancer url as "https://businessobjects.info.com/biprws" but we still see the same issue.

5.)We initially had only BOE.ear file deployed on Webpshere, but we later deployed "biprws.ear" and dswsbobje.ear file on websphere and observe same error.

6.)we did not make changes to the "biprws.properties" file or web.xml file form the path

<…Installation Dir…/enterprise_xi40/warfiles/webapps/biprws/WEB-INF/

7.)If we need to make changes to the file, should i replace the

Retrieving_Method=HTTP_HEADER & User_Name_Parameter=X-SAP-TRUSTED-USER

to Retrieving_Method=HTTP_HEADER & User_Name_Parameter=CT_REMOTE_USER

8.)We have been working on multiple tickets with the SAP ( 712642/2022; 692202/2022 ; 622747 / 2022 ; 559983/2022) for the WebSphere F5 url config on 4.3

Thank you all for the response.

[sumitkumar_gadeela]

Hi Denis,

Thank you for the response,

Iam working with our F5 and Ping Identity SSO team to validate all the configurations.

I will get back with an update after testing.

Sumith

[denis_konovalov]

If biprws URL is producing 404 when accessed thru F5, that means one of 2 things :
1. Your F5 is not setup to forward calls to biprws to correct server
or
2. Your biprws web services are not deployed on websphere.

#2 is easy to test - does http(s)://webpsheredirect:webpshereport/biprws works ?
If yes - its F5 issue if not you haven't deployed biprws to websphere or websphere is not loading it.

[sumitkumar_gadeela]

Hi Denis,

Thanks for the input, we validated the url, http(s)://webpsheredirect:webpshereport/biprws and we get the error "Error 500: javax.servlet.ServletException: SRVE0207E: Uncaught initialization exception created by servlet".

we have created new question for biprws deployment issue,

https://answers.sap.com/questions/13739780/43-sp2-deploy-biprws-restful-service-on-websphere.html