Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Server Installation
15 views
Skip to first unread message
alaa...@gmail.com
Apr 8, 2013, 1:34:52 PM4/8/13
to
Gentelmen ,
I have to install multiple environments for WebSphere Portal (IHS, WAS and WPS). My question is not limited to WebSphere as it's a general server installation, so I thought to ask what is the best approach to use regarding the portal name/ hostname etc.
Should we use the FQDN or the simply the unqualified hostname. I'm thinking to add an entry to my host file, i.e. "1270.0.1 portal", having the name not related to the machine make it possible to just copy it over another one. in this case my development, uat, production and dr environment will have the installation done as "portal" , any harm in this ?
Currently we are doing the dev & uat environments (exact and no clustering ) , I'm thinking to have them both named "portal" and then for the certificate we can use the FQDN, like this
portal.dev.mycompany.com
portal.uat.mycompany.com
Any recommendation regarding this ?
Thanks in advance.
I have to install multiple environments for WebSphere Portal (IHS, WAS and WPS). My question is not limited to WebSphere as it's a general server installation, so I thought to ask what is the best approach to use regarding the portal name/ hostname etc.
Should we use the FQDN or the simply the unqualified hostname. I'm thinking to add an entry to my host file, i.e. "1270.0.1 portal", having the name not related to the machine make it possible to just copy it over another one. in this case my development, uat, production and dr environment will have the installation done as "portal" , any harm in this ?
Currently we are doing the dev & uat environments (exact and no clustering ) , I'm thinking to have them both named "portal" and then for the certificate we can use the FQDN, like this
portal.dev.mycompany.com
portal.uat.mycompany.com
Any recommendation regarding this ?
Thanks in advance.
0 new messages