Open topic with navigation

TIBCO GridServer® 7.1.0

# After Installation

## If Using System Classloader for Engines

If you are using the system classloader in your Engine configuration and deployed the `DSEngine.jar` file to Engines, deploy the new `DSEngine.jar` to Engines after upgrade. This is now deployed in `DS_MANAGER``/webapps/livecluster/engineUpdate/shared.` If `DSEngine.jar` was deployed in the default resources directory, it has already been removed. If it was deployed to any Grid Libraries, you must remove it from them.

## External Database JDBC Drivers

If you are using an external database, copy the required JDBC driver JAR archive from `DS_MANAGER``/webapps/livecluster/WEB-INF/lib` in the old installation to `DS_MANAGER``/webapps/livecluster/WEB-INF/lib/` in the new installation.

## LDAP Upgrade

As of GridServer 6.0, Driver profiles are no longer supported. The `allowedBrokers` property has been replaced by the value of Manager List in the security role assigned to the Driver user. Also, users are now allowed to execute Services based on the “Execute Services” permission rather than by virtue of having a profile.

During upgrade, a new role is created for each Driver profile. This role has execute permission, and maps the “Allowed Brokers” field to “Manager List.” That role is added to each user who has the corresponding profile.

You are not required to maintain these converted profiles; you might choose to reorganize and remap these roles as you see fit.

If you use LDAP authentication and you prefer to assign roles via LDAP groups, you must add those groups to your users in LDAP, and remove the locally assigned roles.

Users and roles are logged during the upgrade to the file `DS_DATA``/logs/newRoles.txt`, so that you have a list of groups to add the user’s LDAP entries. It is a flat file with the following format:

    [user]\t[role1,role2,...]

For example:

    joe driver_developers,driver_boston
    tom driver_testing,driver_london

## Engine Upgrade

| • | For UNIX Engines, `bin/invokeRA` cannot be automatically upgraded. After upgrading, you must manually copy the new `bin/invokeRA` to the upgraded Engine, and follow the instructions in “Using Run-As” in the TIBCO GridServer® Administration.

## Driver Upgrade

| • | Download the new version of the GridServer SDK in the GridServer Administration Tool.

| • | Make sure that all Drivers are upgraded. This simply involves replacing the libraries or executables with the new version.

| • | If you have existing CPPDriver applications, relink them with the new libraries included in the SDK.

| • | On the Driver side, link your code with the `dsUtil` library. Link Engine-side Service code with the `dsUtil` library if it uses any exception classes.

Note:

After the server is upgraded, you can secure the `Internal.script` and passwords stored in the `installation.properties` file at `DS_DATA\conf`. For more information, see Securing Passwords and Internal.script in the TIBCO GridServer® Manager Installation Guide.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO GridServer®

Copyright © 2001-2022. TIBCO Software Inc. All Rights Reserved.