@Wayne Westlake Thank you for the detailed response!
TLDR; I believe my issue is/was related to a PATH variable pointing to the transformer/bin directory. I can now confirm that the separate installs have worked which is great.
I installed FM and Transformer in their separate directories as Administrator and I was able to open their individual configurations and point them to the controller/dispatcher sitting on the same server.
I was subsequently able to reproduce the error when trying to open the main IBM server configuration - the dreaded java.lang error but this time I knew what I changed beforehand - it was a path variable. We use Transformer's PCACTIVATE.EXE in a Windows Powershell script to do a seamless cubeswap but the command wasn't working. During troubleshooting I added a PATH variable to the transformer\bin directory and upon reboot, I wasn't able to open the IBM server configuration.
We use this PATH variable in our C10 environment but because PCACTIVATE sits within the main bin directory, perhaps this is why we don't encounter this error in C10.
But for now, it seems to be working. Thanks for your help.
------------------------------
Mark Peterson
------------------------------
Original Message:
Sent: Tue August 04, 2020 01:15 PM
From: Wayne Westlake
Subject: Installing all C11 components on same server possible?
Hi Mark!
Yes, we have all of C11 installed on the same Win Srv (ver 2016). It was a little tricky to get the clients to work and I had to open a ticket. It was easy as you noticed in C10 but quite different in C11.
As a first step, as you've done, definitely install everything in its own directory. We actually use the default directories.
Of course with each client in its own directory, each has its own Configuration. Also one tip, the first time I launch the configuration I do so as Administrator (just right-click and "Run as Administrator"). Early versions of 11 seemed to have problems initially writing to the registry if you weren't using Administrator. Once you do that and save then the next time you need to make a change you can just use your normal login (though the login we use for cognos is a member of the local administrators group).
Now in the configuration for FM, these are the Environment settings I had to use:
Gateway URI: http://hostname.domainsuffix:80/ibmcognos/bi/v1/disp (which is exactly matches our server's configuration)
Dispatcher URI: http://hostname.domainsuffix:9300/bi/v1/disp
I just tested and this still works fine in this latest 11.1.7 release despite some of the initial issues we had with the server common name, etc.
If you still have issues don't hesitate to open a support tickets with IBM.
Hope this helps!
Wayne
------------------------------
Wayne Westlake
------------------------------