1. Upgrading and Migrating IBM® i2 iBase Databases
6/26/2018
Upgrading and Migrating IBM® i2 iBase Databases
IBM Security support Open Mic
To hear the WebEx audio, select an option in the Audio Connection dialog or by access the Communicate > Audio Connection menu option. To ask a question by voice, you must either Call In or have a microphone on your device.
You will not hear sound until the host opens the audio line.
For more information, visit:
NOTICE: By participating in this call, you give your
Irrevocable consent to IBM to record any statements that
you may make during the call, as well as to IBM’s use of such
Recording in any and all media, including for video postings
on YouTube. If you object, please do not connect to this call.
October 19th 2017

2. IBM Security Learning Academy
6/26/2018
IBM Security Learning Academy
New content published daily!
Learning at no cost!
Learning Videos ● Hands-on Labs ● Live Events

3. 6/26/2018
Panelists
Dan Brace – Presenter – L2 Technical Support Engineer for i2 Products
Dan Shaver – Panelist – L2 Technical Support Engineer for i2 Products
Linda Miyoshi – Panelist – L2 Technical Support Engineer for i2 Products
Christian McQuillan – Panelist – L2 Technical Support Engineer for i2 Products
Kevin Gillis – Panelist – L2 Technical Support Engineer for i2 Products
Cindy Wotus – Moderator – Support Planner for i2 Products

4. 6/26/2018
Goal of session
The goal of this session is for you to have a better understanding of how you can upgrade your IBM i2 iBase database from an older version to the latest version

5. Agenda By the end of this session we will have gone through…
6/26/2018
Agenda
By the end of this session we will have gone through…
Environment Best Practices and the Example Environment
What we will and won’t be covering here today
Upgrading your iBase Clients
Backing up your iBase Database in SQL Server Management Studio
Including steps to take and settings to change in iBase
Restoring your iBase Database to your new SQL Server Machine
Pointing your iBase Clients to the new server
Other Considerations
Search 360 Indexer Upgrade
SQL Login Considerations
OK, so by the end of this session, hopefully you will have a good understanding of
What some of the best practices are for upgrading and migrating
Understand that we need to upgrade our iBase clients. (I’m not going to go into too much detail on this front, but will show you what you need to know)
Show you very briefly how to backup and restore your SQL Databases
Explain how to re-point your iBase client so that it points at your new database
And also show you a few other considerations to keep in mind, such as SQL users and The search 360 indexer.

6. 6/26/2018
The Environment
OK, so now lets have a quick look at the example environment that I will be referring to today.

