Cancel
Showing results for 
Search instead for 
Did you mean: 

Local Service Port Vs TreeCache Peers port

Legend
Legend
Spoiler
Hello Everyone,

Good Evening...!!!

While configuring the 4-Tier for Teamcenter. I have observed below thing in below two separate steps,

A) J2EE Pool Manager-Tree cache Configuration details are:-

Local Service Port:- 17800
Treecache Peers:- 17810


b) Web Applications settings while generating .ear file:-

Local Service Port:- 17810
Treecache Peers:- 17800

1. What is the difference between these two ports?
2. Why there is interchanging of port numbers in above two separate configurations?Capture.PNGCapture2.PNG
5 REPLIES

Re: Local Service Port Vs TreeCache Peers port

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
Server Manager (17800) and the Web Tier (17810) share the (JBoss) TreeCache to maintain session and transaction information. After you have logged in and been assigned a tcserver, further transactions will direct you to the same tcserver via the shared TreeCache. Otherwise your request through the web tier would fall on deaf ears as it wouldn't know where to route the info. The J2EE solution uses the JBoss TreeCache to keep track.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Local Service Port Vs TreeCache Peers port

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
The word "share" can be misleading. The truth is that Pool Manager has its own (JBoss) TreeCache and the Web Tier has its own (JBoss) TreeCache and the two are sync'd. Effectively, they have a shared cache but they are separate.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Local Service Port Vs TreeCache Peers port

Legend
Legend

Thanks a lot Randy, I got some clarity by your answer...

But still i have confusion why they have interchanged port numbers for Treecache peers?

 

Pool Manager                                                    Web Tier

17800                                                                  17810

 

 

TreeCache                                                          TreeCache

17810                                                                  17800

 

I mean they would have used 17820 and 17830 for tree cache pears..

 

But there must be some communication between the same ports?

 

Re: Local Service Port Vs TreeCache Peers port

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
It's for communication. Pool Manager is on 17800 and "listens" on 17810 for incoming requests while the Web Tier is on 17810 and "listens" on 17800. Interconnected so they can "sync" their TreeCache.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11.0.1.mp01 | SW 2016 | TcUA 11.2.3
Evaluating:AW 3.2

Re: Local Service Port Vs TreeCache Peers port

Legend
Legend

Yes Randy Exactly, Thanks i got the clear idea now...