2 Corporate server for same environment- Installation issue

[GaneshDasmale]

Hello Team,

I'm trying to install 2 Corporate servers for same environment while installing second i am getting some issue,

Steps i have followed,

1) I have database server & instance on M/C XXXXC

2) TC_DATA & Volume for both the server should be on M/C XXXXD

2) I have installed first Corporate Server, Server Manager & Web Tier on M/C XXXXA by selecting option 

    "Populate database and create new data directory"

3) Now while installing second corporate server on XXXXB, i have already database which is populated & data directory on XXXXD also exists, so i have selected option

"Use populated database and existing data directory"

4) But the installation failed and gave the message like below

Executing [cd /D "D:\splmlocal\int02\appl\tc112\logs"]
Output from command: cd /D "D:\splmlocal\int02\appl\tc112\logs"
command_exit=0
Exit Status 0, elapsed time 0:00:00
...Done

Executing [preferences_manager -u=infodba -p=***** -g=dba -mode=import -scope=SITE -preference=Mail_server_charset -values="windows-1252" -action=OVERRIDE]
Output from command: preferences_manager -u=infodba -p=***** -g=dba -mode=import -scope=SITE -preference=Mail_server_charset -values="windows-1252" -action=OVERRIDE

Command line login fail! Error code = 515209 (POM_rdbms_error)

The following error has been encountered: 515209 - The operation failed due to an unexpected Database Management System error.
The report file is located at "D:\splmlocal\int02\appl\tc112\logs\1805090745\preferences_manager_20185974731.log".
command_exit=1

[RandyEllsworth]

M/C XXXXC > Database Instance

M/C XXXXD > TC_DATA, Volumes

M/C XXXXA > TC_ROOT, Server Manager (PoolA)

M/C XXXXB > TC_ROOT, Server Manager (PoolB)

M/C XXXXE > TC_ROOT(.Net only), Web Tier

The mistake is selection foundation instead of just selecting server manager. I would install foundation on D where TC_DATA lives. All template deployments or additions would happen on D from then on. Select only the server manager feature when installing A/B. Also, you'll likely want to move the Web Tier to its own server (see attached diagram).

[GaneshDasmale]

@RandyEllsworth Thanks for the response,

But the main purpose of doing this is to have load balancing of the server,

The requirement is to have two corporate servers, don't know why they need it

M/C A --> Corporate server, .Net Server Manager, .Net Web Tier,FSC

M/C B --> Corporate server, .Net Server Manager, .Net Web Tier,FSC

Where M/C A & M/C B should have same port numbers for these services only hostname is different.

M/C D --> Should have TC_DATA & Volume for these both M/C's, Volume server is installed here with FSC.

I think it should be possible because they already have it for dev environment but I need configure it for int environment.

[RandyEllsworth]

That configuration is possible but is wasteful and introduces risk. For instance, what if someone deploys a template on B instead of A? How do you keep the two TC_ROOT's in sync? A lot of hassle for no benefit. Unless you can provide a compelling business case, I think you need to strongly caution them against this configuration and take another look at the diagram I provided in an earlier post which I can easily defend.

Why not have two TC_DATA's: one on A and B then D only has Volumes? Why not have two FMS Masters: one on A and B then D only has an FSC? Yes, all of these are valid configurations but they introduce risk/overhead and need a good ROI to offset the extra work. Understand the business reason(s) and provide solid guidance.

[GaneshDasmale]

I will collect all the data why this is necessary, and may be will come with reason.

I agree with you and the diagram which you have provided in the same way i have configured till date.

The reason they want one TC_DATA directory for both installation because they are using same database instance,

if they use different data directory as well as database instance, then we can not call it as one environment it will become two different environments.

and i dont think TC_ROOT has any entries for deployments except BMIDE projects? so no question of sync?

regarding FSC, they will be having FMS Master only on A, and not on B (but both will have FSC ).

The diagram you shared is the load balancin using multiple Server Manager by having only one Corporate Server.

and what they proposing is load balancing using multiple Corporate Server.

I will check all the details and will share as well

Thanks!

[RandyEllsworth]

For your reading pleasure...

You can have multiple TC_DATA directories, one on each Server Manager, that point to the same DB instance. Best practice for this use-case is to pick one server for updating the data model using TEM and then sync (mirror) that TC_DATA to the other. This avoids issues with UNC or mapped drives being lost. But introduces another task (and point of failure) when making a deployment.

TC_ROOT contains the install directory which keeps track of your deployments and features. Depending on features there can be other files in TC_ROOT that are updated as well (bin, lib, etc).

If I were designing your landscape, I would put the FMS Master on the Volume server. I would also put the Corporate server there since it holds TC_DATA. This is also a good location to deploy single-instance services where only one can exist in an environment (e.g. Action/Subscription/Autonomy) thereby keeping A/B the same.

Welcome to architecting.

[Ekarl]

Hi,

I know this is an older thread, but I came across it as I am encountering the same architectural challenge as the OP, @GaneshDasmale .

First, I found that the Server Manager feature is dependent on TC Foundation (challenging part) and a FSC (easy part), so i do not think it is possible to only install the server manager feature on the business logic servers. At least for .NET architecture, but i think also for java.

This introduces the risk that Randy suggested, that for each additional Server Manager in the pool, there will be an additional TC_ROOT that needs to be kept in sync if you are applying updates etc.. TC_DATA can be pushed from one Server Manager server to the others, so that all have an independent copy of TC_DATA in case of server downtime.

So to the headache of this architecture, is there any good method of keeping the TC_ROOTs in sync?

TC Foundation requires a lot of features (tem won't let you install a second server manager/foundation without adding them) that basically has to be "re-applied" to the database..

If a custom datamodel is updated on OP's A server, it should also be applied to the B server so they are in sync?

Erik

[RandyEllsworth]

You have stated the situation correctly. Siemens has added a method for deploying in parallel.
https://docs.plm.automation.siemens.com/tdoc/tc/12.2/help#uid:xid1256816:index_plm00102:id1683912:xi...

See Patching in parallel...
After patching the first server (corporate), then you can patch the remaining (server managers) concurrently.
https://docs.plm.automation.siemens.com/tdoc/tc/12.2/help#uid:xid1256814:index_server_win:id266001:i...

When you patch your first server, TEM uploads a dataset to the volume that contains key items from the TC_DATA directory. This provides necessary information for patching additional servers. TEM references this dataset during subsequent patching operations, instead of needing an exclusive lock on the Teamcenter database. This allows you to initiate patch operations on your remaining servers at the same time, in parallel. This saves a significant amount of time when updating deployments with multiple servers.