LOADING DATA INTO TENANT TABLES

Transcription

1 LOADING DATA INTO TENANT TABLES Fellow and OpenEdge Evangelist Document Version 1.0 December 2011 December, 2011 Page 1 of 10

2 DISCLAIMER Certain portions of this document contain information about Progress Software Corporation s plans for future product development and overall business strategies. Such information is proprietary and confidential to Progress Software Corporation and may be used by you solely in accordance with the terms and conditions specified in the PSDN Online ( Terms of Use ( Progress Software Corporation reserves the right, in its sole discretion, to modify or abandon without notice any of the plans described herein pertaining to future development and/or business development strategies. Any reference to third party software and/or features is intended for illustration purposes only. Progress Software Corporation does not endorse or sponsor such third parties or software. In the earlier videos in this series, and the white paper on Defining Tenants, Domains, and Users, I set up tenants, domains, and users for the sportsmt sample database. Now I m finally going to load some data into the database for different tenants, and see the effect of all the work done so far, when users in different domains for different tenants connect to the database. In the videos and the screenshots in this and later papers, I've switched from running OpenEdge Management to just running OpenEdge Explorer. This is just to emphasize that the Database Administration Console features I'm showing you work the same in both products. Selecting the sportsmt database connection link in the Admin Console brings up the list of options in the list frame to the left, including Tenants: I select EastSports, and then Edit tenant, to show you something very important: December, 2011 Page 2 of 10

3 In a previous session I chose the delay allocation option for some of the tenants when I created them, to show you how you can move individual objects around between areas, if you don t want them all to wind up in the default areas defined for the tenant. I could have chosen to force allocation of those partitions when I committed the tenant creation, but I chose not to. The important thing to realize is that at some point you have to allocate those paritions before you can store data into them; they don t get allocated automatically. You can go back into the Edit tenant operation and allocate partitions at any time before you load data into them. Under the Tools menu is an item labeled Allocate partitions: If I select that, and confirm that it s going to allocate parititions that were set to delayed, the EastSports partitions are allocated and I can load data into the table instances for that tenant. There is also an API in ABL that gives you access to your December, 2011 Page 3 of 10

4 tenants, and you can use the built-in Allocate() method to allocate partitions at runtime, but that API is beyond the scope of what I m doing here, which is to show you how to do things in the tools. In any case, I also have to go in and do the same thing for the WestSports and SouthSports tenants, which were also created with delayed allocation. After completing that, the next task is to load the application data into the database from all the individual OpenEdge 10 databases it was dumped from. There are several ways this can be done, and other options are shown later in this series, but here I want to allow a database administrator for each tenant to load the data for that tenant, so I need to create some more users. Keep in mind that this simple example doesn't reflect the security requirements of a real application. An application user connected using the blank Userid wouldn't normally be allowed to define administrator users for various tenants. In any case, the new users are all named Admin. This also helps reinforce the fact that you can have multiple instances of the same username in a database, because it s the combination of the userid and domain name that uniquely identifies a user. The first Admin user is for the EastSportsUser domain, and the password is Admin as well. The screenshot below shows the first of four new Admin users: Each of the four Admin users will be in charge of loading and managing one tenant s data in the new combined database. Below I ve created all four Admin users, one for each domain: December, 2011 Page 4 of 10

5 Since I made changes to the data security in an earlier session to show how to set security based on a domain, I need to undo at least one of those settings, where I disallowed Can-Write access to the Order table for everyone in the WestSportsUser domain. I need to change that setting in the Edit data security operation or my Admin user won t be able to load the data: Once that s taken care of, I can show how to get data into the database. I just do this with some simple ABL statements in a procedure window. First I open a little procedure named loadstate.p to load all the state names and state codes into the State table. You can see that it just inputs from a.d file where I dumped the State table out of one of my four OpenEdge 10 databases; they would all have had the same data for this table, of course, and now in my new multi-tenant database I only need one copy of that data: December, 2011 Page 5 of 10

6 input from State.d. repeat: create state. import state.state state.statename state.region. end. Remember that I left the State table as a shared table, so it works the same as it did in the old databases. That is, all users, no matter what tenant they re associated with, can see the same State data. In principle any user with the right privileges can load that data. There s no need to be logged in using a domain for a particular tenant. I can just run the procedure using the blank userid I connected to the database with, since that hasn t been disallowed, even though once again, the blank userid should never be allowed to do this in a real application. After executing loadstate.p I can verify the results, simply by typing FOR EACH State: DISPLAY State. This confirms that any user in any domain, or in my case in no specific domain, can see the State table: Now I start doing the multi-tenant data loading. One of the simplest ways to establish a userid is to use the ABL SETUSERID function. In a multi-tenant OpenEdge 11 database, the Userid needs to be qualified with the user s domain unless you re just accessing shared and default tenant data through the blank domain. To get started, I re-establish my user identity using the Admin userid for the EastSportsUser domain, which of course is for the EastSports tenant: MESSAGE SETUSERID( Admin@EastSportsUser, Admin) VIEW-AS ALERT-BOX. The MESSAGE statement just displays yes if the Userid and password combination is valid. Keep in mind that I set up these security domains, each of which has its own encrypted domain access code, which in principle adds a level of security to the whole user authentication process. But here I didn t have to specify the domain access code. Why is that? December, 2011 Page 6 of 10

7 If you use the SETUSERID method, or for that matter if you use the ABL CONNECT statement or use U and P to connect to the database from the command line, OpenEdge retrieves the domain access code from the domain record based on the domain name you used, and creates the security credentials for you. This is a very important security consideration. If you use the _User schema table and the _oeusertable authentication system in your database, then users can connect to the database in all these ways that effectively bypass the additional level of security provided by the domain access code. In a later video and paper I show how to set up the security credentials yourself, using the CLIENT-PRINCIPAL built-in object that is part of the new OpenEdge security mechanism, and which lets you take advantage of the domain access code to enhance the security of your database. When I execute this one line of ABL, the MESSAGE statement displays the return value from SETUSERID, which confirms that I connected successfully: Now I can load data into the EastSports tenant partitions. The code to do that is in a procedure called loadeastsports.p, which inputs data from a Customer.d in an EastSports sub-directory, then another.d for the Order table, and one for the OrderLine table. I deal with loading Item records in a later video, because I m going to do something special with those. You can also see below that the procedure disables triggers for LOAD of all these tables (I could have left off the statement for the Item table, since I m not loading it here). As you might expect, there are Create trigger procedures for the tables that assign a key, the customer number or order number, to the next available value from a sequence. Since I m loading existing records that already have keys from another database, I don t need the triggers. And also, I haven t actually created the sequences those triggers use yet, because once again there s something special to be said about sequences in a multi-tenant database that I ll save until later: DISABLE TRIGGERS FOR LOAD OF Customer. DISABLE TRIGGERS FOR LOAD OF Order. DISABLE TRIGGERS FOR LOAD OF ITEM. input from EastSports/Customer.d. repeat: December, 2011 Page 7 of 10

8 create cust. import cust.custnum cust.name cust.address cust.postalcode. end. input from EastSports/Order.d. repeat: create order. import order.custnum order.ordernum order.orderdate order.shipdate. end. input from EastSports/OrderLine.d. repeat: create orderline. import orderline.ordernum orderline.linenum orderline.itemnum orderline.qty. end. The Customer.d below shows the ten Customer records loaded into the new database from the old EastSports copy of the database: 1 "Lift Line Skiing" "276 North Street" "02114" 2 "Urpon Frisbee" "Rattipolku 3" "45360" 3 "Hoops Croquet Co." "Suite 415" "02111" 4 "Go Fishing Ltd" "Unit 2" "HA8 7BN" 5 "Match Point Tennis" "66 Homer Ave" "75431" 6 "Fanatical Athletes" "20 Bicep Bridge Rd" "AB9 2YY" 7 "Aerobics valine KY" "Peltolantie 2" "1234" 8 "Game Set Match" "Box 60" "851 14" 9 "Pihtiputaan Pyora" "Putikontie 2" "44800" 10 "Just Joggers Limited" "Fairwind Trading Est" "BL0 9ND". PSC filename=customer records= ldbname=sportsmt timestamp=2011/09/12-10:57:45 numformat=44,46 dateformat=mdy-1950 map=no-map cpstream=ibm Remember that the backstory for these examples is that there were four separate OpenEdge 10 sports databases, one for each of the clients, like EastSports. EastSports had just 10 Customers, with CustNum values of 1 through 10. So I have a separate set of.d files for each of my four clients, dumped from each of their databases. The data I just loaded will only be visible to userids that connect using a domain for the EastSports tenant. To load the next set of data, I reconnect to the database using the Admin id for WestSports, and execute a similar procedure called loadwestsports.p. All the data from the WestSports database.d s goes into the WestSports tenant partitions. Once that s complete, I keep going for NorthSports and SouthSports. Once all that is complete, I can reconnect as an ordinary user in the EastSportsUser domain, my first user JoeEast: SETUSERID( JoeEast@EastSportsUser, Joe ). December, 2011 Page 8 of 10

9 I just need to type FOR EACH Customer: DISPLAY Customer to see the EastSports customers. I have loaded four sets of Customer data into the database, but Joe only sees the data in the EastSports data partitions: Next I can change users, to JimWest in the WestSportsUser domain: SETUSERID( JimWest@WestSportsUser, Jim ). When I re-execute the same FOR EACH Customer code block, I see the four Customers that were in the WestSports Customer table. Note that I have overlapping customer numbers, as well. Since the index data is stored in separate partitions for each tenant, I can have a separate unique index for each tenant for the same table: December, 2011 Page 9 of 10

10 So now that I have created a multi-tenant OpenEdge 11 database; created tenants, domains, and users for those domains; enabled tables for multi-tenancy; and allocated the partitions for the multi-tenant table instances; I was able to load data into each tenant that is seen only by users who connect using that tenant s domain. In the next paper I go into more detail about how you can set up security credentials to maximize the security of your database. December, 2011 Page 10 of 10