How Can I bind different Watson Discovery to each CF application











up vote
0
down vote

favorite












I am creating CF application with one Resource group, one CF org, one Space.



I bound different Watson Discovery to each CF application.



When I get an error saying



 "Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs."


Specifically, The first bind(A_0001_APP) seems to be working fine but the second bind(D_0001_APP) not working as desired.



Is this the right approach?



Any help will be appreciated.



Here is a simplified log.



####################################################################################
# Bind to A_0001_APP -> That is absolutely fine.
####################################################################################
$ ibmcloud target
API endpoint: https://api.au-syd.bluemix.net
Region: au-syd
User: *************************
Account: *************************
Resource group: d_resource01
CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
Org: d_org01
Space: dev


$ ibmcloud cf push A_0001_APP
.....


$ ibmcloud resource service-instance-create A_0001_DISCOVERY discovery advanced jp-tok
Creating service instance A_0001_DISCOVERY in resource group d_resource01 of account *************************
OK
Service instance A_0001_DISCOVERY was created.
Name Location State Type Tags
A_0001_DISCOVERY jp-tok inactive service_instance


$ ibmcloud resource service-key-create A_0001_DISCOVERY_CREDENTIAL Manager --instance-name A_0001_DISCOVERY
Creating service key of service instance A_0001_DISCOVERY under account *************************.
OK
Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
Name: A_0001_DISCOVERY_CREDENTIAL
ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
Created At: Mon Nov 19 07:57:03 UTC 2018
State: active
Credentials: .......

$ ibmcloud resource service-alias-create A_0001_DISCOVERY_ALIAS --instance-name A_0001_DISCOVERY
Creating alias A_0001_DISCOVERY_ALIAS of service instance A_0001_DISCOVERY from resource group d_resource01 into space dev...
OK
Service alias A_0001_DISCOVERY_ALIAS was successfully created.

ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
Name: A_0001_DISCOVERY_ALIAS
State active
Service Instance: A_0001_DISCOVERY
Space: dev
Tags:
Parameters:

$ ibmcloud resource service-binding-create A_0001_DISCOVERY_ALIAS A_0001_APP Manager --service-id my_service
Binding service alias A_0001_DISCOVERY_ALIAS to app A_0001_APP in space dev...
OK
Service binding crn:v1:bluemix:public:discovery:au-syd:a/:*************************:resource-binding::************************* was created.


####################################################################################
# Bind to D_0001_APP -> I can't create service-binding.
####################################################################################
$ ibmcloud target
API endpoint: https://api.au-syd.bluemix.net
Region: au-syd
User: *************************
Account: *************************
Resource group: d_resource01
CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
Org: d_org01
Space: dev

$ ibmcloud cf push D_0001_APP
.....

$ ibmcloud resource service-instance-create D_0001_DISCOVERY discovery advanced jp-tok
Creating service instance D_0001_DISCOVERY in resource group d_resource01 of account *************************
OK
Service instance D_0001_DISCOVERY was created.
Name Location State Type Tags
D_0001_DISCOVERY jp-tok inactive service_instance

$ ibmcloud resource service-key-create D_0001_DISCOVERY_CREDENTIAL Manager --instance-name D_0001_DISCOVERY
Creating service key of service instance D_0001_DISCOVERY under account *************************.
OK
Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
Name: D_0001_DISCOVERY_CREDENTIAL
ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
Created At: Tue Nov 20 10:12:56 UTC 2018
State: active
Credentials: .......

$ ibmcloud resource service-alias-create D_0001_DISCOVERY_ALIAS --instance-name D_0001_DISCOVERY
Creating alias D_0001_DISCOVERY_ALIAS of service instance D_0001_DISCOVERY from resource group d_resource01 into space dev...
OK
Service alias D_0001_DISCOVERY_ALIAS was successfully created.
ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
Name: D_0001_DISCOVERY_ALIAS
State active
Service Instance: D_0001_DISCOVERY
Space: dev
Tags:
Parameters:

$ ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id my_service
Binding service alias D_0001_DISCOVERY_ALIAS to app D_0001_APP in space dev...
FAILED
Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs.
script returned exit code 1









share|improve this question




























    up vote
    0
    down vote

    favorite












    I am creating CF application with one Resource group, one CF org, one Space.



    I bound different Watson Discovery to each CF application.



    When I get an error saying



     "Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs."


    Specifically, The first bind(A_0001_APP) seems to be working fine but the second bind(D_0001_APP) not working as desired.



    Is this the right approach?



    Any help will be appreciated.



    Here is a simplified log.



    ####################################################################################
    # Bind to A_0001_APP -> That is absolutely fine.
    ####################################################################################
    $ ibmcloud target
    API endpoint: https://api.au-syd.bluemix.net
    Region: au-syd
    User: *************************
    Account: *************************
    Resource group: d_resource01
    CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
    Org: d_org01
    Space: dev


    $ ibmcloud cf push A_0001_APP
    .....


    $ ibmcloud resource service-instance-create A_0001_DISCOVERY discovery advanced jp-tok
    Creating service instance A_0001_DISCOVERY in resource group d_resource01 of account *************************
    OK
    Service instance A_0001_DISCOVERY was created.
    Name Location State Type Tags
    A_0001_DISCOVERY jp-tok inactive service_instance


    $ ibmcloud resource service-key-create A_0001_DISCOVERY_CREDENTIAL Manager --instance-name A_0001_DISCOVERY
    Creating service key of service instance A_0001_DISCOVERY under account *************************.
    OK
    Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
    Name: A_0001_DISCOVERY_CREDENTIAL
    ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
    Created At: Mon Nov 19 07:57:03 UTC 2018
    State: active
    Credentials: .......

    $ ibmcloud resource service-alias-create A_0001_DISCOVERY_ALIAS --instance-name A_0001_DISCOVERY
    Creating alias A_0001_DISCOVERY_ALIAS of service instance A_0001_DISCOVERY from resource group d_resource01 into space dev...
    OK
    Service alias A_0001_DISCOVERY_ALIAS was successfully created.

    ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
    Name: A_0001_DISCOVERY_ALIAS
    State active
    Service Instance: A_0001_DISCOVERY
    Space: dev
    Tags:
    Parameters:

    $ ibmcloud resource service-binding-create A_0001_DISCOVERY_ALIAS A_0001_APP Manager --service-id my_service
    Binding service alias A_0001_DISCOVERY_ALIAS to app A_0001_APP in space dev...
    OK
    Service binding crn:v1:bluemix:public:discovery:au-syd:a/:*************************:resource-binding::************************* was created.


    ####################################################################################
    # Bind to D_0001_APP -> I can't create service-binding.
    ####################################################################################
    $ ibmcloud target
    API endpoint: https://api.au-syd.bluemix.net
    Region: au-syd
    User: *************************
    Account: *************************
    Resource group: d_resource01
    CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
    Org: d_org01
    Space: dev

    $ ibmcloud cf push D_0001_APP
    .....

    $ ibmcloud resource service-instance-create D_0001_DISCOVERY discovery advanced jp-tok
    Creating service instance D_0001_DISCOVERY in resource group d_resource01 of account *************************
    OK
    Service instance D_0001_DISCOVERY was created.
    Name Location State Type Tags
    D_0001_DISCOVERY jp-tok inactive service_instance

    $ ibmcloud resource service-key-create D_0001_DISCOVERY_CREDENTIAL Manager --instance-name D_0001_DISCOVERY
    Creating service key of service instance D_0001_DISCOVERY under account *************************.
    OK
    Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
    Name: D_0001_DISCOVERY_CREDENTIAL
    ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
    Created At: Tue Nov 20 10:12:56 UTC 2018
    State: active
    Credentials: .......

    $ ibmcloud resource service-alias-create D_0001_DISCOVERY_ALIAS --instance-name D_0001_DISCOVERY
    Creating alias D_0001_DISCOVERY_ALIAS of service instance D_0001_DISCOVERY from resource group d_resource01 into space dev...
    OK
    Service alias D_0001_DISCOVERY_ALIAS was successfully created.
    ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
    Name: D_0001_DISCOVERY_ALIAS
    State active
    Service Instance: D_0001_DISCOVERY
    Space: dev
    Tags:
    Parameters:

    $ ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id my_service
    Binding service alias D_0001_DISCOVERY_ALIAS to app D_0001_APP in space dev...
    FAILED
    Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs.
    script returned exit code 1









    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I am creating CF application with one Resource group, one CF org, one Space.



      I bound different Watson Discovery to each CF application.



      When I get an error saying



       "Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs."


      Specifically, The first bind(A_0001_APP) seems to be working fine but the second bind(D_0001_APP) not working as desired.



      Is this the right approach?



      Any help will be appreciated.



      Here is a simplified log.



      ####################################################################################
      # Bind to A_0001_APP -> That is absolutely fine.
      ####################################################################################
      $ ibmcloud target
      API endpoint: https://api.au-syd.bluemix.net
      Region: au-syd
      User: *************************
      Account: *************************
      Resource group: d_resource01
      CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
      Org: d_org01
      Space: dev


      $ ibmcloud cf push A_0001_APP
      .....


      $ ibmcloud resource service-instance-create A_0001_DISCOVERY discovery advanced jp-tok
      Creating service instance A_0001_DISCOVERY in resource group d_resource01 of account *************************
      OK
      Service instance A_0001_DISCOVERY was created.
      Name Location State Type Tags
      A_0001_DISCOVERY jp-tok inactive service_instance


      $ ibmcloud resource service-key-create A_0001_DISCOVERY_CREDENTIAL Manager --instance-name A_0001_DISCOVERY
      Creating service key of service instance A_0001_DISCOVERY under account *************************.
      OK
      Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
      Name: A_0001_DISCOVERY_CREDENTIAL
      ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
      Created At: Mon Nov 19 07:57:03 UTC 2018
      State: active
      Credentials: .......

      $ ibmcloud resource service-alias-create A_0001_DISCOVERY_ALIAS --instance-name A_0001_DISCOVERY
      Creating alias A_0001_DISCOVERY_ALIAS of service instance A_0001_DISCOVERY from resource group d_resource01 into space dev...
      OK
      Service alias A_0001_DISCOVERY_ALIAS was successfully created.

      ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
      Name: A_0001_DISCOVERY_ALIAS
      State active
      Service Instance: A_0001_DISCOVERY
      Space: dev
      Tags:
      Parameters:

      $ ibmcloud resource service-binding-create A_0001_DISCOVERY_ALIAS A_0001_APP Manager --service-id my_service
      Binding service alias A_0001_DISCOVERY_ALIAS to app A_0001_APP in space dev...
      OK
      Service binding crn:v1:bluemix:public:discovery:au-syd:a/:*************************:resource-binding::************************* was created.


      ####################################################################################
      # Bind to D_0001_APP -> I can't create service-binding.
      ####################################################################################
      $ ibmcloud target
      API endpoint: https://api.au-syd.bluemix.net
      Region: au-syd
      User: *************************
      Account: *************************
      Resource group: d_resource01
      CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
      Org: d_org01
      Space: dev

      $ ibmcloud cf push D_0001_APP
      .....

      $ ibmcloud resource service-instance-create D_0001_DISCOVERY discovery advanced jp-tok
      Creating service instance D_0001_DISCOVERY in resource group d_resource01 of account *************************
      OK
      Service instance D_0001_DISCOVERY was created.
      Name Location State Type Tags
      D_0001_DISCOVERY jp-tok inactive service_instance

      $ ibmcloud resource service-key-create D_0001_DISCOVERY_CREDENTIAL Manager --instance-name D_0001_DISCOVERY
      Creating service key of service instance D_0001_DISCOVERY under account *************************.
      OK
      Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
      Name: D_0001_DISCOVERY_CREDENTIAL
      ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
      Created At: Tue Nov 20 10:12:56 UTC 2018
      State: active
      Credentials: .......

      $ ibmcloud resource service-alias-create D_0001_DISCOVERY_ALIAS --instance-name D_0001_DISCOVERY
      Creating alias D_0001_DISCOVERY_ALIAS of service instance D_0001_DISCOVERY from resource group d_resource01 into space dev...
      OK
      Service alias D_0001_DISCOVERY_ALIAS was successfully created.
      ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
      Name: D_0001_DISCOVERY_ALIAS
      State active
      Service Instance: D_0001_DISCOVERY
      Space: dev
      Tags:
      Parameters:

      $ ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id my_service
      Binding service alias D_0001_DISCOVERY_ALIAS to app D_0001_APP in space dev...
      FAILED
      Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs.
      script returned exit code 1









      share|improve this question















      I am creating CF application with one Resource group, one CF org, one Space.



      I bound different Watson Discovery to each CF application.



      When I get an error saying



       "Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs."


      Specifically, The first bind(A_0001_APP) seems to be working fine but the second bind(D_0001_APP) not working as desired.



      Is this the right approach?



      Any help will be appreciated.



      Here is a simplified log.



      ####################################################################################
      # Bind to A_0001_APP -> That is absolutely fine.
      ####################################################################################
      $ ibmcloud target
      API endpoint: https://api.au-syd.bluemix.net
      Region: au-syd
      User: *************************
      Account: *************************
      Resource group: d_resource01
      CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
      Org: d_org01
      Space: dev


      $ ibmcloud cf push A_0001_APP
      .....


      $ ibmcloud resource service-instance-create A_0001_DISCOVERY discovery advanced jp-tok
      Creating service instance A_0001_DISCOVERY in resource group d_resource01 of account *************************
      OK
      Service instance A_0001_DISCOVERY was created.
      Name Location State Type Tags
      A_0001_DISCOVERY jp-tok inactive service_instance


      $ ibmcloud resource service-key-create A_0001_DISCOVERY_CREDENTIAL Manager --instance-name A_0001_DISCOVERY
      Creating service key of service instance A_0001_DISCOVERY under account *************************.
      OK
      Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
      Name: A_0001_DISCOVERY_CREDENTIAL
      ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
      Created At: Mon Nov 19 07:57:03 UTC 2018
      State: active
      Credentials: .......

      $ ibmcloud resource service-alias-create A_0001_DISCOVERY_ALIAS --instance-name A_0001_DISCOVERY
      Creating alias A_0001_DISCOVERY_ALIAS of service instance A_0001_DISCOVERY from resource group d_resource01 into space dev...
      OK
      Service alias A_0001_DISCOVERY_ALIAS was successfully created.

      ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
      Name: A_0001_DISCOVERY_ALIAS
      State active
      Service Instance: A_0001_DISCOVERY
      Space: dev
      Tags:
      Parameters:

      $ ibmcloud resource service-binding-create A_0001_DISCOVERY_ALIAS A_0001_APP Manager --service-id my_service
      Binding service alias A_0001_DISCOVERY_ALIAS to app A_0001_APP in space dev...
      OK
      Service binding crn:v1:bluemix:public:discovery:au-syd:a/:*************************:resource-binding::************************* was created.


      ####################################################################################
      # Bind to D_0001_APP -> I can't create service-binding.
      ####################################################################################
      $ ibmcloud target
      API endpoint: https://api.au-syd.bluemix.net
      Region: au-syd
      User: *************************
      Account: *************************
      Resource group: d_resource01
      CF API endpoint: https://api.au-syd.bluemix.net (API version: 2.106.0)
      Org: d_org01
      Space: dev

      $ ibmcloud cf push D_0001_APP
      .....

      $ ibmcloud resource service-instance-create D_0001_DISCOVERY discovery advanced jp-tok
      Creating service instance D_0001_DISCOVERY in resource group d_resource01 of account *************************
      OK
      Service instance D_0001_DISCOVERY was created.
      Name Location State Type Tags
      D_0001_DISCOVERY jp-tok inactive service_instance

      $ ibmcloud resource service-key-create D_0001_DISCOVERY_CREDENTIAL Manager --instance-name D_0001_DISCOVERY
      Creating service key of service instance D_0001_DISCOVERY under account *************************.
      OK
      Service key crn:v1:bluemix:public:discovery:jp-tok:a/*************************:resource-key:************************* was created.
      Name: D_0001_DISCOVERY_CREDENTIAL
      ID: crn:v1:bluemix:public:discovery:jp-tok:a/*************************:*************************:resource-key:*************************
      Created At: Tue Nov 20 10:12:56 UTC 2018
      State: active
      Credentials: .......

      $ ibmcloud resource service-alias-create D_0001_DISCOVERY_ALIAS --instance-name D_0001_DISCOVERY
      Creating alias D_0001_DISCOVERY_ALIAS of service instance D_0001_DISCOVERY from resource group d_resource01 into space dev...
      OK
      Service alias D_0001_DISCOVERY_ALIAS was successfully created.
      ID: crn:v1:bluemix:public:discovery:au-syd:a//*************************::/*************************::resource-alias:/*************************:
      Name: D_0001_DISCOVERY_ALIAS
      State active
      Service Instance: D_0001_DISCOVERY
      Space: dev
      Tags:
      Parameters:

      $ ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id my_service
      Binding service alias D_0001_DISCOVERY_ALIAS to app D_0001_APP in space dev...
      FAILED
      Error response from the server. Status code: 400; description: 400 Code: BXNIM0150E, Message: The service name part of the provided CRNs must be unique, Details: Service name 'discovery' must be unique for all provided CRNs.
      script returned exit code 1






      ibm-cloud ibm-watson watson-discovery






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 21 at 12:43









      Vidyasagar Machupalli

      639515




      639515










      asked Nov 20 at 13:18









      numa

      31




      31
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          As mentioned in the error, the service name part of the CRN (Cloud Resource Name) must be unique.



          The base canonical format of a CRN is:



          crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource


          The service-name segment uniquely identifies a capability (service, component, product) being offered by the cloud. The capability can be a user provided service such as with the services that are listed in the IBM Cloud catalog, or an internal architectural component critical to the IBM Cloud functionality.



          The service-name indicates the service that the resource belongs to, and IBM Cloud enforces global uniqueness of service names. The service-name must be alphanumeric, lowercase, no spaces or special characters other than '-'.



          Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id



          ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID






          share|improve this answer



















          • 1




            Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
            – numa
            Nov 21 at 0:58










          • @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
            – Vidyasagar Machupalli
            Nov 21 at 4:38












          • Problem solved! Your explanation really helped. Thanks!
            – numa
            Nov 21 at 12:25













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393897%2fhow-can-i-bind-different-watson-discovery-to-each-cf-application%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote



          accepted










          As mentioned in the error, the service name part of the CRN (Cloud Resource Name) must be unique.



          The base canonical format of a CRN is:



          crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource


          The service-name segment uniquely identifies a capability (service, component, product) being offered by the cloud. The capability can be a user provided service such as with the services that are listed in the IBM Cloud catalog, or an internal architectural component critical to the IBM Cloud functionality.



          The service-name indicates the service that the resource belongs to, and IBM Cloud enforces global uniqueness of service names. The service-name must be alphanumeric, lowercase, no spaces or special characters other than '-'.



          Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id



          ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID






          share|improve this answer



















          • 1




            Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
            – numa
            Nov 21 at 0:58










          • @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
            – Vidyasagar Machupalli
            Nov 21 at 4:38












          • Problem solved! Your explanation really helped. Thanks!
            – numa
            Nov 21 at 12:25

















          up vote
          0
          down vote



          accepted










          As mentioned in the error, the service name part of the CRN (Cloud Resource Name) must be unique.



          The base canonical format of a CRN is:



          crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource


          The service-name segment uniquely identifies a capability (service, component, product) being offered by the cloud. The capability can be a user provided service such as with the services that are listed in the IBM Cloud catalog, or an internal architectural component critical to the IBM Cloud functionality.



          The service-name indicates the service that the resource belongs to, and IBM Cloud enforces global uniqueness of service names. The service-name must be alphanumeric, lowercase, no spaces or special characters other than '-'.



          Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id



          ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID






          share|improve this answer



















          • 1




            Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
            – numa
            Nov 21 at 0:58










          • @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
            – Vidyasagar Machupalli
            Nov 21 at 4:38












          • Problem solved! Your explanation really helped. Thanks!
            – numa
            Nov 21 at 12:25















          up vote
          0
          down vote



          accepted







          up vote
          0
          down vote



          accepted






          As mentioned in the error, the service name part of the CRN (Cloud Resource Name) must be unique.



          The base canonical format of a CRN is:



          crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource


          The service-name segment uniquely identifies a capability (service, component, product) being offered by the cloud. The capability can be a user provided service such as with the services that are listed in the IBM Cloud catalog, or an internal architectural component critical to the IBM Cloud functionality.



          The service-name indicates the service that the resource belongs to, and IBM Cloud enforces global uniqueness of service names. The service-name must be alphanumeric, lowercase, no spaces or special characters other than '-'.



          Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id



          ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID






          share|improve this answer














          As mentioned in the error, the service name part of the CRN (Cloud Resource Name) must be unique.



          The base canonical format of a CRN is:



          crn:version:cname:ctype:service-name:location:scope:service-instance:resource-type:resource


          The service-name segment uniquely identifies a capability (service, component, product) being offered by the cloud. The capability can be a user provided service such as with the services that are listed in the IBM Cloud catalog, or an internal architectural component critical to the IBM Cloud functionality.



          The service-name indicates the service that the resource belongs to, and IBM Cloud enforces global uniqueness of service names. The service-name must be alphanumeric, lowercase, no spaces or special characters other than '-'.



          Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id



          ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 21 at 4:41

























          answered Nov 20 at 15:19









          Vidyasagar Machupalli

          639515




          639515








          • 1




            Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
            – numa
            Nov 21 at 0:58










          • @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
            – Vidyasagar Machupalli
            Nov 21 at 4:38












          • Problem solved! Your explanation really helped. Thanks!
            – numa
            Nov 21 at 12:25
















          • 1




            Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
            – numa
            Nov 21 at 0:58










          • @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
            – Vidyasagar Machupalli
            Nov 21 at 4:38












          • Problem solved! Your explanation really helped. Thanks!
            – numa
            Nov 21 at 12:25










          1




          1




          Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
          – numa
          Nov 21 at 0:58




          Hi Vidyasagar. Thank you for your quick reply. I think it is just as you say. But unfortunately I used a unique SERVICE_ALIAS_NAME for each binding as you said. Please try it at your convenience. Thanks.
          – numa
          Nov 21 at 0:58












          @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
          – Vidyasagar Machupalli
          Nov 21 at 4:38






          @numa Yes. I am able to reproduce the issue with unique alias names and what worked for me is a different service-id ibmcloud resource service-binding-create D_0001_DISCOVERY_ALIAS D_0001_APP Manager --service-id myserviceID. Edited my answer with more information
          – Vidyasagar Machupalli
          Nov 21 at 4:38














          Problem solved! Your explanation really helped. Thanks!
          – numa
          Nov 21 at 12:25






          Problem solved! Your explanation really helped. Thanks!
          – numa
          Nov 21 at 12:25




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393897%2fhow-can-i-bind-different-watson-discovery-to-each-cf-application%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          404 Error Contact Form 7 ajax form submitting

          How to know if a Active Directory user can login interactively

          TypeError: fit_transform() missing 1 required positional argument: 'X'