the service definition does not exist. Error after adding two user provided services

[sucheno]

Hello,

I am trying to add two user provided services to access 2 different classic schemas in my container.

DB module build and adding synonyms are working fine if I add only any one of those services, but not success if I add both of them at once.

I have added two seperate .hdbgrants files for these services. ( these files are built successfully before building DB module)

Have you succeeded to consume 2 user provided services in the same project?

Can anyone help to figure out whats going wrong here?

Thanks.

[sucheno]

The issue is identified with group: SERVICE_REPLACEMENTS

If we remove this group and linked parameters & properties and maintain the just the Service name, it is working fine. But this is not SAP recommended way.

[Ivan-Mirisola]

Hi sucheno,

Just to clarify: group SERVICE_REPLACEMENTS is intended for cross-container access between two HDIs. If you want to have access to a specific Schema in a HANA DB that is not an HDI, then the recommended way is the way you are currently using.

Best regards,
Ivan

[sucheno]

Hi ivan.mirisola,

Thanks for the clarification.

Still, SERVICE_REPLACEMENTS is working only when add for one cross HDI container service to my project.

If we add more than one HDI container, Build is throwing the error.

[Ivan-Mirisola]

Hi sucheno,

I've seen this behavior before on earlier HANA versions. Which version are you using?

Are you also specifying a TARGET_CONTAINER property on your hdb module pointing to your hdi service using a variable such as ~{container-name}.

There is a full example here using more than one cross-container:

https://github.com/SAP/com.sap.openSAP.hana5.example/blob/master/mta.yaml

Check the example and see if your mta.yaml file has more or less the same approach.

If you have the latest version of WebIDE for HANA development installed on your instance, you could use the New --> Add SAP HANA Service Connection.

Best regards,
Ivan

[sucheno]

Hi ivan.mirisola,

TARGET_CONTAINER property is also specified in MTA for container. Also, I am using WebIDE wizard to add the cross-container services.

I am using 2.0 SPS 01 for my database module. However, It is found that there is some issue while using logical service names in .hdbgrants file.

Now, I am able to successfully build the database module by specifying physical service names in .hdbgrants file instead of logical key specified in MTA.

I have raised SAP incident and checking for why logical service name is not accepted in .hdbgrants file.

This should be supported as per the example project you have shared and as per the below SAP tutorial.

https://developers.sap.com/tutorials/xsa-create-user-provided-anonymous-service.html

Usage of logical service name is indeed working fine when we use one cross-container service. it is only not working when we add more than one service to my project.

Is there anything you suspect here going wrong?

Best Regards,

Suchen.

[Ivan-Mirisola]

Hi Suchen Oguri,

I think the problem may be on the SP you are using. Have you updated the WebIDE to the latest version? As I recall, I had the same issue with 1.0 SP12 and support team indicated me to update WebIDE to the latest version available. WebIDE doesn't follow the same SP stack as HANA - it is independent. So you can apply the latest version on any stack. I had the latest version installed on 1.0 SP12 for instance!
Hope this helps!

Best regards,
Ivan

[sucheno]

Hi ivan.mirisola,

Thanks for your responses.

SAP confirmed this as bug and they are fixing it.

Best Regards,

Suchen

[TomF]

Hi Suchen Oguri,

I'm experiencing the same issue.

Can you show me how you fixed this please. You can send it to my é-mail as well if you prefer that way.

Kind regards,

Tom.

[sucheno]

Hi tom.franckaert2,

Please refer the the answers. I have provided now.

Best Regards,

Suchen.

[sucheno · Accepted solution]

Hi,

After raising this to SAP, This issue has been confirmed as bug and they are planning to release the fix in July.

I followed this workaround meanwhile. You can use the physical service name instead of WebIDE generated logical name as below.

      - name: SCHEMA1-grantor
      - name: SCHEMA2-grantor
----
resources:
  - name: SCHEMA1-grantor
    type: org.cloudfoundry.existing-service
  - name: SCHEMA2-grantor
    type: org.cloudfoundry.existing-service

However, Below is the WebIDE default and recommended way of using after the bug fix.

 - name: cross-container-service-1
        group: SERVICE_REPLACEMENTS
        properties:
          key: ServiceName_1
          service: ~{the-service-name}
                            
      - name: cross-container-service-2
        group: SERVICE_REPLACEMENTS
        properties:
          key: ServiceName_2
          service: ~{the-service-name}                      
----
resources:
  - name: cross-container-service-1
    parameters:
       service-name: SCHEMA1-grantor
    properties:
       the-service-name: ${service-name}
    type: org.cloudfoundry.existing-service

  - name: cross-container-service-2
    parameters:
       service-name: SCHEMA2-grantor
    properties:
       the-service-name: ${service-name}
    type: org.cloudfoundry.existing-service

Hope this helps.

Regards,

Suchen Oguri.