...

1. Navigate to Tools > Schema Repository (Online Schema Repository in Online Event Process Development perspective). This opens a Schema Repository editor using which schemas can be added to schema repository.
   To add schema files to the catalog, click Add to Catalog button
   
   
   Figure 1: Schema Repository

   Note
   In Online Event Process Development perspective, Schema Repository editor name appears appended with the server name, for example, Schema Repository for EnterpriseServer (as shown in the images used here), " EnterpriseServer" being the name of the active server.

2. To add schema files to the catalog, click Add button in the Schema Repository dialog box that pops-up and select any one of the following options:
   
   

   • Add File(s): Click this option and select the required schema file(s) from the browser window that appears.

     Tip
     Use CRTL/SHIFT to select multiple files.

   • Add Folder: Click this option and select the required folder containing multiple schemas from the browser window.
      

   
   Figure 2: Adding XML files to Catalog

   Under Details section, it shows details of the particular file selected:

   • The namespace URI and Location.

   • Save to the Catalog folder: If this option is enabled, schema files will be saved in <FIORANO_HOME>/xml-catalog/user folder. If it is disabled, the absolute path of the files' original location will be used to refer the schema. File location in catalog can be modified. Ensure to click Save button after enabling/disabling this option / changing file location.
     

   • Note
     If an entry has empty URI string or if two or more entries have the same URI, such entries will be shown in red font and an error message describing the problem with the entry will be shown in its Details. If schema is invalid, OK button will be inactive, hence remove the inavlid schema to add the remaining files or fix the issue with the invalid schema and add again.

   • Save to the Catalog folder: If this option is enabled, schema files will be saved in the xml-catalogs folder.
     
     

     Tip

     Separate xml-catalogs are maintained for Offline, Online and Mapper perspectives. Perpspective xml-catalog path Offline %FIORANO_HOME%/runtimedata/eStudio/workspace/.repositories/Offline/xml-catalog/user Online %FIORANO_HOME%\runtimedata\workspace\.repositories\ Online\1392242684378756868\xml-catalog\user Mapper <FIORANO_HOME>/xml-catalog/user When perspective switch is done, the respective xml-catalog of the perspective will be referred and Schema Repository tool displays the schemas in the current perspective's xml-catalog.  If it is disabled, the absolute path of the files' original location will be used to refer the schema. File location in catalog can be modified. Ensure to click Save button after enabling/disabling this option / changing file location.

   
   Figure 3: Adding schema to Schema Repository
   
   

   Note
   Schema files which are not saved in the catalog folder (Save to Catalog folder option disabled) will be referred by their absolute paths; refer location of Entry 3 in the figure below. If a folder is added, relative paths will be used to refer them in the catalog; refer entry 1 and 4. Figure 4: Table displaying the schema files added to catalog

3. Click OK to add schemas to the repository; added schemas get listed in the schema repository.
   
   
   Figure 5: Schema Repository with schema files added
   
   

   Info
   Search option in the dialog box helps to filter the added schemas using keywords (case sensitive) in the URI/Location. It helps to trace a specific schema when there are many in the Schema Repository list.

Separate xml-catalogs are maintained for Offline, Online and Mapper perspectives.

...

Schema Repository

...

in

...

Schema Repository in Online Perspective

Fiorano Enterprise server maintains its own schema repository in %FIORANO_HOME%/runtimedata/repository/Schemas.

...

Suppose if EP1 is not opened in eStudio2 ? , this Event Process is not fetched in eStudio2. In this case if a new Event Process EP2 is created in eStudio2 having schema reference schema1 (since the Event Process is not fetched in eStudio2, it is unware that schema1 is used in EP1) and when EP2 is deployed to the Server, it renames schema1 to some other name and updates EP2 to avoid conflicts. When this case happens eStudio2 complains that the new schema file is missing as EP2 is updated when deployed to the server.

...

Figure 8: Offline Schema Delete Warning

xml-catalogs