Infralution Support Forum Index Infralution Support
Support groups for Infralution products
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Merging databases

 
Post new topic   Reply to topic    Infralution Support Forum Index -> Licensing Support
View previous topic :: View next topic  
Author Message
PaulS



Joined: 03 Jul 2013
Posts: 21

PostPosted: Thu Feb 25, 2016 9:25 pm    Post subject: Merging databases Reply with quote

Customer has a database for a old product with a license server using the previous version of infralution. Now they have new version of the same software with a new license server url, latest infralution version, and new license parameters in the software. They want to merge the old product licensing database into the new database. They would coexist as separate products I guess. Is there anything to doing the merge? I assume it would just be an export and import operation in sql server. They will direct visits to the old server to the new one with DNS.

They also want to control the number of customer new activations by including the old activations in the count. I see this as too confusing but there will be more on this later.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 4847

PostPosted: Thu Feb 25, 2016 9:39 pm    Post subject: Reply with quote

The first thing to do would be to upgrade the old database to the same version as the new database by running the Configure License Tracker Wizard.

The trick with importing the data will be the fact that the database uses simple numeric IDs and these will be overlapping for Products, Customers, Sales and License Keys. You can import the data in without the IDs (new IDs should be autogenerated) but then you will have to fix up the IDs in the relationships from the old ID to the new ID. TO do this you would need to import tables in the order below keeping track of old ID <-> new ID for each record and mapping these as you progress

Product
Distributor
DistributorProduct
LicenseKey
Authentication
Customer
Sale
LicenseKeySale
SaleUpgrade

The other tables should not be imported.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
jobrieninfralutiondotcom



Joined: 30 Oct 2013
Posts: 3

PostPosted: Wed Mar 16, 2016 6:03 pm    Post subject: Reply with quote

Infralution wrote:
The first thing to do would be to upgrade the old database to the same version as the new database by running the Configure License Tracker Wizard.

The trick with importing the data will be the fact that the database uses simple numeric IDs and these will be overlapping for Products, Customers, Sales and License Keys. You can import the data in without the IDs (new IDs should be autogenerated) but then you will have to fix up the IDs in the relationships from the old ID to the new ID. TO do this you would need to import tables in the order below keeping track of old ID <-> new ID for each record and mapping these as you progress

Product
Distributor
DistributorProduct
LicenseKey
Authentication
Customer
Sale
LicenseKeySale
SaleUpgrade

The other tables should not be imported.



What about CNAME redirection and SSL certificate validations?

We are attempting to migrate legacy apps that have licenses with old Authentication URL embedded in them.

Will CNAME redirects really work? Also, will SSL cert validations to the changed Authentication URL cause Authentications to fail?

Any additional suggestions on how to migrate to a new URL and License server for legacy apps with an installed base of customers using pre-issued keys bound to the client app version they are using?
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 4847

PostPosted: Wed Mar 16, 2016 9:27 pm    Post subject: Reply with quote

The Authentication Service does not require SSL for security (it encrypts all data passed to and from the service) - however I don't think there should be any issues if you use https. You would just need to change the URL in your License Parameters (and in License Tracker). Some forms of redirects can cause problems with web services - however I think DNS redirects should be OK. You would need to test both to be sure.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
jobrieninfralutiondotcom



Joined: 30 Oct 2013
Posts: 3

PostPosted: Thu Mar 17, 2016 5:20 pm    Post subject: Reply with quote

Infralution wrote:
The Authentication Service does not require SSL for security (it encrypts all data passed to and from the service) - however I don't think there should be any issues if you use https. You would just need to change the URL in your License Parameters (and in License Tracker). Some forms of redirects can cause problems with web services - however I think DNS redirects should be OK. You would need to test both to be sure.


Thank you! We have now confirmed this is working using DNS name redirect to new/different Authentication URL, and migrated data to new License DB.

Our only minor snag was/is our legacy customer issued Licenses have an authentication URL using "HTTP" instead of "HTTPS, and our new License server was forcing SSL/HTTPS, causing authentications to fail.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 4847

PostPosted: Thu Mar 17, 2016 8:42 pm    Post subject: Reply with quote

If you want your authentication service to use SSL then I don't see an easy solution to this. You could rebuild the legacy software application to use the new URL and their existing licenses would then work (since the URL is not in the license key but in the software). Is there some way you can set up both a standard and SSL URL to both point to the same location?
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
jobrieninfralutiondotcom



Joined: 30 Oct 2013
Posts: 3

PostPosted: Thu Mar 17, 2016 8:57 pm    Post subject: Reply with quote

Infralution wrote:
If you want your authentication service to use SSL then I don't see an easy solution to this. You could rebuild the legacy software application to use the new URL and their existing licenses would then work (since the URL is not in the license key but in the software). Is there some way you can set up both a standard and SSL URL to both point to the same location?


Thank you for providing fantastic support for your products! We love your licensing solution. Smile

Our solution to handle legacy client app/licenses is we modified our cloud app and Licensing source so that our cloud app doesn't enforce HTTPS/SSL for just the .../AuthenticationService.asmx URL to allow these legacy licenses to use HTTP...../AuthenticationService.asmx. It would then also allow our newer apps/licenses to use the HTTPS...../AuthenticationService.asmx.

Thanks again!
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Infralution Support Forum Index -> Licensing Support All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group