OPERA Electronic Distribution Suite (OEDS) > Installing OPERA Electronic Distribution Suite (OEDS) > Available Windows Services for OEDS
Available Windows Services for OEDS
The following Windows Services may be available, depending on the functionality installed as part of a new OEDS installation or an
upgrade:
GWIZ (AVSTAT)
The AVH service creates and sends restriction messages with the purpose of maintaining the hotel database at the four GDS hosts. This
allows for business continuity in case of a loss of connectivity between the GDS host and the OPERA database.
GWIZ (Lanyon Rate Bridge)
This service formats an XML message with data extracted from the OPERA database. The service then posts the message to a predefined
URL where the Lanyon Rate Publisher® program processes and forwards the message to the GDS hosts.
The Lanyon Rate Bridge XML message generated contains required data elements to update a rate at a GDS host, including the Rate
Category and Rate Level fields. The purpose of sending the rate category is to send the correct single character code that will be used by a
travel agent to request availability for that specific category of rates.
GWIZ (OAP) Type A Pegasus Server
This service receives TypeA messages from Pegasus and converts the messages into a language that is understood by OAP. This service
also serializes data from OAP and sends response messages back to Pegasus.
GWIZ (OAP) Type B Pegasus Server
This service receives TypeB messages from Pegasus and converts the messages into a language that is understood by OAP. This service
also serializes data from OAP and sends response messages back to Pegasus.
GWIZ (OAP) Type B Reservation Service
This service fetches TypeB booking messages from the TypeB In queue and passes this data to the OPERA Access Point Reservation
service. This service also retrieves data from the OAP Reservation service and passes it into either the TypeB failed reservation queue or
the TypeB out queue.
GWIZ (ONREQUEST)
This service is only used when the hotel sells bookings via GDS for rates that have the “On Request” restriction set. It allows TypeB
bookings to be inserted with a "Waitlist" status in OPERA for those specific rate codes.
GWIZ Business Event Processor
This service manipulates data for automated restriction and rate update messaging. Multiple copies of the GWIZ Business Event service
can be installed on different OEDS servers to provide a fail-over capability to continuous processing of channel Business Events. What this
means is that the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are
started on. After starting all of the required services on one machine, start all of the required services on the second machine. The first
machine processes the business events until there is an issue. When an issue is detected, the second machine will begin to deque the
business events.
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
GWIZ Pegasus Rate Update Service
This service generates rate updates and creates files for Pegasus to distribute to the four GDS hosts. Through configuration, this service
will upload the files that are produced on a 60-minute interval to a pre-determined location on an FTP server. Using rate updates, hotels
can maintain the databases at the GDSs to serve as backup for business continuity. This service requires that the Switch Company and
the hotel have established an agreement to use the specified rate update method.
GWIZ Rate Update Service
This service processes data after the GWIZ Business Event Processor has fetched data required to build Rate Update messages. This
service is configurable to send out messages at an interval that is adjustable according to client's needs.
GWIZ Session Purge
This service runs at pre-determined intervals and performs an also pre-determined action on bookings that have been in session for the
time period specified in the time interval.
ADS ARI Resend
This service wakes up at specific intervals. For each message sent to the ADS partner (Rate, Availability, Booking Limit, etc.), the ADS
partner responds with an ACK, NACK, or NOACK immediately. If the message is processed, the ADS partner responds with an error or
success message. The ADS Resend Service reprocesses and resends messages if the ADS partner responds to the original message with
certain error codes (4201, 4000, 5000, 6000), or after receiving an ACK from Expedia with no associated error or success message.
Cookie Preferences | Ad Choices
ADS ARI Retry
This service wakes up at specific intervals. For each message sent to the ADS host (Rate, Availability, Booking Limit, etc.), the host
responds with an ACK, NACK, or NOACK immediately. If the message is processed, the ADS host responds with an error or success
message. The ARI Retry service retries to send messages to the ADS host if the host responds to the original message with certain error
codes (4201, 4000, 5000, 6000), or after receiving an ACK from the host with no associated error or success message.
ADS Avh Bridge
This service reads restriction data generated by OPERA. It formats and sends the message to its destination at the ADS host.
ADS Booking Limit
This service sends inventory status messages. It is a Windows .NET Service that wakes up specific interval (specified in the configuration
file; generally every 6 hours) and prepares booking notification messages. The booking notification is sent for all properties setup for an
ADS channel in Channel Management, where the ARI Enabled check box is selected.
ADS Hurdle Processor
This service reads the hurdle data from the "ads_hurdle_queue" table and checks if the rate is closed due to restriction. If the rate is
closed, it will insert the restriction as "CLOSE" for that rate-room combination in the gds_avail_upd_message table. If the rate code is not
closed due to the hurdle, the service will check if there are other restrictions and will insert a record in the gds_avail_upd_message table
with the appropriate restriction or OPEN status as "PENDING."
ADS Ping
This service allows for communication between OPERA and an ADS partner, and it is constantly monitored. The ADS partner sends
inbound Pings, while OPERA sends outbound Pings. These pings are based on the OTA specifications, which allow for third party travel
partners to communicate with each other. If a disruption occurs on either side, notifications are sent out to the client via e-mail and logged
locally in order to troubleshoot the issue.
OEDS BE Processer For EQC
This service processes business events for Expedia Quick Connect (EQC). A fail-over configuration can be implemented for this service.
What this means is that the service can now be started in the same enterprise without a detrimental effect on the servers or databases
they are started on. After starting all of the required services on one machine, start all of the required services on the second machine.
The first machine processes the business events until there is an issue. When an issue is detected, the second machine will begin to
deque the business events.
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
OEDS BE Processer For GOCONCIERGE
This service processes business events for GOCONCIERGE. A fail-over configuration can be implemented for this service. What this
means is that the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are
started on. After starting all of the required services on one machine, start all of the required services on the second machine. The first
machine processes the business events until there is an issue. When an issue is detected, the second machine will begin to deque the
business events.
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
OEDS BE Processer For HOTSOS
This service processes business events for HOTSOS. A fail-over configuration can be implemented for this service. What this means is
that the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are started on.
After starting all of the required services on one machine, start all of the required services on the second machine. The first machine
processes the business events until there is an issue. When an issue is detected, the second machine will begin to deque the business
events.
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
OEDS BE Processer For OPENCOURSE
This service processes business events for OPENCOURSE. A fail-over configuration can be implemented for this service. What this means
is that the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are started on.
After starting all of the required services on one machine, start all of the required services on the second machine. The first machine
processes the business events until there is an issue. When an issue is detected, the second machine will begin to deque the business
events.
Cookie Preferences | Ad Choices
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
OEDS BE Processer For SPASOFT
This service processes business events for SPASOFT. A fail-over configuration can be implemented for this service. What this means is
that the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are started on.
After starting all of the required services on one machine, start all of the required services on the second machine. The first machine
processes the business events until there is an issue. When an issue is detected, the second machine will begin to deque the business
events.
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
OEDS BE Processer For TACSPA
This service processes business events for TACSPA. A fail-over configuration can be implemented for this service. What this means is that
the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are started on. After
starting all of the required services on one machine, start all of the required services on the second machine. The first machine processes
the business events until there is an issue. When an issue is detected, the second machine will begin to deque the business events.
As part of this functionality, the application setting in the OEDS group named BUSINESS EVENT WAIT TIME establishes the frequency that
the services on the second machine will check to see if there are issues with the first machine. By default, this value is set to 60 minutes.
When an issue is detected with the first machine, the service on the second machine will begin to process the Business Events.
OEDS Booking Fetch For EQC
This service retrieves new bookings from Expedia on a timed interval.
OEDS IQ Processer For OPENCOURSE
This service processes interactive messages for HTNG and OPENCOURSE. For example, OPERA looks up a profile in OPENCOURSE and
waits for a response.
OG Gaming Business Event
This service processes business events for the OPERA Gaming interface.
OG Gaming Interactive
This service processes interactive messages for the OPERA Gaming interface.
OG Gaming Interval Process
On a nightly basis, this service sends updated profile information to Ballys ACSC.
OG MergeProfile Service
This service is a remoting service call by the gaming interface to merge profiles.
OGEASBusEvent v.1.0
This service processes business events for EAS interfaces. A fail-over configuration can be implemented for this service. What this means
is that the service can now be started in the same enterprise without a detrimental effect on the servers or databases they are started on.
After starting all of the required services on one machine, start all of the required services on the second machine. The first machine
processes the business events until there is an issue. When an issue is detected, the second machine will begin to deque the business
events.
As part of this functionality, a new application setting has been added to the OEDS GROUP named Business Event Wait Time. This setting
establishes the frequency that the services on the second machine will check to see if there are issues with the first machine. By default,
this value is set to 60 minutes. When an issue is detected with the first machine, the service on the second machine will begin to process
the Business Events.
OGEASIntEvent v.1.0
This service processes interactive messages for EAS interfaces.
OPERA Access Point-Activity
This service is used by HTNG interfaces to process activity information.
OPERA Access Point-Availability
This service connects to the OPERA database, and with the inbound data elements from the GWIZ TypeA service, makes the necessary
calls to OPERA APIs. It fetches the applicable room/rate combinations that satisfy the requirements from the availability request. The
service also passes back the response data elements to the TypeA server so that it can be sent back to the channel.
OPERA Access Point-Brochure
This service allows a Web user to request brochure types to sent to them via email or mail methods, given the hotel criteria, brochure type,
name identifier, and e-mail address.
Cookie Preferences | Ad Choices
OPERA Access Point-Folio
This service allows for a folio query from Tibco.
OPERA Access Point-Lov
This service allows for the website to display a list of values. In addition, it also writes OAP information to the RequestLog.xml file.
OPERA Access Point-Membership
This service allows the Web user to enroll in a membership/loyalty program and also provides a hotel access to the guest's
membership/loyalty program information.
OPERA Access Point-Monitor
This service runs the 2C (Command and Control) utility. The 2C utility allows a property to view performance reports and monitor OEDS
Windows Services, and manage Type B failed messages. It also allows users to send out email alerts of errors based on thresholds and
extracts message samples for support purposes.
OPERA Access Point-Name
This service connects to the OPERA database to allow users to create, update, and delete user profile information.
OPERA Access Point-Populate Price
This service populates the GDS_PRICE_QUEUE for first time during channel distribution. The service will populate the price table
information more efficiently based on the value set in OEDS application parameter MAX REGIONAL RATEDAYS.
OPERA Access Point-QueueHandler
This service provides message queuing functionality for HTNG interfaces.
OPERA Access Point-Reservation
This service connects to the OPERA database, and with inbound data elements from the GWIZ TypeA or TypeB Reservation service, makes
the necessary calls to OPERA APIs in order to execute the action of the booking request. The service also passes back the data elements
that result from the booking operation to the TypeA service. This provides immediate return to the channel or to the TypeB Reservation for
reprocessing (failed reservation) or return to the channel.
OPERA Access Point-ResvAdvanced
This service enables the check-in and check-out functionality, handles financial information, and allows OPERA Kiosk to interact with
OPERA PMS using OWS.
OPERA Access Point-Security
This service allows for the management of Web user account credentials.
OPERA Access Point-Stay History
This service retrieves a list of past reservations, given the guest name and agent identifiers. A date range is also allowed. Only
reservations with status checked-out or canceled are returned. Considerable detail is provided about the guests, amenities, services,
facilities, rates, charges, and communications.
OPERA Access Point-UnitOwners
Allows for the management of unit owner accounts using Web Services
OPERA Access Point-Utility
This service processes data coming from any source (channel) and inserts/deletes the data in the oeds_request_log and
oeds_request_log_summary tables to allow users to monitor requests (General Availability, Send Brochure, etc.). The information
inserted/deleted from the tables includes the process time (both the total request time and OAP time) and status, along with the request
date, time, and status.
Cookie Preferences | Ad Choices