Daily Lab / POC Activities

caBIG

• Requested lab team to install Oracle on one Linux VM
• Tom & caBig team created preliminary data model to test
• Set up meeting with Austin Kreisler (HL7 / Data Modeler) to verify test data model
• Set up meeting the caBig team to review EA data model
• Set up meeting with caBIG vocabulary team to validate data model against caBig vocabulary

Globus

• Globus install complete
• Next step: connect to HealthGrid security domain, then build other nodes

Daily Lab / POC Activities

Extramural

• Error in attempt to copy SUSE install disks to hard drive (/home/labuser/SUSE). VM locked up after second disk copy. Deleted Disk01 and abandoned attempt
• Internet access in VM not working. Informed IT team

Presentation from caBIG

Click here for presentation notes

Key points:
Make sure to use SDK vs. 3.2.1
For the DB – make sure to select either Oracle or mySQL

Essentially the steps include creating a domain model/object model
Then creating the data model (make sure to drag from foreign to primary to build connections)
Then map those two models together using a tool called caAdapter
In order to prep for seed after you need to export your models into XMI
The key is to make sure that you export at the highest level of the logical view
And make sure that you only have one check box marked in the upper right hand section
Once you run caAdapter, it will modify your XMI file
And then export it to then run the caCORE SDK
The caCORE SDK will generate the web front end to your data service


There are other steps to gridify this data service however there not required for this proof of concept

Conceptually, if everything above was step one, steps 2, 3 and 4 – involve the “semantic integration workbench” the UML Loader (this step registers the xmi with the caDSR), and the caCORE SDK.

A tool called “introduce” can gridify the application

You can access the SDK 3.2.1 presentation from following link.
SDK 3.2.1 Presentation: https://gforge.nci.nih.gov/docman/view.php/196/5994/SDK%20-%20Bootcamp.ppt

The caAdapter tool that had mentioned earlier as being the webtool is actually a standalone application for version compatible with SDK 3.2.1. Their web version should get released in two to three weeks. You can download their standalone version from http://ncicb.nci.nih.gov/download/caadapterlicenseagreement.jsp

Tom

Daily Lab / POC Activities

caBIG

• Talked to Scott Halpine & team at Software Consultants about next steps
• His team and I have played with EA tool
• His team will set up conference call this week with NCBI folks to help build UML model for PoC
• Essentially, we need to understand which EVS attributes to use in model creation
• Scheduled Enterprise Architect tool demonstration to go over the creation of our UML model [See next post]
• Successfully loaded production version of EA tool with key (no longer under 30-day trial period)
  

Contact Information
Scott A. Halpine
Software Consultants, Inc.
4601 Presidents Drive, Suite 250
Lanham, MD, 20706
Tel: 301-306-5104
Fax: 240-260-0197
Cell: 301-996-3077

Raghu Narasimha ( 301-306-5103 (O)) & 240-355-4799 (C)) provided the following links for reference:

Here’s that link to NCI EVS – caCore 3.2 sequence diagrams and logical view.

This second link downloads an EA format.

This third link downloads another caCore component.

Click here for UML Example

Daily Lab / POC Activities

Continuation of prerequisite software installation for Globus

• Began to install Ant
• Ant installation failed because C compiler and associated dependencies were not installed in original SUSE install
• Had initial difficulty installing C compiler, etc.
• Figured out how to install software from CDs
• Completed compiler installation
• Plan to copy all 4 SUSE installation disks onto hard drive for future potential software needs

Daily Lab / POC Activities

Further setup of Globus environment
Prior to installation

• Discussed installation pathway with Nigel at Argonne
• Successfully installed jdk1.5.0.14
• Downloaded apache-ant-1.6.5 and dpkg-1.14.7
• Globus build can take up to 4 hours; if longer then something is wrong

Update to older blog item - with link to pdf document

Put up link to excellent Data Grid Taxonomy manuscript - in older blog item here.

Daily Lab / POC Activities

At AMIA in Chicago last week Jonathan Silverstein, president of HealthGrid. US Alliance, recommended that we tap Nigel Rarsad nmp@uchicago.edu. Nigel is a few weeks ahead of us in setting up Globus and may be a good technical resource going forward.

Ken email Nigel this morning.

This afternoon, spoke to Nigel via mobile phone (773) 524-1681.

Recommended installing Java 1.5.14 and Ant 1.6.5 into /usr/local directory on SUSE and all should go well. Also recommended using quickstart document.

Interesting Sites/Books/Concepts/Etc

• Developing Multi-Agent Systems with JADE (Wiley Series in Agent Technology) (Hardcover)

X.509 Certificate & Grid

By Stephan Erberich

X.509 do not use IP information. The cryptographic key of the certificate authenticates the sender being part of the same security domain. That's why you can logon to your bank account from any computer because it uses single sign on via ssl and cert creation bases on your username/passwd.

In your case healthgrid security domain will issue you an end entityX.509 certificate which you can deposit in a cert bank, the myproxy service (also on healthgrid). Then you can checkout proxy certificates of limited lifetime (e.g. tokens) to authenticate yourself or a MEDICUS services to access the healthgrid resources.

One more word on this: Authentication is not equal authorization. Thus knowing that a service request comes from "Ken Hall", does not mean that you will gain access to all services. This will depend on your role in the Grid. Actually roles becoming obsolete with SAML assertions which use attributes instead of roles.

Now what you need in order to provide services on a server is a host certificate which allow the host to validate the authenticity of the user cert presented to services running on the host. These certificates use the FQHN as distinguished name (DN) in the certificate. Thus a host cert is not bound to an IP address, but to DNS FQHN.

Hope this untangled the matter a bit.