Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations IFRs on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using TCCS with NX

Status
Not open for further replies.

kirlek

Automotive
Aug 24, 2012
6
Hi,

We need to use a proxy to connect over the internet from a NX client to a Teamcenter server. I think that this can only be done by TCCS.

I have installed TCCS. TCCS starts and connects to the fcc without any problems.

But when I try to start NX using: ugraf -pim=yes -u=username -p=password -tccs_env_name=our_env_name
NX gives a messagebox saying: SOA: Failed to get the TCCS Environment. Received TSP Exception with no message string.

Does anyone have any ideas on what the problem could be?

/Erik
 
Replies continue below

Recommended for you

I solved it!

Starting the tccs manually with starttccs.bat showed:
ERROR - None - 2013/05/08-08:55:11,554 UTC - A0165 - Mismatched TCCS_CONFIG_HOME
:
Client: C:\ProgramData\Siemens\cfg\tccs
TCCS:


Setting the environment variable TCCS_CONFIG_HOME for starttccs.bat solved it and now NX is connected to TC via TCCS and proxy.

Also the documentation for TCCS_CONFIG_HOME is wrong in Tc9, see PR #:1898782.

/Erik
 
A new problem has emerged...

It seems that the FMS uses HTTP 1.1 to communicate and our proxy does not support that.

Does anyone know if it is possible to change it to HTTP 1.0?
 
Try setting next variable in cmd screen :

set UGII_UGMGR_COMMUNICATION=HTTP

Best regards,

Michaël.

NX7.5.4.4 + TC Unified 8.3
Win 7 64 bit (Intel(R) Xeon(R) CPU X5650 @2.67GHz)
24.0 GB
NVIDIA Quadro 4000 + NVIDIA Tesla C2050

 
Thank you for your reply Michaël. But I think that that variable is only used for direct connections and not with the TCCS.

HTTP 1.1 might not be the problem after all, even though the proxy error message led me to believe that.

The actual error from the proxy is "HTTP/1.0 400 Bad Request"

This is the request from the FCC/TCCS:
GET HTTP/1.1
User-Agent: FMS-FCC/9.1 (bd:20120302)
X-Ticket: 70def0a3a8d721e782e55ce41a954cda3a7c9a24856dcac07f04b8ebea6bcac8v1004F00000000000012ae00001d5fa53ca45a2013%2f05%2f15+13%3a41%3a25-1522752422+++++++++++++++++++++soa+++++++++++++++++++++++++++++01030000000ca53ca45a++++++++++++%5cengineering_50780ad1%5c000020__ug__cvi06wo4s729l.qaf
X-Policy: NX
Proxy-Connection: Keep-Alive
Host: localhost:8080


At the end of X-Policy: NX there is a NULL. Checking the TCCS log with level debug reveals that it sends "X-Policy: NX[0x0][\r][\n]". 0x0 is NULL and this makes the proxy throw an error.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor