Okay, changing the setting in setupCmdLine.sh to
ITP_LOC=/opt/WebSphere61/Profiles/dmgr/deploytool/itp
and copying the contents op /opt/WebSphere61/AppServer/deploytool/itp to this
directory SOLVED the problem. (Ofcourse had to restart dmgr to update the
environment variable).
The deployment too
> 1) Ensure that the wasprofile.properties file was edited to point to
> /opt/WebSphere/Profiles directory as described in the paper before you
> created the zones and profiles
The white paper states that you should change the following
Before: WS_CMT_LOG_HOME=${was.install.root}/logs/wasprofile
All,
I have set up a new environment with Solaris 10 x86 Zones and WebSphere 6.1
Network Deployment. The known whitepaper is used as baseline for the
installation.
After implementing the whitepaper the three zones (dmgr, app1, app2) all run
fine but then deploying a new application that uses E
