Provision database moving to another server

Our database folks are changing the server with the database.  The only thing I know has to change is in the

Help>About Provision>License>Configure License window,

where I will change the server name in Configure floating license server.

 

Is there any documentation that would help me find out if anything else needs to change?  Or, has anyone done it?

 

Thanks,

TJ

Tagged:

Comments

  • Hi TJ,

     

    Is this regarding ProVision or Knowledge Exchange?

     

    If this is ProVision then your databases, .MDB files, are stored locally on your machine (or on a network drive).

     

    If the Database Server is being migrated to a new machine, then you would need to configure Knowledge Exchange's datasources to look at the new server address instead of the old address.  If you are using Tomcat, then you can do this by modifying the KEServer.xml in the /tomcat/conf/catalina/localhost/ directory to look at the new address (0. Migrate data to new databases, 1. Stop Tomcat, 2. Make changes to point to new server in each data source, 3. Save the file, 4. Restart Tomcat, 5. Verify KE is up and running).

     

    The floating license server doesn't use a database as a resource, and thus shouldn't require any changes.

     

    Regards,

    Matt Michael

  • I wasn't around when Provision was initially installed, so I acutally have no idea what is in the databases on the server.

     

    This is definitely the Provision server, not KE.  The Provision program is on our desktops.  I had assumed the databases on the server were for user management and licensing.  If it's something else, please let me know.

  • Hi TJ,

     

    If you use ProVision and interact with Knowledge Exchange (where you would check your notebooks into), then your client data is being stored in Knowledge Exchange.  You may want to take a look at the Technical Briefs in the documentation section under Support (https://knowledge.opentext.com/go/Metastorm) to have a better overall understanding of how ProVision and Knowledge Exchange interface. 

     

    Please note, you are likely working with Knowledge Exchange if you are Checking data In and Out in ProVision. (ProVision is the client-side product, Knowledge Exchange is the server-side product that ProVision interacts with).

     

    Regards,

    Matt Michael

  • Yes, we use Provision with KE.

     

    I'll read the support you recommended, because I am really puzzled about what was in the databases that were migrated.

     

    Thanks!

  • Hey TJ,

     

    If you're using KE, then it would be the Admin Database and Users Databases and any Reporting Databases.  The Admin database houses the User ID's that users use to login to KE, as well as the access rules that you define for those users. User Databases house the actual data that the users check-in to KE. Reporting Databases are there so that you can perform a 'Warehouse Extract' and export data from the User Databases to a reportable format, which you can then report from in the Reporting Database.

     

    Regards,

    Matt Michael

  • The link you provided about sends me to a login that wants me to change my password, and then goes nowhere.

     

    So I still don't understand what was in the provision databases on a different server that isn't a part of KE. Could they have become obsolete when KE was installed later?

  • Hi TJ,

     

    I can't say what would be in those databases as I didn't set them up.  If they're named 'ProServer' or something along those lines, they could be quite old from when KE was called 'ProServer'.

     

    Regarding access to knowledge.opentext.com... have you contacted CommunityAdmin@metastorm.com with your Support ID and asked them to append that to your MCC account?  If not, I would advise doing this.  After you have done so, you should have access to the aforementioned link.

     

    Regards.

    Matt

  • I learned that what they were calling the provision databases were actually the KE databases, stored on a different server than the KE server.  That's more than I ever needed to know. :-)