About Service Groups

PASS uses specific services to communicate with your trip planning system to retrieve fixed route itinerary data.

Service groups are defined in the path\Config\localhost.profile file.

As an add-on to PASS, PASS-IPA expects that the following PASS service groups have been installed:

  • CoreServerManagement

  • CoreConfigurationManagement

  • CoreDataManagement

  • CoreUtility

  • CoreApplicationEngine

  • CoreMessaging

  • MAP_AddressMatching

  • MAP_Routing

  • Cmn_InstantMessenger

  • PASS_Pass

  • PASS_PassAgent

  • PASS_PassBookingValidation

  • PASS_PassEligibilityTests

  • PassCmn

In addition, the following service groups specific to PASS-IPA should have been installed:
  • INFO_InfoWeb

  • INFO_InfoPTP

The following service groups should not be activated (unless the associated applications have been installed on your system):
  • INFO_RealTimeManager
  • PASS_ParaCutter
  • PASS_TCC

About Service Shells for Multiple Databases

When setting up a two database solution, PASS users must be able to connect with a second service shell. The Primary service shell (used for Address Matcher) defined in Tools > System Properties, under Services cannot be used. This is because the service shell must connect to the FX/INFO database.

Service Shells should not be run from the same folder to minimize logging conflicts. They will, however, point to the same profile file.

The critical issue when setting up a two database solution is that PASS users must be able to connect with a second service shell. It can’t be the one defined in Tools/System Properties/Services because it has to be a service that connects to the INFO database. To manage this properly, you need to define and link two different service shells. This is done by defining a “server farm” in the profile file in the config folder. You need to add xml code similar to this:
<servers>
  <server id="INFO" defaultService="Hiwire" anonymousAccess="false">
	    <components>
		<group name="INFO_InfoPTP"/>
	    </components>
  </server>
</servers>
<computers>
   <computer name="localhost">
       <servers>
          <server id="Primary" address="localhost" port="4010"/>
	   <server id="INFO" address="localhost" port="4020"/>
       </servers>
    </computer>
</computers>