Recommendation, suggestion to Olympia Server


(estebanp) #1

Hi guys,

We are heavy users of “micro” services based on RO/DA in our systems, but due to the unavailability of a fail over solution to Olympia we split our usage and fail safety among several Olympia servers that serves specific services. In occasions we installed 2 or more Olympia Servers on a system and due to its name, our IT guys have trouble identifying from the Service console which Olympia serves what.

Could you guys add a parameter on the config file that could be used fully or partially on the name of the service when being installed so it can be differentiated on the Services Console?

Thank you.

(antonk) #2


You mean you need to configure the the name of the Windows service that is used to run Olympia?

(estebanp) #3

Hi Anton,

Something to add to the Service name or Display name. Something that when view on the Service Control Panel (Windows) it may read like e.g.

“Authentication Event Repository” , “Powered by Data Abstract, Oxygene and Olympia Server”.

“Transactions Event Repository”, “Powered by xxxx”

“Our name”, “Your branding”

If not specified then it will just be as usual, “RO Olympia Server”, “etc”.

Thank you in advance.

(RemObjects) #4

Thanks, logged as bugs://79498

(RemObjects) #5

bugs://79498 got closed with status fixed.

(antonk) #6

Starting next Beta the service name will be configurable via the ROOlympiaServer.exe.config file:

      <setting name="ServiceName" serializeAs="String">

(estebanp) #7

Great news, thank you guys.

(antonk) #8

As a follow-up may I ask do you use Olympia only as a session store server or you use it to store events data as well?

(estebanp) #9

Hi Anton,

Actually events are the main thing, Sessions are a side effect, we need notifications of almost every action done via our services.