7. The Environment Client Windows 10
6/26/2018
The Environment
Client
Windows 10
Client environment is NOT changing (i.e. we are not going to move the iBase clients to a new location and are not upgrading Windows).
Has a shared and accessible network location for the iBase Security (*.ids) and the iBase Database (*.idb) files
iBase
iBase (Will be upgraded to iBase )
Uses both iBase Security and Windows Authentication
User Guide Database
Upsized to SQL Server
Security also Upsized to SQL Server
Alerting Enabled
Search 360 Enabled
Windows Server 2008 R2 (Old SQL Server)
Microsoft SQL Server 2008 R2 Standard
iBase Search 360 Indexer on this machine
Windows Server 2012 R2 (New SQL Server)
Microsoft SQL Server 2016 Standard
iBase Search 360 Indexer will be on this machine
So as you can see from the slides, our environment consists of a fairly typical setup for iBase.
We have a Client side machine with iBase installed onto it, which in our case is currently running version of ibase, and this client machine is also running Windows 10, so you’ll see that in the screenshots included in the presentation.
Just as a note here, I will NOT be changing the client environment itself, only the software installed onto it. i.e. we will not be changing the location of the client, or the version of windows etc.
The client machine has got a set of ids and idb files on it, (which are our database connection and security connection files that hopefully you're all familiar with).
The iBase database is actually the User Guide database, which hopefully you are all aware of, but if not just to let you know that this is a really nice sample database which we ship with all versions of ibase which allows you to test play around with iBase when you’re just getting started, and it's a good database for us to use today, because it has some data in it, and we use it for a lot of troubleshooting our technical support issues.
I’ve also enabled Search 360 and alerting on this database, because these are I would say the main 2 utilities of iBase which our customers are most concerned with when considering migrations, and use on a day to day basis that may be affected by an upgrade or a migration, so I’ve turned these on for us to see how to work with those.
The server environment hosting our iBase database is currently running Windows Server 2008 R2 and has Microsoft SQL Server 2008 R2 installed on it, and in terms of authentication, I’ve set up the database so that it can log in using both iBase security, and Windows Authentication, so as long as the domain user I’m signed on as exists in the SQL Server and has the right privileges, then it should be able to get into the database.
So what are we going to change?
In terms of changes, we will be upgrading iBase to version and we will be migrating our iBase database over to a new machine running Windows Server 2012 R2, with SQL Server 2016 standard installed onto it. As I mentioned before in the previous slide, we will not be changing anything about our Client side environment itself, only the software installed onto it.

8. The Environment What we won’t be covering… Upgrading your SQL Server
6/26/2018
The Environment
What we won’t be covering…
Upgrading your SQL Server
Example is from a new install perspective, rather than an in place upgrade
How to Backup and Restore your SQL Database in Detail
We will show you this in the example, but you should refer to available Microsoft documentation for more detail on how to backup and restore to SQL Server
The upgrade of your Windows Environment
Refer to available Microsoft documentation for more detail on new installations and in place upgrades of Microsoft Windows products
Client environment is NOT changing (i.e. we are not going to move the iBase clients to a new location and are not upgrading Windows).
I also thought it would be important for me to explain what I’m not going to cover in this open Mic session.
Obviously we’re IBM Technical support engineers and not Microsoft Support Engineers, so though I am going to show you some bits and pieces of very simply what we do inside SQL Server, I appreciate that a lot of you likely have SQL DBA’s and IT Administrators who will handle the ‘back end’ of things for you, so I’m not going to cover the SQL Side in too much detail.
In the same vein, I’m not going to be showing you how to upgrade your Windows installation, and I’m not going to show you how to upgrade your SQL Server software either. For our demo, we are pretending that we are migrating our database over to a completely separate database.
So if you need to upgrade your version of SQL Server or Windows, you'll need to reach out to Microsoft for that information.

9. 6/26/2018
Best Practices
Deploy your upgrade in a test environment first if at all possible
Make sure you have backups of your databases and associated security and database files (*.ids & *.idb)
Consider the impact to your users
Get the software you are going to upgrade downloaded from IBM Passport Advantage and Fix Central
OK, so with the Environment considered and with an idea of what I am and am not going to show you, let’s have a look at a best practices we would advise for your migration.
Most of these are pretty obvious and pretty simple, but worth mentioning just in case you haven’t considered any of them.
So, the first one listed is ’deploy your upgrade in a test environment if at all possible’. Some of our customers have at least 2 different environments set up with copies of their databases. This is usually for scenario’s exactly like the one we are showing you today. Our Customers tend to have their production environment, which they will only apply changes to, once they have tested them first in a test environment, so that’s worth mentioning here, as if anything goes wrong, you at least aren’t affecting your current users.
Next on the list is to make sure you have recent backups of all your databases and to make sure that the ids and idb files we will be talking about throughout today, have also been recently backed up somewhere as well.
We also have on the list a note here to make sure you’re considering the impact to your users. By this what I mean is, it’s probably not a sensible idea to do any kind of migration work at 10 oclock on a Wednesday when your users are expecting no down time, and is probably a better idea to conduct the work out of hours, for example overnight or over a weekend.
The last thing (again is pretty obvious) but I’ll say it anway, make sure you get the software you are going to upgrade when you do the migration downloaded from the IBM Passport Advantage site and Fix Central if you will also be applying Fix Packs

10. 6/26/2018
Upgrading iBase
OK, so our migration is going to consist of 2 MAIN steps, which are the Upgrade, and the Migration. We usually recommend that you upgrade iBase in situ first, so let’s have a look at that now.

11. Database Properties and details
6/26/2018
Database Properties and details
OK, before we get going with the bulk of the slides, I just want to point out the little indicator I’ve placed at the top right of all these slides. All these are is a quick indicator to help you guys on the call figure out where I’ve taken these screen shots from, so if the tick is underneath the Windows 10 logo, it means I’m on the client, if it’s under the old Windows 2008 logo it means I’m on the Database Server, and if it’s under the shiny cool Windows 2012 logo, it means we’re looking at the client we’re migrating too, so hopefully that helps out a bit 
OK, so now first of all, let’s have a look at the properties in our Database.
Here you can see I’m on the Client machine and I’ve opened up iBase designer which I’m hoping you’re all familiar with.
I’ve then logged into the database we will be upgrading today, which as I mentioned on the previous slide is the iBase User_Guide database.
Once you’re in here you can click File -> Database Properties to bring up a dialog box which will show you some useful information about the database. As you can see from the left screenshot, this database is stored in a SQL Server running 2008, and authenticating using Windows Authentication
For the right screenshot, I’ve simply gone to Help -> About IBM i2 iBase from the menu bar, and it then shows me information about my iBase installation, including the fact that the database is currently running on iBase version
Obviously you don’t have to do this, this is just to show you the versions etc.

12. 6/26/2018
Database features
OK, so as I mentioned before, I’ve turned on Search 360 and Alerting for this database. Again this isn’t something you need to do for the migration, but I just thought I’d quickly just show you the fact that they are both turned on as you can see from these screenshots. A lot of our customers typically use these two features on a day to day basis, and therefore want to preserve during their migration, so we will show you how to do this during the presentation.
You can see from the last screenshot here at the bottom, that in our client Environment, we have 3 main tools we will be using throughout the session, two of which I am sure are very familiar (those being iBase user and iBase Designer) and the last one here in blue, which is the iBase Database Configuration Tool.
I’ll explain how we use this later, but it’s worth knowing that these can be installed if they aren’t already via a quick ‘Modify installation’ in the iBase msi installer or via the Control Panel. We’re going to need the Database Configuration tool in a later step, so make sure you get that installed on the client machine before starting.

13. 6/26/2018
Upgrading iBase
Speaking of installations, that’s where we’re going to start. I know that this slide is a little blurry, but don’t worry too much about not being able to see the content of the slide, when you get access to the deck afterwards you should be able to see what I mean, bu these are just here to jog your memory as to what you need to do
So, let’s upgrade iBase. The good news here, is that as iBase is a .Net application, it is very easy to upgrade. You simply download the latest installer for the latest version of iBase which as I mentioned before is from the IBM passport advantage website. You can then extract your files, navigate to those files, and either run the setup.exe file included in the download, or do what I have done in these screenshots, which is instead utilizing the iBase msi installer, which is found in your extracted files\IBA\IBM i2 iBase 8\IBM i2 iBase 8.msi.
Double click the installer to run it, and follow through with the steps to upgrade your iBase client, as per your requirements.

14. 6/26/2018
Upgrading iBase
So, I’m not going to bore you here by showing you a million screenshots of me clicking through all of different options on how to install from an MSI file, as it probably wouldn’t be very useful to you in this presentation, but what I will call out here is that above, you can see I am selecting the ‘Custom’ option from the list, so that I have full control over what I am and am not installing. Obviously what you install may be very different to what I install, as your licenses may vary, and you may not use some of the features shown here.
One of the features you will find in here however, is the Database Configuration Utility, which exists in the list of options under Extended Features -> Tools. So if you were wondering how you get that installed onto the system, you can do that now.
So, simply follow through with the msi installation, and you should then be sat with a shiny new version of iBase installed.

15. 6/26/2018
Upgrading iBase
OK! So,once the installation has completed, we need to open up the database in iBase designer, by which I mean open iBase designer, and then open the database as well. (i.e. open the idb file).
As you can see from the screenshots, when we open our database in iBase designer, we are shown a message stating that iBase designer needs to upgrade search 360 so that it can be used in the latest version. NOTE that when you do this, the search 360 index will no longer work with the search 360 indexer, and your users on older client versions of iBase (8.9.1 for example) will not be able to use search 360.
If we use the Help and about options in iBase designer, we can also see that yes, iBase has in fact been upgraded to
Bare in mind that you will need to do this for all your databases that you use so that they are all at the right version.

16. Saving the database password
6/26/2018
Saving the database password
While we are in iBase designer, we should also take this opportunity to save our Database Password somewhere. Note that this is not the same as the password you use to sign into your iBase database, but rather, a password unique to your database that is used to get you into your database, should you be unable to connect to your security file for some reason.
To find yours, in ibase designer go to Tools -> Feature Availability -> Options, and then switch to the Advanced tab. At the bottom of the options, you will find the ’Database Password’ field, which you should copy and save somewhere useful. Don’t worry too much about this for now, we’ll go into detail about what this is used for later.

17. 6/26/2018
Changes in iBase
So that’s the upgrade done, now we’re going to move onto changes we are going to make in iBase before we do our migration.

18. Changes in iBase before we backup the database
6/26/2018
Changes in iBase before we backup the database
Make sure all users are out of the database!
Make sure you’ve taken a backup.
Consider using a test environment.
Make sure you’ve taken a backup!
Make sure you’ve taken a backup!!!
OK, so there are a few things that we need to do first to our database before we migrate it over from one database to another, so first lets do a bit of house keeping.
First, we need to make sure that all of our users are out of the database while we do the migration. As I’ve mentioned before, you may want to carry out the migration out of hours to ensure this, and again I’ve already mentioned about potentially having a test environment to test your migration in first, to avoid disruption to the production environment.
Lastly but definitely not least, make sure that you’ve taken appropriate backups of your database before carrying out the work, so that you know you can get back to where you were, just in case, and if at all possible, consider using a test environment rather than just your production environment to make sure the work goes off without a hitch. It’s on this slide the most, because it’s the most important.

19. 6/26/2018
Disabling Search 360
Ok, so now we’ve done our housekeeping and we know there is no-one in the database, let’s dive back into iBase designer again so that we can work with Search 360 and Alerting.
Let’s start with Search 360. First, go to Tools -> Search -> Search 360 Administration
The Search 360 Administration window will then appear. Click the check box next to ‘Enable Search 360’ and click OK. When you do so, the ‘Disable ‘Search 360’ message will appear, asking you if you wish to remove the existing search index, or keep it. We’re going to select ‘No’ so that we keep the existing search index, and don’t have to completely re-index the database when we move it.

20. Suspending Alerting Now let’s look at Alerting.
6/26/2018
Suspending Alerting
Now let’s look at Alerting.
If you use Alerting, you will also want to Suspend alerting while you do your migration. To do so we’re going to go to Tools -> Feature Availibility -> Alerting Configuration… and in the resulting window, click the Suspend Alerting Button.
I’ll mention a VERY IMPORTANT note here, which is to not do this UNLESS you have first upgraded to the latest version of the iBase, as otherwise when you click Suspend alerting in an earlier version, you’ll find that this also deletes your existing Alert Definitions, which obviously you don’t want to do, so make sure you upgrade iBase first.
Once you’ve done this, close iBase designer again, and switch to your current SQL Server box, in our case, our ‘old’ SQL server box is SQL Server 2008 R2.

21. Backing up your existing iBase Database
6/26/2018
Backing up your existing iBase Database
Now let’s look at the meat and potatoes of the move. backup and restore.

22. 6/26/2018
Backup
Now, Remember here that I’m not going to talk in too much detail about how to backup and upgrade SQL Server from one place to the other, as I’m sure that most of you likely have SQL Server DBA’s to do this, but suffice to say that the above screenshots show you pretty much what you have to do, this being;
- Go into SQL Server management studio
Right click your database
Go to Tasks -> Back Up
And backing up your database to somewhere on your disk. Again, have a look at the Microsoft documentation if you need further assistance.
Once you have done this, for your main data database, also repeat the process for the _Log and _Sec databases, which are your audit log database and your Security database.
As another important note here, just because you’ve taken the database backups, doesn’t mean we’re done with this server, so make a note to make sure that it is not de-commissioned at this point, or you will cause yourself headache further down the line.

23. 6/26/2018
Move your Backup Files
Once you’ve backed up your database to disk, move your Backup files from your existing old SQL Server machine, onto your new shiny SQL Server machine, here I’ve moved them over to my SQL Server 2012 R2 Box.

24. Restoring your iBase Database
6/26/2018
Restoring your iBase Database
Now we move onto restoring the files.

25. Restoring your database
6/26/2018
Restoring your database
On the new Machine, we’re now going to sign into SQL Server Management Studio as an Administrator, and right click on Databases, and then click restore database.
When the Restore database window appears, click the radio button next to Device: and click the elipses highlighted in the screenshot to show the browser where you will locate your backup media (i.e. the files you just created).

26. Restoring your database
6/26/2018
Restoring your database
When the window loads, click the Add button, then navigate to your backup file you wish to restore. As a quick note here, you can only do one file at a time, so don’t try to multi select the .bak files.
Once you’ve clicked OK, click OK in the main window and the database will be restored by SQL Server Management studio.
Repeat the process for the other two databases. (i.e. the _Log and _Sec databases).
Obviously if you are migrating multiple upsized iBase databases, you will need to repeat these steps for all the databases you are migrating.

27. 6/26/2018
Users
So this slide is actually more of a note that will likely again be handled by your SQL DBAs but it is worth mentioning as we have seen customers in the past run into issues because they haven’t considered it.
Hopefully you’ll recall that I said on one of the previous slides that the user I use to login in this iBase database, can do so through iBase security OR Windows Authentication.
Well, if we’re using Windows Authentication, we need to consider the fact that our user logins on this new blank SQL Server database might not exist yet, so in order for us to use the database, we’ll have to make sure that we add our users to the new SQL Server database as well, with the appropriate permissions.
The best way I’ve found of doing this is to have both the old and the new server open, and then checking the permissions on the users in the old database, by right clicking a user, and clicking Properties, and switching to the User Mapping tab.
There, we can check the displayed values of our old users, and use that information to re-create those users in the old database.
Again, I’m sure most of you have probably got DBA’s who look after this sort of thing, and I’m sure they’ve probably got better ways of backing up and restoring users as well as the data, but this is just a sort of ‘in a nutshell’ view.

28. 6/26/2018
Compatibility
Lastly here, it’s also worth noting here that although we’ve restored our database over to SQL Server 2016, the database itself is actually still has SQL Server 2008 compatibility. If you want to change this to be SQL Server 2016 Compatible, you can do so under the properties for the database, under the Options tab.
Now we’ve restored the database to SQL Server 2016 on our SQL Server 2012 R2 Server, sign out of SQL Server Management Studio, and again make sure no one is in the database, before switching back t the Client.

29. Reconfiguring the Database
6/26/2018
Reconfiguring the Database
OK, so now we’ve upgraded iBase, we’ve restored our data to the new place, now we need to actually tell the iBase software where this new location is.

30. Reconfiguring your Database
6/26/2018
Reconfiguring your Database
So hopefully you remember the little blue icon from before.
This is the iBase Database Configuration tool, which hopefully is now installed on your client. Click this to open it.
What we are going to do here is tell your security file, and your database files, (i.e. your ids file and your idb file) that they should no longer point to the database they currently point to, but instead point to another database.
This is a bit of a weird process, as first we must repoint ONLY the security file, and once we have done that, we can then repoint the database file as well.
When the Database Configuration Utility opens, click the ellipses highlighted in the screenshot next to the ‘Security File Name:’ field, and navigate to where your security file is on your client system. (Note that if this is on a file share, and you have also moved client, you need to make sure you give your users the right permissions, or you may run into trouble).
From here, enter the user name of an administrator for your iBase database. This can either be an iBase username, or a domain style username, either should work. As you can see in the screenshot, I’ve used a domain user, but I could just as easily have used SYSADMIN SYSADMIN, which those of you who are familiar with the User Guide database will know is our supplied admin user for this database.
Once you’ve entered the details, press Next.

31. Reconfiguring your Database
6/26/2018
Reconfiguring your Database
When we press next, we get to the Database Configuration Screen, where we can change the location of the SQL Server that contains our database information.
Remember here that so far we are just re-pointing the User Guide databases security file from our old server to the new one, not the details about the data in the database, so once we’ve made this change, iBase will no longer go and look on your old server for the security file (or rather Security database), and instead, will look on the new database.
Select your new SQL Server database from the list, or type it in manually if it doesn’t appear, and then either provide SQL Server authentication for the SQL Server, or (if your current user has appropriate privileges to connect to the database, and your SQL Server is set up to allow it, click ’Use Windows Authentication’).
Also make sure that you have ticked ‘Test connection before saving’ to make sure you can see that everythings gone smoothly before saving your changes.
Once you’ve entered your SQL details, (or checked the box for Windows Auth), click Save to save your changes. Hopefully you see something similar to the final screenshot, where we can see the test connection succeeded and the settings were updated.
That’s the security file done. Press close, then open the Database Configuration Utility again so that we can reconfigure where iBase looks for the data database.

32. Reconfiguring your Database
6/26/2018
Reconfiguring your Database
So open up the Database Configuration Utility again, but this time around, we’re going to select both our Security File AND our Database File, i.e. our ids AND our IDB. Again we’re going to enter in our credentials as before, and follow through the exact same steps as we did just now. This will change the database’s location rather than the security file this time around however.
Again, here you can see that this time around, I’ve signed in using the SYSADMIN iBase account to make the changes rather than the Domain user just to show you that both work just fine, but remember I’m only doing this for demonstration purposes. I’d expect you guys to use the same credentials both times. Obviously again I have also switched the Server field from the old SQL Server box, to the shiny new SQL Server 2012 one.

33. Reconfiguring your Database
6/26/2018
Reconfiguring your Database
Again, we should see something like the screenshot above showing us that the test connection was successful and that the settings were applied successfully.
Once we’ve done this, we can close out of the Database Configuration Utility, and open up iBase designer again. If you then check the Database Properties, you’ll probably find 2 things. 1 it now shows the correct new database, and (if you’ve moved to a newish version of SQL Server) you might find that you have a little red message that says that this version of SQL Server is not supported.
Don’t worry if you get that message. It’s expected. The latest release notes and system requirements are the best source of information as to what is and isn’t a supported configuration, but in most all circumstances you can safely ignore that message. The reason why it comes up is because when iBase was developed and last updated, the versions we have updated to didn’t exist!

34. 6/26/2018
Search 360 and Alerting
OK, now we’ve moved the database, we need to just do a few more bits of housekeeping, and we should be ready to rock and roll again.

35. 6/26/2018
Resuming Alerting
So previously, we disabled search 360, and we suspended alerting temporarily while we moved our server, so obviously we now need to turn them back on. This may seem simple on the surface, but for Search 360, will likely involve a few extra steps, so we’ll start with Alerting.
Make sure you sign into iBase Designer to do this.
To start alerting again, once more go to Tools -> Feature availability and Alerting Configuration…
When the Alerting Configuration window loads, you’ll find that the Server field likely has the old database location in it. Don’t worry. This is expected. We need to now manually change this address to the name of the new Location (so in this case, I changed the Server name from WIN-2K8-SQL to WIN-2K12-SQL) and then pressed, ‘Resume Alerting’.
Then close the alerting configuration window, and sign out of iBase Designer.
You should now be able to log back into iBase User and see your old alert definitions and your Alert inbox with any alerts you previously hadn’t looked at before the migration.

36. Resuming Search 360 Let’s look now at re-enabling Search 360.
6/26/2018
Resuming Search 360
Let’s look now at re-enabling Search 360.
So Re-enabling Search 360 means 2 things. First, we need to allow our users to use Search 360 via the index we preserved earlier again. This part is pretty easy. We simply go back into ibase designer, sign into our database, and then go back to the Search 360 Administration option we used earlier, under Tools -> Search -> Search 360 Administration
We simply then click the Enable ‘search 360’ checkbox and click OK again. If you are signed in as a person with appropriate privileges in the SQL Database, this will automatically enable CLR and do some other bits and pieces on the SQL Database, and will then allow the users to use Search 360 against their previously indexed records again. If it hasn’t automatically been able to enable CLR against the database, then you’ll need to have a look at the Search 360 guide in order to enable it using a script in SQL. Don’t worry too much about that now, I’ll have it in the useful links at the end of the presentation.

37. Installing the Search 360 Indexer
6/26/2018
Installing the Search 360 Indexer
Now as I said on the previous slide, re-enabling Search 360 is two fold for our new database. Not only are we doing the client side, but we also need to make sure that we are properly indexing the database on our server side, via a scheduled index of the database.
To do this, we need to install the search 360 indexer onto our new SQL Server machine. Again, follow the steps with the MSI file that we did earlier, but this time when you get to the custom features part of the install, only select to install the ‘Server’ features. As a side note here, you’ll need to make sure you’ve got .Net 3.5 installed on the machine in order to run the installer, otherwise you get a nasty Warning like the one on this slide.

38. 6/26/2018
Scheduling your Index
Once you have installed the ‘Server’ features of iBase, you should then get the iBase Index Service Configuration tool installed onto your machine. Start that up, and you should be shown the SQL Server login screen. Again, you are entering the SQL Server details here for the server, so either provide a SQL Server login for your server, or alternatively, click the Windows Authentication button if you are authenticated in the server, and click OK. It may take a few moments for the Login to happen correctly.
Once you have connected to the database, you should find that the Add button can now be clicked, so that we can add an indexing configuration against our iBase database. Click the Add button.

39. 6/26/2018
Scheduling your Index
The Configure Database window will then appear, which allows you to enter the details about the database which you want to index. As you can see from the screenshot above, I have entered the name of my server, the name of the database I want to index (note that this is the Data database only, not the security or log database), and then decide on how frequently you want to index your database. Obviously this is up to you based on your requirements, but in the screenshot shown, I’ve selected to index every 5 minutes.
As a note here, for the Server name, if your Instance name is MSSQLSERVER, don’t enter it here.
Once you’ve clicked OK, you should see your details appear in the previous window, and you should see ‘Status’ as ‘Connected OK’.
And that’s it for Search 360. Click Close in the index service configuration. The next time your search 360 is scheduled to run, it will add the latest entities and links etc into your database.

40. Backup – Why did I copy down that database password?
6/26/2018
Backup – Why did I copy down that database password?

41. 6/26/2018
Database Passwords
So why did I get your to write down that password somewhere earlier?
Well sometimes what happens is you try to repoint your database to the new location, but for some reason the utility can’t get to the old security file. This could be because some fool has pre-maturely decommissioned your database, or because the network is down, etc. but don’t panic. That’s what the database password is for.
If you can’t get to the database, the utility will ask you for the database password to prove that you have security administrator permissions for that database. Once you enter the password correctly, you will then be able to enter the new location of your security file. Once you have done this (remembering that we are only using the ids file here), you won’t need to enter the database password again when you come to change the location of the data database, as the utility should now be able to connect to the security files new home on the new SQL Server.
Hopefully that makes sense.

42. Useful Technotes and Links
6/26/2018
Useful Technotes and Links
SQL Server Support message -
Installing the Database Configuration Utility ibm.com/support/docview.wss?uid=swg
Configuring Search 360 Blog - xing?lang=en
IBM i2 iBase Release Notes -
IBM i2 iBase System Requirements - reports/report/html/softwareReqsForProductByComponent?deliverableId=FD3D9A3076F711E4 A5D05AF6B8E6E27F
IBM Passport Advantage – 01.ibm.com/software/passportadvantage/pao_customer.html
IBM Fix Central –
Turn it back over to moderator

43. 6/26/2018

44. Questions for the panel
6/26/2018
Questions for the panel
Now is your opportunity to ask questions of our panelists. To ask a question now: Raise your hand by clicking Raise Hand. The Raise Hand icon appears next to your name in the Attendees panel on the right in the WebEx Event. The host will announce your name and unmute your line. or Type a question in the box below the Ask drop-down menu in the Q&A panel. Select All Panelists from the Ask drop-down-menu. Click Send. Your message is sent and appears in the Q&A panel. To ask a question after this presentation: You are encouraged to participate in the dW Answers forum: <

45. IBM® i2 iBase – Upgrading and Migrating