The Leadtools.Ccow.Server implements a context management server. The server creates an ActiveX specific implementation of a context manager.

Using the LEADTOOLS CCOW Context Manager

The LEADTOOLS CCOW Context Manager is a COM local server. Each request for a context management interface will return the same instance of the context management interface. As a result, only one copy of the LEADTOOLS CCOW Context Manager application will ever be running.

Local Server Registration

The context manager will have to be registered on the user’s machines before it can be used in a context management system.

• To register the context manager launch the Leadtool.Ccow.Server with the register command option:
  

  directory\Leadtools.Ccow.Server /register

• To unregister the context manager launch the Leadtool.Ccow.Server with the register command option:
  

  directory\Leadtools.Ccow.Server /unregister

The server can be started in two ways:

1. The context manager executable will be automatically started when an application requests that a COM object be created with “CCOW.ContextManager” progid. If the application is created in this way it will automatically close when the last reference is a context manager is closed.
2. Clicking on the application icon. If the application is started this way it will not go away when the last reference is closed. It will be up to the user to close the application by right clicking on its tray icon ( ).

Configuring the LEADTOOLS CCOW Context Manager

To configure the LEADTOOLS CCOW Server right-click the tray icon and click Configuration. The Configuration menu choice will bring up the following dialog:

The Configuration dialog has the following tabs for configuration:

• Applications - Associate applications with the context manager. In order to join the common context an application will have to be registered with the context manager.
• Subjects – List the subjects that the context manager supports. At installation the following subjects are supported: User, Patient, Encounter, Observation, DICOMStudyComponent, DICOMSeries, DICOMInstance and DICOMStudy

• Advanced - Controls advanced settings for the context manager.

Context Manger Configuration Application Tab

Commands:

1. Add - Add a new application to the Context Manager. The following information will need to be provided:
   1. Name - The name of the application. If you have multiple instances of an application use the "%" symbol to indicate that additional characters may come after the primary application name. For example, if Application% is specified, the following applications will be able to join the context: Application1, Application2, etc.
   2. Passcode - If the application will be setting secure subject they it will need a passcode. This passcode is used for passcode base authentication.
   3. Allowed - Check to allow the application to join the context.
2. Edit - Edit the selected application.
3. Delete - Delete the selected application. The application will no longer be able to join the context.
4. Allow All - Allow all the applications to join the context.
5. Allow None - Do not allow any of the applications to join the context.

Context Manger Configuration Subject Tab

Commands:

2. Add - Add a new subject to the context manager. The Add command button will open the following dialog:

   

   Options:
   1. Name - The name of the subject.
   2. Secure - Select if the subject is secure.
   3. Items - The subject item names.
   4. Dependent Subjects - Select the subjects that this subject is dependent on.
   5. Allowed Applications - If the subject is secure, select applications that are allowed to set the subject context data.
3. Edit - Edit the selected subject.
4. Delete - Delete the selected subject.

Context Manger Configuration Advanced Tab

Commands:

2. Apply - Applies the current settings

Options:

1. Max Participants - The maximum number of participants allowed to connect to the context manager. To specify no limit set the value to -1 .
2. Transaction Timeout - The maximum amount of time to wait for a context transaction to complete.
3. Action Timeout - The maximum amount of time to wait for an action to time out.
4. Notification Timeout - The maximum amount of time to wait for a response from a participant that has been notified of a context change.
5. Notification Retry Interval - The amount of time to wait before retrying to notify an unresponsive participant of a context change.
6. Ping Notification Timeout - The maximum amount of time to wait for a response to a ping request.
7. Ping Interval - The amount of time to wait before attempting to ping context participants. If an application fails to respond to a ping request, it will be removed from the context manager.
8. Ping Participants - Select to instruct the context manager to ping the participants using the Ping Interval.

 

 

---

Products | Support | Contact Us | Copyright Notices

© 2006-2011 All Rights Reserved. LEAD Technologies, Inc.