A definitive issue for distributed AM/AS deployment over node agent

I have experienced issues to deploy AM over AS 8.x via remote node
> agent. I have AS DAS admin server and node agent seperated deployment
> use case. AM is deployed from a remote AS instance via node agent
> AS central deployment repository is located at DAS admin server which
> is remote to AM server AS instance.
>
> I am using amconfig -s silentfile post installation configuration. It seems
> AM DIT are able to create in DS repository. However, AM specific web
> app war file has issues
>
> (1)
>
> -- # /opt/SUNWappserver/bin/asadmin deploy --user admin
> --password ll5129427 --host v1280-137-06.mdelabs-mpk.com
> --port 6666 --contextroot amserver --name amserver
> --target jesswitch-cluster /opt/SUNWam/amserver.war
>
> CLI171 Command deploy failed : Deploying application in domain
> failed; Error loading deployment descriptors for amserver
> -- /etc/opt/SUNWam/dtd/sun-web-app_2_3-0.dtd (No such file or directory)
> ; requested operation cannot be completed
>
> Since on DAS server, there is no AM deployment, therefore
> /etc/opt/SUNWam/dtd/sun-web-app_2_3-0.dtd does not exist
> on DAS server. I know I can manually copy over to DAS, any work
> around done to ensure the amconfig works in AS/AM distributed
> environment ?
>
> (2) all other war file deployment shares the same issue
>
> (3) jvm configuration change create-jvm-options
> has the issue too.