English

How To: Create unique user connection names from ArcIMS to ArcSDE

Summary

Instructions provided describe how to create unique user connection names from ArcIMS to ArcSDE.

Procedure

Select an option below.

  • When using the sdemon -o info -I users command to see the number and type of connections, if the same user is used in all ArcIMS AXL files a list appears for that username.

    Code:
    sdemon -o info -I users -i esri_sdeORA

    ArcSDE Instance esri_sdeORA Registered Server Tasks on zephyr at Fri Mar 11 15:5
    8:43 2005
    -------------------------------------------------------------------------
    S-ID User Host:OS Started
    ----- -------- -------------------------------- ------------------------
    3096 LOADER zephyr:Win32 Fri Mar 11 12:32:38 2005
    3097 LOADER zephyr:Win32 Fri Mar 11 12:32:39 2005
    3098 LOADER zephyr:Win32 Fri Mar 11 12:32:39 2005
    3090 LOADER zephyr:Win32 Fri Mar 11 12:01:46 2005

    When serving ArcSDE data through an ArcIMS MapService, the number of gsrvr processes spawned on the ArcSDE Server equal the number of instances assigned to the Virtual Servers responsible for processing requests to the MapService.

    Multiple MapServices assigned to the same Virtual Server do not spawn additional gsrvr processes. If the MapService's map configuration file points to two different users within an ArcSDE instance, then the number of gsrvr processes spawned doubles.

    In order to distinguish which connection belongs to which AXL file, create separate user names in ArcSDE and use different usernames in the SDEWORKSPACE tag of each AXL.

    The example shows connections for 2 AXL files served as image services, with 2 separate users: LOADER & MANVEEN specified in SDEWORKSPACE:

    Code:
    sdemon -o info -I users -i esri_sdeORA

    ArcSDE Instance esri_sdeORA Registered Server Tasks on zephyr at Fri Mar 11 16
    3:14 2005
    -------------------------------------------------------------------------
    S-ID User Host:OS Started
    ----- -------- -------------------------------- ------------------------
    3096 LOADER zephyr:Win32 Fri Mar 11 12:32:38 2005
    3102 MANVEEN zephyr:Win32 Fri Mar 11 16:02:44 2005
    3097 LOADER zephyr:Win32 Fri Mar 11 12:32:39 2005
    3101 MANVEEN zephyr:Win32 Fri Mar 11 16:02:43 2005
    3103 MANVEEN zephyr:Win32 Fri Mar 11 16:02:45 2005
    3098 LOADER zephyr:Win32 Fri Mar 11 12:32:39 2005
    3090 LOADER zephyr:Win32 Fri Mar 11 12:01:46 2005
    3104 MANVEEN zephyr:Win32 Fri Mar 11 16:02:45 2005

  • Another option would be to query the SDE.PROCESS_INFORMATION table to check the PID's