Hello marcbecker , yes actually I copied the whole application.yml from my old CAP 2 project and replaced my cap 1.34 project's application.yml with it. there was a property called "mtxs.enabled: true" . I have removed it and uploaded the same and it worked!. I can't thank you enough for this. I can now work with JCO integration.
the other thing you mentioned that I can use Streamlined MTX with cap 1.34 also. So in that case what I have to do
1. copy the MTX module from the new CAP proejct
2. Replace the the MTX module of CAP 1.34 with the copied folder
3. then change this to "@sap/cds": "^7" to "@sap/cds": "^6" in the package.json of mtx
4. Copy over side-car configuration from CAP 2 mta.yml to CAP 1.34 mta.yml
5. add these values in saas-registry service's appurls property "onSubscriptionAsync: true", "onUnSubscriptionAsync: true", "onUpdateDependenciesAsync: true", "callbackTimeoutMillis: 3600000"
Please let me know if my understanding is correct or do I have to do more configuration changes.
One thing I noticed in CAP 1.34 project's mta.yml files present in GITHUB, that this oauth2-configuration is not mentioned in xsuaa service.
So for trial account router was unable to redirect after successful login .so I had to add that taking reference from CAP 2 project's mta.yml
Hello marcbecker, I tried to implement streamlined mtx . but could not make it work. I am sure I am doing something wrong. can you please guide me ?
1. This is the mta.yaml file :
* not able to add more attachment here .so adding in the below comment. Please please have a look
Hello marcbecker,
...Continuing from above
2. this is the package.json file inside "mtx-sidecar" module
3. after deployment during subscription process getting this error from sidecar
Can you please kindly help me solve this issue
Hello marcbecker , I have one question
what are the main benefits of using stream lined mtx instead of classic mtx.if you can please shed some light on this matter that would be very helpful.
one more problem I am facing in classic mtx. I want to delete tenant specific HDI container on tenant un-subscription process. so I added this code from documentation.
from the log I can see this handler method is getting called. however the tenant Container is not deleted.
also this log is getting printed
{"msg":"Skipping subscription deletion of tenant '8347ef66-0b2d-4140-add6-070d45bda6f2'","level":"INFO","written_ts":"1695454011597000000","logger":"com.sap.cds.services.mt.impl.MtSubscriptionServiceCompatibilityHandler","correlation_id":"30539e53-3956-44c1-5924-2e51eaf8347e","written_at":"2023-09-23T07:26:51.597Z","thread":"http-nio-0.0.0.0-8080-exec-10","type":"log"}
Can you please help me to understand what could be the issue here
Hello marcbecker ,
I am not able to make it work. Getting the same error message. Please help.
*I would like to highlight one point . even though there is no folder with name- "mtx-sidecar" but when I run "mbt build" a folder is created with name "mtx-sidecar" with the following content "gen --> sdc --> _i18n, db, node_modules,srv"
* This is the starting commands of mta.yml
*This is now my sidecar configuration in mta.yaml
*After deployment while tenant subscription getting the error message
STDERR [mtx] - Error: Could not get additional deployment resources
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at /home/vcap/app/node_modules/@sap/cds-mtxs/srv/model-provider.js:85:37
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async next (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-dispatch.js:76:17)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async ModelProviderService.handle (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-dispatch.js:74:10)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async resources4 (/home/vcap/app/node_modules/@sap/cds-mtxs/srv/plugins/hana.js:123:18)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async /home/vcap/app/node_modules/@sap/cds-mtxs/srv/plugins/hana.js:234:7
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async Promise.all (index 1)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async _deploy (/home/vcap/app/node_modules/@sap/cds-mtxs/srv/plugins/hana.js:222:18)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async next (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-dispatch.js:76:17)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async ApplicationService.handle (/home/vcap/app/node_modules/@sap/cds/lib/srv/srv-dispatch.js:74:10)
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR at async _nextTask (/home/vcap/app/node_modules/@sap/cds-mtxs/srv/jobs-service.js:131:12) {
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR code: 500,
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR numericSeverity: 4
2023-09-26T05:51:26.333+0000 [APP/PROC/WEB/0] STDERR }
Hello marcbecker,
Yes last week I have checked that. yes both are different
I tried to replace classic .cdsrc with stream lined .cdsrc
but got some error in during build itself. so I reverted to classic .cdsrc
So should I replace .cdsrc and try again and maybe let you know the error
this the .cdsrc for classic project
this is the .cdsrc for steam lined
Hello marcbecker ,
Sorry for being late in replicating the issue. So when using cdsrc of streamlined mtx getting this error
but I did not change anything anywhere other than those we discussed. could you please guide me
Hello marcbecker, Yes that was the problem. Thanks for correcting me . out of process 1 or process2 which is the preferred way?
Actually as I mentioned in my earlier questions, I am not using CDS. but have kept .cds files in srv and db folder otherwise getting some errors . So what I did was I removed the entire "<!-- STEPS TO BUILD CDS MODEL AND GENERATE POJOs -->" plugin .now I think I have to add again
but I do not have schema.sql or schema-nomocks.sql so will it work If I remove these two executions and keep the rest as it
Hello marcbecker , finally it worked!!! . have kept these execution steps only ,removed the rest of the execution steps. Thank you from the bottom of my heart for helping me out. I am truly grateful.!
Hi marcbecker,
I have created a Multi tenant SAAS application (Non-CAP NodeJS based) and have deployed this app to SAP BTP in the Provider subaccount. Along with the application I have the saas-registry instance and xsuaa instance created in my Provider subaccount. I am also able to subscribe to this application from the Consumer subaccount.
Current Status: So far, I have successfully implemented application subscription from tenant subaccounts using the saas-registry and an xsuaa instance. I’ve also implemented the necessary logic for subscribe and unsubscribe events in the backend.
Note: This is a pure backend application, and I am not using an Approuter, as there is no frontend component involved. The application is intended to be consumed by tenant-specific backend or frontend apps via API calls.
Problems:
- When I subscribe app in consumer subaccount, the xsuaa instance (using tenant-mode as "shared in provider subaccount) is not automatically created in consumer subaccount.
- To address this, I added event for getting dependencies while subscribing in backend the code is shown in below picture.
- Also added "url" for "getDependencies" in "appUrls" and dependencies detail in SaaS configuration file as shown below.
- After these changes, I tried subscribing to the app again from the consumer subaccount got an error shown below.
Asking for Suggestions:
- How can I achieve the automatic creation of an XSUAA instance in the consumer subaccount when subscribing to the app, to ensure full isolation between consumer subaccounts?
- If not then how can I achieve independent OAuth 2.0 Authentication for tenants specific to their subaccount?
| User | Count |
|---|---|
| 30 | |
| 22 | |
| 16 | |
| 8 | |
| 7 | |
| 7 | |
| 5 | |
| 4 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.