Page 1 of 1

TM1 Web Component on Separate Physical Server

Posted: Wed Jul 29, 2009 2:25 am
by appleglaze28
Has anyone tried deploying TM1 web with the IIS and necessary components installed to a Web Server being utilized by other application? If so what configurations are needed and where?

I was hoping this could solve my issue on the TM1 missing the username & password on the initial webpage since its running on Serve 2008.

Re: TM1 Web Component on Separate Physical Server

Posted: Wed Jul 29, 2009 10:18 am
by David Usherwood
Might do - but I believe that Server2008 isn't (yet) supported by Iboglix.

Re: TM1 Web Component on Separate Physical Server

Posted: Wed Jul 29, 2009 10:29 am
by Alan Kirk
David Usherwood wrote:Might do - but I believe that Server2008 isn't (yet) supported by Iboglix.
Yup, you speak the truth. Alas that horse ain't just dead, it's buried.

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 12:45 am
by appleglaze28
Has anyone tried it even if its not on a Server 2008 OS? Like Server 2005. I'm not sure what configuration needs to be, I can't find it in any documentation.

Since it might be possible to have TM1 Web running on a separate server. Would it be possible to connect the TM1 Server existing in Server 2008 to a Web Server running on Server 2005?

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 12:56 am
by Alan Kirk
appleglaze28 wrote:Has anyone tried it even if its not on a Server 2008 OS? Like Server 2005.
There IS no Server 2005. There is Windows Server 2003 (which is supported) and Windows Server 2008 (which is not).

There was an SQL Server 2005, which is a database application, not an operating system.
appleglaze28 wrote:I'm not sure what configuration needs to be, I can't find it in any documentation.
That's because It (Server 2008)-Is-Not-Supported. There will be no documentation for an unsupported configuration.
appleglaze28 wrote:Since it might be possible to have TM1 Web running on a separate server. Would it be possible to connect the TM1 Server existing in Server 2008 to a Web Server running on Server 2005?
Not considering that Server 2005 doesn't exist, no.

I know that this is a really radical idea, but if you were to get some Windows Server 2003 disks and install them as your server operating system instead of Windows Server 2008, then you may find that there's no longer any need to ask questions like these.

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 1:10 am
by appleglaze28
Thanks for correcting me, I typed wrong since I'm currently working on MS SQL Server 2005 at work.

I'm just trying to figure out if its possible to have the Web in Server 2003 since every probably run their web in it 2003 and I just want to narrow down possibility of utilizing 2008 sever for TM1 and have the TM1 web component be installed with a existing web server.

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 1:23 am
by Alan Kirk
appleglaze28 wrote:Thanks for correcting me, I typed wrong since I'm currently working on MS SQL Server 2005 at work.

I'm just trying to figure out if its possible to have the Web in Server 2003 since every probably run their web in it 2003 and I just want to narrow down possibility of utilizing 2008 sever for TM1 and have the TM1 web component be installed with a existing web server.
Uh-huh. Typos have a habit of happening once rather than twice but leaving that aside, Windows Server 2008 isn't a supported environment for the TM1 application itself either. So if you want to insist on using that operating system, you're pretty much on your own. I'm sure you'll have lots of fun, for certain values of "fun". Good luck!

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 11:56 am
by lotsaram
Alan's patience has deserted him, and I can't say I blame him as you do seem determined to make life as difficult for yourself as possible. But to answer the intent (rather than the literal reading) of the question yes you can a TM1 web server running on a separate physical or virtual server on a different OS to the TM1 database server. In fact it is reasonably common to have several web servers connect to a single tm1 database server. Just install the web components without the database or client components on the web server (and make sure the appropriate versions of .Net and IIS in that order are installed on the web server prior to the TM1 install.)

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 1:35 pm
by Steve Vincent
Also check the PDF guides that get installed with TM1. the admin guide goes in to quite a lot of detail about system architecture, including a pretty diagram of a complete setup. You seem to also be able to run a UNIX system with apache to also serve the web end, it doesn't have to be Windows and IIS :)

Re: TM1 Web Component on Separate Physical Server

Posted: Thu Jul 30, 2009 9:13 pm
by Alan Kirk
Steve Vincent wrote:Also check the PDF guides that get installed with TM1. the admin guide goes in to quite a lot of detail about system architecture, including a pretty diagram of a complete setup. You seem to also be able to run a UNIX system with apache to also serve the web end, it doesn't have to be Windows and IIS :)
I'm assuming that you're looking at the 9.0 documentation, and I'm guessing that you're taking that from the implication of the following statement on page 1-16:
The TM1 HTTP Connector, when implemented on a Windows Web server, supports SSL. SSL is not supported on UNIX Web servers.
The 9.0 Admin guide does mention being able to use Apache Tomcat with the HTTP Connector, but since the 9.1 SP3 Release Notes mention that support for the HTTP Connector will be "discontinued as of the next major TM1 release" that's not a basket I'd be putting eggs in.

Interestingly the 9.0 Web guide specifies that the O/S has to be Windows, though we know from a recent thread that the manuals are sometimes... of questionable accuracy. However the supported software page on the IBM web site is fairly unambiguous about it; it explicitly mentions Solaris / AIX for the application, but omits them under the Web heading. Mind you, it states that Firefox 2.0 is supported as a browser as well and I know from experience how well that works.