The connection definitions with GEN_ are created during upgrade processing. These should be renamed to a meaningful name.
For more details on connection definitions, see article What is a workgroup server connection definition?
Since connection definitions were new with 10.1.5, the names for them were generated from the existing attributes. The WGS name itself could not be used because multiple users might have the same WGS defined in different ways. So the upgrade generated a name GEN_ followed by the IP, host and port. In many cases, all you will need to do is rename the definitions. To do this, go to the workspace and click on the Manage Workgroup Servers icon.
This will bring up the list of all WGS connections that have been defined. These include any that any users created before 10.1 was installed.
You can see the generated names, as well as details about the connection. In the example above, the first one is defined to connect to 127.0.0.1 (loopback) at port 4010 and the 2nd and 3rd connect to a second workgroup server, but one of the definitions uses the host name and the other the IP. We will review what needs to be done for each.
This one just needs to be renamed since it is the default connection and all attributes are correct. The name does not matter from a connection perspective, and could be the WGS name or a more friendly name. In this case, we will use the WGS name. To modify the name, select it and then click on the Modify icon.
You can then change the name and click OK to save changes. Since we are modifying an existing one, there is no need to verify the connection.
Most customers will be able to stop at this point because they are using default connections, but for some users that have multiple WGS and non-default connections, the remaining sections covers examples they might encounter.
This is an example of definition that was manually added and is not a default connection. It is the one that we would prefer to be used, since it uses the host name. If any users need to connect to this instance, we want them to be able to recognize it so will call this one Production.
As before, we do not need to verify the connection at this point and can just click OK.
As noted, this is actually the same as the Production WGS connection, except that the user that created it, used the IP address and not the host name. As noted above, we would prefer to use the host name. There are 2 options for this one. First, we could rename it to something like Production_IP or second, we could remove it. The first option is not desirable because it would be confusing so we would like to do the second. However, before we delete it, we need to reallocate any viewlets that use this connection to the Production one. To do this, we use the Reassign viewlets function.
We then select this connection from reassign from and Production to assign to and press Next. This will provide a list of all viewlets in that connection and their type. Since we are going to remove this connection, we will Assign All and continue by pressing OK.
Once we do this, all viewlets will be moved from this connection to production.
Now that this connection definition has no viewlets assigned to it so it is safe to delete it. To do that, we select it and then select Delete.
Users that had were using this connection will not get it automatically. They will see their dashboard, but no viewlets. They will need to add the new connection to their connection list, see Adding workgroup server connections.
We can now exit this dialog and logout. Logging out after making connection definitions is required.
After logging back in, you can verify you got the expected results and users can begin to use the newly created names.