DataHub

Service Setup/change

On the MCe server, through the MCe UI, Create a new Service Instance, in MCe DataHub module

• This creates a code you need to register the service for use

Now on the Service Server (which might be the same physical computer as above)

• Unzip the service which installs the service
• The configure will launch,
  • you can optionally enter a service identifier that will let you install multiple copies on the same server. This would normally only be used when moving it, or when running a SaaS.
  • You enter the URL
  • You enter the code from the 1st step
  • You click the register button.
    • This goes and talks to the MCe server
    • The MCe server will
    • verify the code is correct
    • Verify the code hasn't been used
    • Lock the code to this instance
    • If unable, it will report an error

Now, you change servers or what to change the URL or want to do some other change in setup.

You should first change YOUR code in YOUR program(s) to point at the new location for saving files.

You redo the steps above, the old service will stop working. You will receive warnings asking you if you are sure, since the old service will stop working and if you change your mind after this step you will have to setup again the original service. But of course you would only do this because you want to move the service.

Where you could run into a problem is if you release the wrong service (assuming you have more than one) and you have a hard time accessing the server – maybe you need to book with IT. This means your DataHub service will be down until you get access to YOUR server to fix the mistake you made. Hence the warnings are strongly worded to avoid that.

Unlike a lot of systems, the fact that you will be 'down' for a few minutes is irrelevant because it will just carry on and process the backlog when you get the new one running again.