/*sebthom-start*/?>/*sebthom-stop*/?> Posted on 6 July 2009 /*sebthom commented out: */?> 4 comments
Recently I had to setup some WebSphere Portal 6.1 installations in VMWares within a private network. Unfortunately the portal installer aborted with the following message “EJPIC0067E: Portal requires a fully qualified host name that is recoganized by the DNS Server.” Even when adding the fully qualified hostname to the hosts file the installer may still fail with the same message.
The workaround is to disable the hostname check by invoking the portal installer with the following parameter specified: -W nodeHost.active=”False”. You should however only do this for test or development installations.
/*sebthom-start*/?>/*sebthom-stop*/?> Posted on 19 September 2008 /*sebthom commented out: */?> No comments
With WebSphere Portal 5.1 a new deployment option was introduced that allowed the installation of WP onto an existing node managed by a deployment manager. AFAIK the main reason for this new option was to simplify the cluster setup procedure.
Both options, installing WP standalone and federating it into a cell afterwards as well as installing it on an already managed node have different pros and cons each. In WP 6.0 the installation onto a managed node was even mandatory to enable WebSphere Process Server integration.
Surprisingly WP220.127.116.11 does not support the installation on a managed node anymore. All nodes of a cluster need to be installed as standalone systems first and then be federated into a WebSphere cell.
For WP 6.0 the installation procedure is described here. The 6.1 info center does not mention this procedure anymore and it no, it was not dropped accidentally.