Setting Up Schemas in the
File System
You create the directory structure and save the schemas appropriately. These schemas can be used to validate the structure of a PI message payload.
· You have created the RFC destination for AI_VALIDATION_JCOSERVER on AS ABAP and AS Java.
More information:
Creating RFC
Destinations on AS ABAP and AS Java
· You have the appropriate permissions to access and modify the directory structure for XML validation.
· You must have access to the schemas that are referenced by using the import namespace tag in the main schema.
...
1. For XML validation, you must save the required schemas from the Enterprise Services Repository in the file system by creating the following directory structure:
¡ For validation on the Integration Server, create the directory /validation/schema/<GUID of software component version to which Service Interface is assigned>/<Repository Namespace of Service Interface> under the directory <sysdir>/xi/runtime_server.
¡ For validation on the central and decentral Adapter Engine, create the directory /validation/schema/<GUID of software component version to which Service Interface is assigned>/<Repository Namespace of Service Interface>under the directory <sap installation directory>/<system id>/<instance number>/j2ee/cluster/server0 for a non clustered installation of AS Java.

● You can find the <GUID of software component version> in the Enterprise Services Repository on the Key tab page in object Software Component Version.
● For a clustered installation of the AS Java, create the above directory structure under their respective server node directories.
More information:
2. Convert the <Repository Namespace of Service Interface> to a valid folder name by replacing the following characters with ~:
/,\,:,*,?,",<,>,|,;,,,=,&,%,[,],#

If there are more than one special characters one after the other, replace them with a single ~. For example, A%&B becomes A~B. If there is a period at the end (.), then the system automatically deletes it.
3. Under the above directory structure, create the directory /<Service Interface>.
4. If the schema contains the targetNamespace attribute in the xsd definition, then proceed as follows:
a. Create the /<targetNamespace> directory under the above directory.

You can find the <targetNamespace> in the Enterprise Services Repository on the WSDL or XSD tab page.
b. Repeat step 2 to convert the <targetNamespace> to a valid folder name.
c. Export the schema and save it under the /<targetNamespace> directory.
More information:
Exporting Schemas from
the Enterprise Services Repository
5. If the targetNamespace attribute is not present in the schema, export the schema and save it under the /<Service Interface> directory.
More information:
Exporting Schemas from
the Enterprise Services Repository
6. If the main schema contains references to other schemas by using the import namespace tags, then proceed as follows:
a. Create the directory /<import namespace> for each of the referenced schemas, under the /<Service Interface> directory.

You can find the <import namespace> in the Enterprise Services Repository on the WSDL or XSD tab page.
b. Repeat step 2 to convert the <import namespace> to a valid folder name.
c. Export the schema (xsd file) pointed to by the <schemaLocation> attribute.
More information:
Exporting Schemas from
the Enterprise Services Repository
d. Enter the file name as the schema name pointed to by the <schemaLocation> attribute.
For example, if schemaLocation="http://www.w3.org/2001/xml.xsd", name the file as xml.xsd.
e. Save each of the referenced schema under their respective /<import namespace> directory.