TOGAF diagram and Automated Script

[schurms]

Hi.  We have created a C## batch script which runs each night to publish all packages within a TOGAF database to a html website.  Eg publishing all our business process packages.

Problem - When we run the script the models are all successfully exported however the root TOGAF circle diagram is incorrectly rendered.  (Eg it is displayed as square boxes and not the circles under TOGAF.)  Now the script is run on a PC with a version of EA which has a TOGAF License Key applied.

When the diagram is manually opened, the TOGAF diagram displays correctly. Further when a manual html publish is started from within EA the diagram correctly renders. (Again because the version of EA uses a TOGAF License key.)

The incorrectly rendered TOGAF diagram is displayed as it would be if you open up a version of EA that does not have a TOGAF License key applied.  So the Automated script is running as if there is no TOGAF license Key.

Question:  We have a TOGAF license key.  How can we run a batch script on EA and let it use the TOGAF License key, to correctly render the TOGAF model.  I can not find a parameter to specify a specific Licence Key to use when opening the repository.  (As stated earlier, we are running this on a PC which has a version of EA which is using a TOGAF License Key.)

Any thoughts?

[Eve]

The problem is that when started via automation EA doesn't load add-ins. Something that could potentially be changed, but not something that I'd change without some serious investigation.

What you may be able to do is use Process.Start to create a process. The Process object has a process id, and from there it will be possible to connect to that instance of EA. (Sorry but I'm not a C# programmer and I don't have specifics on hand)

[schurms]

Thanks for the prompt reply.

I will implement a workaround as it is really only one image.  (E.g keep a copy of the Togaf image, created from a manual publish, in a separate directory and replace it as a last step.)

[Stoppy]

Is the TOGAF Key and other Keys stored in the same location, ie. could the automation be picking up the non TOGAF key as a default?

Your Apprentice

Stoppy

[schurms]

Stoppy,

As Simon M communicated, the TOGAF extension is actually an add-in to EA which requires the correct key to enable the add-in functionality at run-time.  

The problem is not specifically license key related, but related to  enabling the TOGAF add-in when calling EA via the automation EA.

You get the same results if you enable and disable the TOGAF add-in from within EA directly, whilst still using a TOGAF authorised license key.  So it is all about enabling the TOGAF add-in.

But good suggestion.