![ibm notes traveler server url ibm notes traveler server url](https://img.yumpu.com/33845332/1/500x640/lotus-notes-traveler-8511-installation-installing-lotus-notes-.jpg)
Ibm notes traveler server url driver#
After downloading the driver package, shutdown the Traveler Servers, extract and copy the JDBC driver to the “\Traveler\lib\” directory.
Ibm notes traveler server url download#
Just download them using the URL in the official documentation, and you are good to go. This is not a big deal, as there are only a handful of settings involved, take note of them before moving to the new database and do not forget to apply them once you have moved to the new enterprise database.īefore configuring HCL Traveler to use the new database on MS SQL, you will need to download the appropriate JDBC driver for the MS SQL. One important thing to keep in mind is that all the settings in “LotusTraveler.nsf” Database (HCL Traveler Administration Database, accessed only via HTTP/HTTPS) will be lost after migrating to the new Database. This is useful during the migration, as you can see the impact on the users during the process and verify that everything is running smoothly. I usually to this using a “UDL” file, as described in the separate post.Īfter the database is created and the connection is tested, I strongly advise configuring at least two test devices, using the same settings and the same application as the majority of the users are using at the customer site. Consult the official documentation for the appropriate SQL Server permissions.īefore proceeding with the next steps, make sure to test the connection to the SQL Database, using the service user you created earlier. After that you should create a new service user solely for the traveler connection, this user should have appropriate rights to the database/instance. In our case it was the port 1433, but you may need to check your database server settings, as this may differ depending on the configuration and/or technology used. We decided to continue with a simple move towards another enterprise database, meaning that the end user devices will have to “re-sync” most of their data again, this could be an issue in a larger environment, so when in doubt start with a PoC environment and plan accordingly.įirst thing to do is to create a new SQL Database and open up the needed Firewall ports to access it.
![ibm notes traveler server url ibm notes traveler server url](https://img.yumpu.com/33845006/39/500x640/lotus-notes-traveler-lotus-notes-traveler-developerworks-lotus.jpg)
Although the database is not so complicated, and it may be possible to write your own tool for “low-level” SQL Data migration towards another enterprise database (this is just a thought of mine and I have not tried this out). Nevertheless, the move towards another enterprise database was desired by the customer as long as there was no action needed on behalf of the users (entering their credentials again for example), this means that the ActiveSync devices will need to resynchronize their data after the move.ĮDIT: There are also no tools to migrate the HCL Traveler data from one enterprise database to another. The customer is using Microsoft SQL for all other applications, which is set up with redundancy and high availability in mind, so this was a sensible choice, opposed to running a single instance of DB2.ĮDIT: A migration of the Traveler data, inside the enterprise database, is currently not supported, and I do not know of anyone who has done it successfully. One of my customers wanted to migrate the HCL Traveler Database from IBM DB2 to Microsoft SQL.