Evaluation

The installation of the Enterprise Hub is divided into three separate downloads for the Hub Server, the client addin and the workflow designer for the different roles that are performed

·        EA.Gen.Hub
This standard installer creates the windows service on the host that executes the replication, filtering and triggers in the background on a server.  For evaluation purposes this can be any 64-bit Windows workstation that you have development access to.  We recommend 16gb of memory and four cores to use the FastLoad jobs for initial load

·        EA.Gen.Hub.Addin
This standard installer will need to be installed on any workstation where read-time replication is desirable.
 

These are all accessible from the download menu of the site, and will redirect to the login page if there is not currently an active user sessions.

Select register option and enter your email and a password to use when returning.  After you’ve confirmed your address, all downloads will be available

Installation

When you click on the download option, and zip file will be downloaded including the MSI installer and a licence description for the software.  Running the EA.Gen.Hub installer will create and start a Windows service using the default System account (you’ll only need to change this if you wish to using SQL/Server integrated security or access EAP files from a network file-server.

The software will be installed in the "C:\Program Files\Cepheis\EA.Gen.Hub\Server" directory.  This directory also includes AccessDatabaseEngine_X64.exe to install the database driver compatible with Sparx EAP/EAPX files that will be need to replicate content native Sparx files.  We recommend using Microsoft SQL Server Express for the evaluation process because it is free, and capable of supporting the size of database that you’ll need for the evaluation.

Select Evaluation

Any EAP file models and server databases can be used for the evaluation,  but only server databases (MS SQL/Server, Oracle MariaDB(MySQL)) can participate in the real-time replication because the Enterprise Hub Service needs to be able to open a connection remotely.

The Sparx EAExample.eap repository is a good example as is the reverse-engineer of the entire CLR (.net) and Java JDK, but you should also include a number of your own repositories from different domains. 

Setup

 Repositories are registered with the Enterprise Hub by

1. Adding database connections in the <connectionStrings> section of the EA.Gen.Hub.exe.config file e.g. 
   
   <add name="EAExample" connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\EA\EAExample.eap" providerName="JetEntityFrameworkProvider" />
   <add name="ER" connectionString="Data Source=localhost;Initial Catalog=EnterpriseRepository;Integrated Security=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
   <add name="AR" connectionString="Data Source=localhost;Initial Catalog=ApprovedRepository;Integrated Security=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
   <add name="IR" connectionString="Data Source=localhost;Initial Catalog=ImplementdRepository;Integrated Security=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
   <add name="MI" connectionString="Data Source=localhost;Initial Catalog=ManagementRepo;User id=svc_hub;Password=**********;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
   <add name="BA" connectionString="Data Source=localhost;Initial Catalog=BusinessArchitecture;User id=svc_hub;Password=**********;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
   <add name="DA" connectionString="Data Source=localhost;Initial Catalog=DataArchitecture;User id=svc_hub;Password=**********;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
   <add name="TA" connectionString="Data Source=localhost;Initial Catalog=TechnologyArchitecture;User id=svc_hub;Password=**********;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />  
   
   
2. Adding connection references to the <connections> section of the Enterprise Hub section e.g.
   
   <connections>
         <connection name="ER">
           <routes>
             <route to="AR" master="true" status="Approved" />
             <route to="IR" master="true" status="Implemented" />
             <route to="BA"
                         master="true"
                         type="Event,
                                    Decision,
                                    Activity,
                                    Process,
                                    Business Process,
                                    Object,
                                    Actor,
                                    Analysis,
                                    ArchiMate_BusinessActor,
                                    ArchiMate_BusinessFunction,
                                    ArchiMate_BusinessObject,
                                    ArchiMate_BusinessProcess,
                                    ArchiMate_BusinessRole,
                                    ArchiMate_BusinessService" />
             <route to="MI"
                         master="true"
                         type="Requirement,
                                    Issue,
                                    Change,
                                    ArchiMate_Deliverable,
                                    ArchiMate_Driver,
                                    ArchiMate_Gap,
                                    ArchiMate_Goal,
                                    ArchiMate_Requirement,
                                    ArchiMate_Stakeholder,
                                    ArchiMate_Value,
                                    ArchiMate_Assessment" />
             <route to="DA"
                         master="true"
                         type="table,
                                    View,
                                    Procedure,
                                    Function,
                                    Trigger,
                                    Database,
                                    database connection,
                                    Logical" />
             <route to="TA"
                         master="true"
                         type="ArchiMate_SystemSoftware,
                                    ArchiMate_TechnologyService,
                                    ArchiMate_Device,
                                    Node,
                                    Component" />
           </routes>
         </connection>
         <connection name="AR">
           <triggers>
             <trigger class="EA.Gen.Hub.Workflow.WorkflowJob"
                            assembly="EA.Gen.Hub.Workflow"
                            workflow="ChangeStatus.xaml"
                            description="change the status of dependant changes" elementClass="Element">
             </trigger>
           </triggers>
         </connection>
         <connection name="IR">
           <triggers>
             <trigger class="EA.Gen.Hub.Workflow.WorkflowJob" assembly="EA.Gen.Hub.Workflow" workflow="ChangeStatus.xaml" description="change the status of dependant changes" elementClass="Element">
             </trigger>
           </triggers>
         </connection>
         <connection name="MI" />
         <connection name="BA" />
         <connection name="DA" />
         <connection name="TA" />
         <connection name="EAExample">
           <routes>
             <route to="ER" master="true" />
           </routes>
         </connection>
       </connections>
   
   
3. Select the Jobs that you wish to schedule  in the background for initial load and catchup when realtime-replication is not possible.  The FastLoad option should only be used if the test computer has sufficient memory to hold the entire source model in memory during initial load

Review

The EA.Gen.Hub service can be stopped and restarted with the commands "sc stop EA.Gen.Hub" and "sc start EA.Gen.Hub" (or via Component Services in the Control Panel), but can also be run from the command line for realtime progress logging without the need to monitor the Windows Event-Log or the log-file.  The command prompt is preferable for the evaluation because it will enable you to quickly resolve any access issues.

Please forward any feedback to feedback@cepheis.com