Original Question:
Hello all,
We are using Pro INTRALINK 3.4 M030 and Pro ENGINEER Wildfire 3 M110.
We have two INTRALINK Server Environments, one is a Production
Environment and one is a Test Environment.
On a Client machine, When switching between INTRALINK Production server
to INTRALINK Test server using the "tnsnames.ora" file in the <
INTRALINK Client Load Point > and Logging on to the INTRALINK, I can see
what Environment I am in.
In the Production Environment I can see in the administration tool that
the name of the Data server is "proi-vlt", see attached
"Production_Environment" Picture.
In the Test Environment I can see in the administration tool that the
name of the Data server is "proi-tst", see attached "Test_Environment"
Picture.
Each time, I'm Launching only one Client after I've changed the
"tnsnames.ora" file and set the Environment Variable "PDM_LDB_PATH" to a
different location, I made sure that there is no mix-up between the
".proi" folders, So far so good.
why is it that when Launching Pro ENGINEER from the INTRALINK Client, it
will always show on the top of the Pro ENGINEER Window that the name of
the server Environment is "proi-vlt", see Attached "Proe_Window"
Picture, even when I'm Launching the Pro ENGINEER From INTRALINK Client
Connected to the Test Server? What is the meaning of that?
Please Advice.
Thank you
GILAD
Orbotech, Israel
Responds:
That is hard-coded in the database and cannot be changed (so far as I
know). It will not cause you any errors other issues. Ours still
references a server that has been sent down the road many years ago.
It look like that the test environment have been made as a copy of the
production env.
When a Intralink server is replaces then somewhere in the system it
still think that the host in the orginal name.
I have several single site servers made from the same dump file. The
server name are different but intralink in some places use the old name
from the dump file.
I don't know if this is a bug or not, but it is working.
