IMPAX 6.5.1 Server Knowledge Base home > Configuring IMPAX Server with Administration Tools > Configuring support for multiple IMPAX clusters

Configuring an IMPAX spoke for Change Context (cc) object synchronization

Important!

Important!

This topic applies only when the IMPAX site archives to an IMPAX Data Center.

Change Context (cc) objects are a mechanism for managing attribute (such as patient name) or structural (such as split or merge) changes made to a study at an IMPAX spoke after it has been archived at Data Center. The cc objects summarize the nature of the change. They are sent to Data Center and stored with the original study (which, having been archived, cannot be changed). If that study is requested by an IMPAX spoke later on, the change indicated by the cc object is applied.

Since the creation of cc objects is disabled by default, some configuration must be done at the IMPAX site to enable their use.

Setting IMPAX database triggers

First you must set up the database triggers required to create cc objects when study changes occur. The procedure is slightly different for Oracle and for SQL Server database systems.

To trigger cc object creation on an IMPAX Oracle database

  1. Using a tool such as SQL*Plus or TOAD, log in as the user mvf or dbadmin.

  2. Type

    EXEC ENABLE_CONTEXT ()

  3. Ensure that the result is

    PL/SQL procedure successfully completed.

To trigger cc object creation on an IMPAX SQL Server database

  1. In SQL Server, using a tool such as OSQL or Query Analyzer, log in as the user mvf or sa.

  2. Type

    EXEC ENABLE_CONTEXT

  3. Ensure that the result is

      (1 row(s) affected)
      (13 row(s) affected)
      (13 row(s) affected)

    Row numbers could vary.

After triggering the creation of cc objects, every time a supported attribute is changed (for example, through a RIS update, the Administration Tools, or CLUI), cc objects are potentially transmitted to IMPAX, and the CHANGE_CONTEXT and CHANGE_CONTEXT_DETAIL records in the mvf database tables are updated with the change.

Specifying the SCU queue for notify jobs

If there is more than one SCU queue in the cluster, specify the correct queue for the Task Scheduler to run notify jobs on.

To specify the SCU queue for notify jobs

  1. Launch CLUI.

  2. To determine the current settings, type

    select * from MVF_TS_MODULE_CONFIG where attribute='SCU_NOTIFY_QUEUE_REF'

  3. To configure the SCU queue value, type

    update MVF_TS_MODULE_CONFIG set value='scu_queue_ref' where attribute='SCU_NOTIFY_QUEUE_REF' and ae_ref='ae_ref'

    where ae_ref is the ae_ref that owns the image cache and scu_queue_ref is its SCU queue_ref.

  4. After the changes are made, restart MVF Task Scheduler.

Completing other configurations in IMPAX for IMPAX Data Center

You must complete a series of other configuration changes to get full cc object support between an IMPAX spoke and IMPAX Data Center.

To complete other configurations in IMPAX for IMPAX Data Center

  1. Launch CLUI.

  2. To synchronize cc objects with the IMPAX Data Center, enable database linking by typing

    UPDATE dosr_database_link set database_link = 'T', synchronize_changes = 'T' WHERE ae_ref = IMPAX_Data_Center_ae_ref

  3. Open the dosr_database_link table and check that the changes were made.

  4. To ensure that all incoming sources are configured to archive, in CLUI, type

    UPDATE dosr_station SET archive_flag = 'T'

    This assumes that the site wants all images to be archived to the Data Center.

  5. To refresh cached data including entries in the dosr_database_link table, in CLUI, type

    flush_mem_caches

  6. To be able to query and retrieve from the IMPAX Data Center, add the IMPAX Application Server into the IMPAX Data Center AE network page. As the entry values, use the correct AE title and host name and port 104.

Required permissions


See also


Topic number: 49692

Applies to: IMPAX 6.5.1 Server Knowledge Base