Author |
Message
|
KavitaK_TW |
Posted: Tue Dec 05, 2017 1:01 am Post subject: SAP node deployment error while using same rfc id |
|
|
Newbie
Joined: 04 Dec 2017 Posts: 3
|
Hello All,
I am trying to deploy 2 message flows with SAP node which are using same SAP adapter connection and same rfc id.
but I am getting error as below
BIP5035E: The XMLNSC validator signalled that an error occurred at line 15 while validating a XML schema. The file being processed
was SapGIDocObj.xsd in library SAP_TEST_MSGSET.
The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same
name this schema contains two occurrences of 'http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapgidocObj,SapGIDocObj'.
Errors have occurred during the validation of a XML schema.
IIB V10
Appreciate your suggestions. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Dec 05, 2017 3:19 am Post subject: Re: SAP node deployment error while using same rfc id |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
KavitaK_TW wrote: |
Hello All,
I am trying to deploy 2 message flows with SAP node which are using same SAP adapter connection and same rfc id.
but I am getting error as below
BIP5035E: The XMLNSC validator signalled that an error occurred at line 15 while validating a XML schema. The file being processed
was SapGIDocObj.xsd in library SAP_TEST_MSGSET.
The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same
name this schema contains two occurrences of 'http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapgidocObj,SapGIDocObj'.
Errors have occurred during the validation of a XML schema.
IIB V10
Appreciate your suggestions. |
If you are using the same adapter you have to download both schemas in the adapter. You may need to use the adapter as a shared resource and the schemas as well.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
KavitaK_TW |
Posted: Tue Dec 05, 2017 4:35 am Post subject: Re: SAP node deployment error while using same rfc id |
|
|
Newbie
Joined: 04 Dec 2017 Posts: 3
|
fjb_saper wrote: |
KavitaK_TW wrote: |
Hello All,
I am trying to deploy 2 message flows with SAP node which are using same SAP adapter connection and same rfc id.
but I am getting error as below
BIP5035E: The XMLNSC validator signalled that an error occurred at line 15 while validating a XML schema. The file being processed
was SapGIDocObj.xsd in library SAP_TEST_MSGSET.
The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same
name this schema contains two occurrences of 'http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapgidocObj,SapGIDocObj'.
Errors have occurred during the validation of a XML schema.
IIB V10
Appreciate your suggestions. |
If you are using the same adapter you have to download both schemas in the adapter. You may need to use the adapter as a shared resource and the schemas as well.
Have fun  |
I have single schema. I have added same msg set in 2 message flows and trying to deploy it in same EG (integration server) on a Node. The reason is I need to prepare copy of existing environment to new environment. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Dec 06, 2017 8:40 am Post subject: Re: SAP node deployment error while using same rfc id |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
KavitaK_TW wrote: |
I have single schema. I have added same msg set in 2 message flows and trying to deploy it in same EG (integration server) on a Node. The reason is I need to prepare copy of existing environment to new environment. |
Then you should have different adapters. Until the environments are separate you can set the same config on each adapter _________________ MQ & Broker admin |
|
Back to top |
|
 |
KavitaK_TW |
Posted: Fri Dec 08, 2017 5:14 am Post subject: Re: SAP node deployment error while using same rfc id |
|
|
Newbie
Joined: 04 Dec 2017 Posts: 3
|
Thanks for the reply.
I have deployed the message flows on separate Integration server(EG) on same Node and it worked fine. |
|
Back to top |
|
 |
|