on 12-04-2018 11:17 PM
Our scenario:
- We would like to have some re-usable General Master Data-like Calculation Views that can be used across different reporting Calculation Views.
- The General Master Data will be available for anyone with a HANA DB ID.
- The reporting Calculation Views are limited just to a user's business area however.
- We have no legacy XS Classic content, and would like to keep it that way per SAP's statement that XS Classic is going away.
Our to-date attempted approach:
- We have created an XSA Project with a DB Module that contains the Master Data Dimension Calculation Views. The data these views are modeled on is in an ABAP-managed schema, and exposed via a User-Provided Service.
- We then want to create separate XSA Projects per business/process area to expose the reporting calculation views. These views are against data also in the same monolithic ABAP schema, and we are using HDB Roles to manage access to the DB module/container level.
- We have established cross-container access to the Master Data DB Module and can access the MD Dimension Calculation Views via .hdbsynonyms.
- We can then bring the Dimension CVs into our business reporting CV into a typical Star Join type view and it brings across the Dimension CV semantics, etc.
Our potential problem:
If we enhance a Dimension CV in our MD project, while it does not break our reporting CV that uses it via Synonym, the Dimension CV changes are not reflected in the reporting CV. Further, it breaks the reporting CV in WebIDE and gives it a red X and I have to remove and re-add the synonym in the Star Join. This obviously is not maintainable at scale. Also, things like Data Lineage in CV modeling context menu is incomplete, since the reporting CV cannot see beyond its own container (understandably so).
At this point, I am questioning whether my approach is logical. I've been told XSA is the now and the future, and addresses some inherent issues with SYS_BIC and SYS_REPO so I'm sold on adopting it.
Has anybody crossed this bridge already? Is this the proper way to try to keep smaller manageable projects, while at the same time having reusable components? I'm trying to summarize as best as I can so that someone will actually read this to the end, but I can supply any further details or rationale if you like.
Thanks for any suggestions.
Design question ended up being moot. The "red error" issue mentioned was due to a timeout on webide for hrtt-service on the backend after 30 seconds.
Leaving this technical config answer here in case others face the same issue down the road. We were able to identify a timeout parameter in XSA Cockpit to change which extended the timeout length past 30 seconds. However we also identified that the issue with what was causing the service to take so long. Our .hdbgrants file tied back to a global_role to object_owner and application_user. This global role had an *extremely* high number of object privileges for SELECT access on DB Tables in the mentioned monolithic ABAP schema. (Longer story why for another day). We will work on significantly reducing those objects down which will make things snappier while opening a CV, but we did also locate the timeout parameter on XSA Cockpit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for sharing the resolution Mike... was the timeout in the XSA cockpit or the cockpit manager? on my blog...
https://blogs.sap.com/2018/09/20/my-experience-w-hxe-2-sp03-cockpit-cockpit-manager/
i saw it in the cockpit manager.. is that the same place you are referring to ? thanks again
mike... try.... doing the same steps again 🙂
it may work this time
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Doing the same steps again and expecting different results? Definition of insanity, right up my alley. 🙂
But yes, after I tried to illustrate the problem to you this morning and did not get the error, I assumed I did something wrong until a developer this morning who had an untouched project overnight is now also randomly getting the "red error". I suspect this may a sizing/XSA issue with a service in WebIDE?
Example intermittent error:
EDIT:
On a hunch, I looked at the Chrome F12 debugger Network traffic. For every red X, it's corresponding with an HTTP 504 Gateway Timeout error in a webide call. This is looking more and more like a sizing issue, rather than completely a design issue.
EDIT 2:
Web IDE logs look to be pointing to hrtt-service timing out.
(23803)[1543957438576] [APP/7-1] SYS #2.0#2018 12 04
15:03:58:576#-06:00#ERROR#/Handler########RHOWLES#I1QRUmv-f4dJg28SW32OENTZnFGUSYix######jpa8dkxl#PLAIN##GET
request to /metadataapi/dbobjects/Airport?xml=true completed with status 504 -
Request to https://ipaper-sap-hrtt-service.bwvxsa.sap.ipaper.com:35133/metadataapi/dbobjects/Airport?xml=true
failed with a timeout#
(23804)[1543957438578] [APP/7-1]
ERR VError: error while forwarding request to https://ipaper-sap-hrtt-service.bwvxsa.sap.ipaper.com:35133/metadataapi/dbobjects/Airport?xml=true:
socket hang up
(23805)[1543957438578] [APP/7-1]
ERR at ClientRequest.<anonymous>
(/hana/shared/BWV/xs/app_working/u02abwgdb02/executionroot/a70403a5-5525-48af-a80c-e1d40facb58c/app/node_modules/approuter/lib/middleware/request-handler.js:57:37)
(23806)[1543957438578]
[APP/7-1] ERR at emitOne (events.js:116:13)
(23807)[1543957438578]
[APP/7-1] ERR at ClientRequest.emit (events.js:211:7)
(23808)[1543957438578]
[APP/7-1] ERR at
TLSSocket.socketCloseListener (_http_client.js:363:9)
(23809)[1543957438578]
[APP/7-1] ERR at emitOne (events.js:121:20)
(23810)[1543957438578]
[APP/7-1] ERR at TLSSocket.emit (events.js:211:7)
(23811)[1543957438578]
[APP/7-1] ERR at _handle.close (net.js:557:12)
(23812)[1543957438578]
[APP/7-1] ERR at TCP.done [as _onclose]
(_tls_wrap.js:358:7)<br>
I'm going to ask to get hrtt-service scaled up to see if this helps.
EDIT 3:
Scaling it up and out didn't do anything helpful. The timeout occurs exactly at 30 seconds. I cannot locate where this timeout can be configured. Opened an SAP Incident for lack of another option. Will update this question with SAP's answer in the event I don't get one here.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.