Skip to Content

<u>Abstract :</u><br />

Many times we come across a scenario when we get multiple referenced external definitions from an external system or maybe we need a mass import of the external definitions in our ESR. Till PI 7.0, we have been creating external definitions for each and every xsd separately, which is very time consuming, especially if we have many external definitions for upload.

As we all know that Process Integration 7.1 has been known for bringing many most awaited features in it, one of them is “Mass Import for External Definition”

In this blog, we will be seeing how this new feature has reduced our work in dealing with the multiple external definitions in ESR in a smarter way. 


<u>A Case in Point</u><u>* :*</u>

I am a big fan of explanation via “example”. Someone has well said that “An example is worth thousand words”. So, let’s not wait anymore.Lets start with a simple example


In the example, I have three XSDs; Company, Person and Product.

The Company.xsd is the main XSD and it contains two referenced XSDs, Person.xsd and Product.xsd as shown below :


</p>h3. Company.xsd


</p>h3. Product.xsd


</p>h3. Person.xsd



h3. <u>Implementation Steps to import the schemas in one shot : </u>

To leverage the use of “Mass Import” facility of ED, you can choose either :

1. Tools–> Import External Definitions(Figure1)

<u> Figure:1</u>



2. Right Click on the Ext Definition and Select “Import  External Definitions”(Figure 2)

 <u> Figure:2</u>




 Once you select the “<u>Import External Definition</u>s”, a Wizard will appear as shown below(Figure 3) :

<u> Figure:3</u>



Click on “Continue”.

<u> Figure:4</u>



 In the above screen(Figure 4), you have to select the Namespace and SCV where you want to import  the external definitions. If you have used the second method to come to the Wizard, the Namespace and SCV would be automatically filled.


Select “Continue”


<u> Figure:5</u>



 In this step(Figure:5), you can decide whether you want to import the referenced XSDs/WSDLs or not. In our scenario, we do care about the referenced XSDs, so, I have checked the “Import ReferencesAlso” option.





Select the XSD files you want to import from your local directory.

To check the smartness of the Wizard 🙂 , lets assume* *we only know that Company.xsd is the main XSD and we dont know the names of the referenced XSDs, so I can just select the Company.xsd file. and then click “Continue”.

What do you think it would do??






Well………. The Wizard definitely has smartness :). It did find by itself that Person.xsd and Product.xsd are the referenced XSDs for Company.xsd. The wizard
determines the referenced files using the schemaLocation attribute.

Note that the
wizard can only determine the referenced file if the reference to a file is in
the local file system.

The Wizard also gives an option to edit the External Definition Names.



<u> Figure:8</u>



Thats it, we imported all 3 XSDs 🙂 Was’t it a <u>S</u>weeter, <u>S</u>horter and Smarter way?

Here are the three External definitions created by the Wizard- one main (Company) and two referenced (Person and Product).( Figure 9)


<u> Figure:9</u>




You can find the refernced XSDs under the <u>External reference tab  </u>of Customer External Definition as shown below:

 <u> Figure:10</u>





Under the <u>Message Tab</u> of your ED, you can check out the message structure for the External Definition.  Here, in our example for the Customer External Definition, you can see the fields which are defined in the Person.xsd and Product.xsd.


<u> Figure:11</u>



<u>Conclusion :</u>

The new

M*** Import for External Definitions feature of PI 7.1 not only helps in handling the mass import of External definitions but also provides a smart way to figure out the referenced XSDs and WSDLs.


h3. Related Link :

Our 🙂  +




To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply