First let me introduce what my role is and what we are trying to do. I am the solutions architect and belong to a DevOps team. We are trying to migrate an existing TeamCenter 188.8.131.52_a01_3 and ActiveWorkspace 3.2 environment from a series of physical hosted systems over to Amazon AWS as part of the corporate cost-out initiative (i.e. help save the company money not relying on company-owned datacenters anymore).
The end game/solution will allow for us to provide the application support team a way to fully automate the Teamcenter environment, using Scalr, Chef and Github to be able to setup the instances, configure the infrastructure/OS servers, install the Apache / JBosss apps in the web tier and deploy the WAR files. We wil also be able to automate the enterprise tier in a similiar fashion, using silent installation, as needed for scaling up or down the TCs, depending on load of the web and application servers and whatnot. Hopefully.
So after conversing with the present TeamCenter PLM support team, we are trying to come up with a plan of action on what steps are needed to migrate the environment over to Amazon AWS. They were nice enough to provide us the PDFs for TeamCenter 11.2 installation, but making sense of these things is a whole another ballgame.
As a proof of concept (so our team can see what's involved and resources needed), I have setup an EC2 RHEL7 instance in our AWS environment. Problem is, now I am confused after reading (and re-reading) the UNIX/Linux installation guide. It seems the guide (written like a 'choose your own adventure') seems to be geared more for physical based systems rather than virtualized environments or even cloud solutions.
So my question is, has anyone installed/deployed the TeamCenter 11.x application to a virtualized environment or better yet, Amazon AWS (or any other cloud environment)? If so, would they mind helping with what needs to be setup and the order steps? We are wanting to use an Oracle RDS instance for the Oracle database, but the installation steps under the Foundation Database part is looking for a Database Path as if it exists on the local system (which it doesnt) and Database Paths don't exist within RDS. So we are a bit stuck on how to proceed.
Foundation Database screen... for setting up a new database, I am stuck.
1st Option: Create and populate database, create new data directory.
It's looking for a database path (i.e. ORACLE_HOME/oradata/Oracle_SID). We don't have one as we are planning on using a Oracle RDS instance (managed by Amazon). Is it possibly looking for something else or what is this?
2nd Option: Populate database, create new data directory
It's not liking it since the username of the RDS instance is the 'system level' one. We aren't DBAs and we have no tools to connect to the Oracle RDS instance and create a 'username' it's asking for.
3rd Option: Create new data directory using existing populated database
Same result as 2nd Option above.
4th Option: Use populated database and existing data directory
Data directory doesn't exist, so it can't do anything.
Currently, I am using the following two Linux zip files:
I downloaded the Tc11.2.2_lnx64.zip and the Tc11.2.2_patch_1_lnx64.zip, but haven't unzipped them yet. Do I need to do that as well or wait?
Do you happen to know which ports or configuration values need to be altered to allow 4 tier communication through an AWS ELB? I have the SLPM Licensing working as well as the help docs. The issue seems to be name resolution with the local host WINXXXX for the .net web tier services and the public ELB amazon name. Is proxy forwarding required? Forgive me as I have only ever setup a LAN side deployment and never needed Proxy values. Everything is working locally on the Corp Server.
just an FYI I have added the publix AWS ELB name to the .Net Web Tier/Server Manager/FCC Parent values with no change. I am almost certain this is an Amazon resolution forwarding issue but I am not an Am,azon expert, just learning that as well. I am working with an AMazon VAR also and they are stumped.
Yes, it was an FCC screenshot as the entire 4 Tier structure is failing. 4T/Thin CLient/FCC. The Solr service is working 8282/8283 so HTTP and name resolution are functioning from that perspective. That is why this is so puzzling as part of the communicatrion is successful while others are not. Yes, in retrospect the DNS alaises would have been better; though I cannot go backwards at this point. Thanks for the reply, if I figure it out I will keep others posted (literally LOL)