Hi,

I'm looking for some advice on options and how best to distribute XML protocols on AEP.

We are finalising the build of our software which uses PipelinePilot and ChemistryDirect to carry out processing behind the scenes. The system is installed on a clients site (CUSTOMER) instance, using a Runtime licence for the AEP server. Customers won't have access to the system via the PP Client, only a webport or APIs we provide.

We only ever have to worry about our system & protocols, as nothing else will run on the server (so its not a Collection in the wider sense of the word on a general use AEP instance).

Our clients will receive a weekly data updates into the Direct database from our central (MASTER) database using Pipeline pilot scheduled jobs.

We would also like to use a similar process to update any protocols and dependencies files on the CUSTOMER instance from our MASTER instance or AEP. Ideally this would be an automatic process without requiring an admin to do anything on the server.

I've read the "INTEGRATION COLLECTION - Application Packaging Guide" and this provides one possible method (the Accelrys preferred) e.g.

-We could create a package file, upload it into our database

-A scheduled job downloads the package on the customer server, extracts it to the apps folder and then executes the pkgutil -i command to install it.

Does anyone know if the pkgutil -i command be executed from within pipeline pilot (I'm assume the component "Run Program (on Server)" or "Run Command (SSH)" would do the job)?

However I'm wondering if the alternative method below would work (and would be easier to admin).

-We upload the latest version of the xml.gz protocol files directly into our central Oracle MASTER database that contains the data.

-A scheduled job on the customers server then downloads the xml.qz protocols and copies them directly in the relevant XMLDB folder. The original file isn't overwritten as it’s a new version e.g.

OpenCCguides.31.xml.gz is added to the XMLDB folder where the current version is OpenCCguides.25.xml.gz

As the customers PP server can/should only ever run protocols created on our system the protocol names and GUIDs should stay the same between our MASTER system and the CUSTOMER protocols, so protocols referencing each other (which many do) should still find the relevant copies.

This would prevent the need to create and deploy packages.

Would this work? What would happen if 2 different protocols ended up with the same GUID?

I did try a mock up of this type of transfer, but the PP client didn’t pick up the new protocol version, so I assume something has to be triggered for the XMLDB to be updated that a new version is on the server.

Any ideas what that is and how it can be triggered?

Any other advice or thoughts?

Thanks

Joe