autoimportXML walkthru

Post Reply
Stepan Karandin
Posts: 17
Joined: 24 Jul 2017, 11:41

Hi, folks

I'm going thru autoimportXML sequence. CentOS 7, Tomcat 7.0.69, Protégé 3.5, no RDMBS

Questions:
- how to make settings for protégé client raised by essential_import_utility(com.enterprise_architecture.essential.importutility.integration.ProtegeJarLoader)
- whats wrong with default settings for context of essential_import_utility?
- is protégé 3.5 and 3.4.8 are compatible over RMI?
- may be I made a stupid mistake somewhere?

The first one is XML file:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

<knowledge_base xmlns="http://protege.stanford.edu/xml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <simple_instance>
    <name>KB_041892_Class0</name>
    <type>Business_Process</type>
    <own_slot_value>
      <slot_reference>name</slot_reference>
      <value value_type="string">Business Process</value>
    </own_slot_value>
  </simple_instance>
</knowledge_base>
Second one is automated XML import activity at GUI. It has connection settings to the local Protege RMI

The third is:

Code: Select all

Nov 28 23:05:28 arch-repo server[6044]: Nov 28, 2017 11:05:28 PM edu.stanford.smi.protege.server.RemoteClientProject copyKb
Nov 28 23:05:28 arch-repo server[6044]: INFO: Loaded pprj file into knowledge base in 13669 milliseconds.
Nov 28 23:05:35 arch-repo server[6044]: Nov 28, 2017 11:05:35 PM com.enterprise_architecture.essential.importutility.integration.ProtegeIntegrationManager executeXMLImport
Nov 28 23:05:35 arch-repo server[6044]: INFO: Integration executed. Return code: 50
It suspicious

Code: Select all

[root@ea ~]# ls /usr/share/tomcat/
bin                   java15.log.lck  java22.log.lck  java2.log.lck   java6.log.lck
conf                  java16.log      java23.log      java30.log.lck  java7.log
[b]dup_import_script.py[/b]  java16.log.lck  java23.log.lck  java31.log.lck  java7.log.lck
java0.log             java17.log      java24.log      java32.log.lck  java8.log
java0.log.lck         java17.log.lck  java24.log.lck  java33.log.lck  java8.log.lck
java10.log            java18.log      java25.log      java34.log.lck  java9.log
java10.log.lck        java18.log.lck  java25.log.lck  java35.log.lck  java9.log.lck
java11.log            java19.log      java26.log      java36.log.lck  lib
java11.log.lck        java19.log.lck  java26.log.lck  java37.log.lck  logs
java12.log            java1.log       java27.log      java3.log       temp
java12.log.lck        java1.log.lck   java27.log.lck  java3.log.lck   update.info
java13.log            java20.log      java28.log      java4.log       webapps
java13.log.lck        java20.log.lck  java28.log.lck  java4.log.lck   work
java14.log            java21.log      java29.log      java5.log
java14.log.lck        java21.log.lck  java29.log.lck  java5.log.lck
java15.log            java22.log      java2.log       java6.log
Stepan Karandin
Posts: 17
Joined: 24 Jul 2017, 11:41

Some update

Code: Select all

Source information transformed successfully.
Created new instance of class: Business_Process

Failed to send snapshot to the Report Service
Stepan Karandin
Posts: 17
Joined: 24 Jul 2017, 11:41

SOLVED. Comments and answers will be appreciated =)

Two things done:
to notice that there wasn't python file at activity
to change dist/protégé.jar to the 3.5 from server
User avatar
jonathan.carter
Posts: 1087
Joined: 04 Feb 2009, 15:44

Hi Stepan,

Thanks very much for sharing your experience with one of the service interfaces of the Import Utility!

You can use the autoImportXML service with either a local repository within the Import Utility or with a server-based Protege repository. This is controlled in the same way as with other Import Activities.
It looks like you’ve got past that issue, though.

We’re about to release a new version of the open-source solution and in the Import Utility, this includes the Protege 3.5 engine, which can, as you’ve found cause version incompatibilities between Protege 3.4 and Protege 3.5.

In the new release, we include an example XML import activity which should help to demonstrate how to setup and use this capability.

The ’50’ error code is a script error, which suggests that the transform is creating an import script that has a bug or some unhandled data case. Examples could be type-mismatch (putting a String in an int slot, for example) or something more fundamental with the script that the transform is creating.

As you’ve said, this is most likely down to there being no import script specified as part of the request.

In open-source mode, there is a simple HTML form that is very helpful for testing the XML import.
You’ll find this at:

http://<YOUR IMPORT UTILITY SERVER>/serviceRequestXMLForm.html

A new feature that we’ve added recently is to have the XML import create an update file - a packaged-up Python script that you can download and then run separately. This is the way to use the import utility in Cloud-mode, for example, and it allows you to more easily debug the XML transform that you’ve defined.

Jonathan
Essential Project Team
Post Reply