Method of synchronizing independently distributed software and database schema

Abstract

Upgrading a software application from one or more upgrade package files in a server ( 1 ) to a client ( 21 a , 21 b , 21 c ). According to this method a copy of the upgrade package files and an upgrade database table are created on the server ( 1 ). A pointer is created in the client's ( 21 a , 21 b , 21 c ) file on the server ( 1 ). This pointer points to the upgrade package files on the server ( 1 ); In invoking the upgrade the, the upgrade files are made active, and the upgrade database table is scanned when a client ( 21 a , 21 b , 21 c ) docks. This is to determine the status of an upgrade with respect to the particular client ( 21 a , 21 b , 21 c ). The upgrade is copied to the client ( 21 a , 21 b , 21 c ) if the client ( 21 a , 21 b , 21 c ) has not received the upgrade. At this point the upgrade may be invoked at the client ( 21 a , 21 b , 21 c ). Also disclosed is a program product carrying code for the upgrade method.

We claim:  
     
         1 . A method of upgrading a software application from upgrade package files in a server ( 1 ) to a client ( 21   a ,  21   b ,  21   c ) comprising the steps of: 
 a) creating a copy of the upgrade package files on the server ( 1 );    b) creating an upgrade database table on the server ( 1 );    b) creating a pointer in the client's ( 21   a ,  21   b ,  21   c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 );    c) making the upgrade active;    d) scanning the upgrade database table when a client ( 21   a ,  21   b ,  21   c ) docks to determine the status of an upgrade with respect to the client ( 21   a ,  21   b ,  21   c );    d) copying the upgrade to a client ( 21   a ,  21   b ,  21   c ) if the client ( 21   a ,  21   b ,  21   c ) has not received the upgrade; and    e) invoking the upgrade at the client ( 21   a ,  21   b ,  21   c ).    
     
     
         2 . The method of  claim 1  comprising invoking the upgrade at the beginning of a client ( 21   a ,  21   b ,  21   c ) session.  
     
     
         3 . The method of  claim 1  comprising invoking the upgrade at the end of a client ( 21   a ,  21   b ,  21   c ) session.  
     
     
         4 . The method of  claim 1  comprising invoking the upgrade at the client's ( 21   a ,  21   b ,  21   c ) option.  
     
     
         5 . The method of  claim 1  comprising invoking the upgrade at the server's ( 1 ) option.  
     
     
         6 . The method of  claim 1  comprising creating a docking item file type to scan the upgrade database table when the client ( 21   a ,  21   b ,  21   c ) docks to thereby determine the status of an upgrade with respect to the client ( 21   a ,  21   b ,  21   c ).  
     
     
         7 . An article of manufacture comprising a computer usable medium having computer program code means embodied therein for causing upgrading a software application from upgrade package files in a server ( 1 ) to a client ( 21   a ,  21   b ,  21   c ), the computer readable program means in said article of manufacture comprising: 
 a) computer readable program code means for causing a computer to effect creating a copy of the upgrade package files on the server ( 1 );    b) computer readable program code means for causing a computer to effect creating an upgrade database table on the server ( 1 );    b) computer readable program code means for causing a computer to effect creating a pointer in the client's ( 21   a ,  21   b ,  21   c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 );    c) computer readable program code means for causing a computer to effect making the upgrade active;    d) computer readable program code means for causing a computer to effect scanning the upgrade database table when a client ( 21   a ,  21   b ,  21   c ) docks to determine the status of an upgrade with respect to the client ( 21   a ,  21   b ,  21   c );    d) computer readable program code means for causing a computer to effect copying the upgrade to a client ( 21   a ,  21   b ,  21   c ) if the client ( 21   a ,  21   b ,  21   c ) has not received the upgrade; and    e) computer readable program code means for causing a computer to effect invoking the upgrade at the client ( 21   a ,  21   b ,  21   c ).    
     
     
         8 . The article of manufacture of  claim 7  further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the beginning of a client ( 21   a ,  21   b ,  21   c ) session.  
     
     
         9 . The article of manufacture of  claim 7  further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the end of a client ( 21   a ,  21   b ,  21   c ) session.  
     
     
         10 . The article of manufacture of  claim 7  further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the client's ( 21   a ,  21   b ,  21   c ) option.  
     
     
         11 . The article of manufacture of  claim 7  further comprising computer readable program code means for causing a computer to effect invoking the upgrade at the server's ( 1 ) option.  
     
     
         12 . The article of manufacture of  claim 7  further comprising computer readable program code means for causing a computer to effect creating a docking item file type to scan the upgrade database table when the client ( 21   a ,  21   b ,  21   c ) docks to thereby determine the status of an upgrade with respect to the client ( 21   a ,  21   b ,  21   c ).  
     
     
         13 . A program storage device readable by a machine, tangibly embodying a program of instructions executable by a machine to perform method steps for of upgrading a software application from upgrade package files in a server ( 1 ) to a client ( 21   a ,  21   b ,  21   c ) said method steps comprising: 
 a) creating a copy of the upgrade package files on the server ( 1 );    b) creating an upgrade database table on the server ( 1 );    b) creating a pointer in the client's ( 21   a ,  21   b ,  21   c ) file on the server ( 1 ) pointing to the upgrade package files on the server ( 1 );    c) making the upgrade active;    d) scanning the upgrade database table when a client ( 21   a ,  21   b ,  21   c ) docks to determine the status of an upgrade with respect to the client ( 21   a ,  21   b ,  21   c );    d) copying the upgrade to a client ( 21   a ,  21   b ,  21   c ) if the client ( 21   a ,  21   b ,  21   c ) has not received the upgrade; and    e) invoking the upgrade at the client ( 21   a ,  21   b ,  21   c ).    
     
     
         14 . The program storage device of  claim 13  wherein said method steps further comprise invoking the upgrade at the beginning of a client ( 21   a ,  21   b ,  21   c ) session.  
     
     
         15 . The program storage device of  claim 13  wherein said method steps further comprise invoking the upgrade at the end of a client ( 21   a ,  21   b ,  21   c ) session.  
     
     
         16 . The program storage device of  claim 13  wherein said method steps further comprise invoking the upgrade at the client's ( 21   a ,  21   b ,  21   c ) option.  
     
     
         17 . The program storage device of  claim 13  wherein said method steps further comprise invoking the upgrade at the server's ( 1 ) option.  
     
     
         18 . The program storage device of  claim 13  wherein said method steps further comprise creating a docking item file type to scan the upgrade database table when the client ( 21   a ,  21   b ,  21   c ) docks to thereby determine the status of an upgrade with respect to the client ( 21   a ,  21   b ,  21   c ).