I have a couple of WAR files created from a multi-tiered application on a remote server, that I have deployed on WLS 10.3.6. They deploy but won't start.
I suspect the problem is that the application is trying to refer to files back on the remote server, and that the remote server location is not included in the application war files.
My question is: Is there a way for me in a WLS config file to give a <DNS server name>/<subdirectory> and redeploy the app with that info?
Or does the remote DNS server name have to be imbedded in the WAR file prior to deployment ?
Can you copy it locally ? I don't think there is a way to specific the server name. If you are using stage deployment mode, this may not cause an issue. Try changing the deployment mode "stage" if it is different.
Thanks for responding. The application I'm trying to deploy is multi-tiered, and the piece in question probably needs to stay on the remote server (ie not on the same server as WLS). So I'm going to try to NFS mount the remote directory so that my WLS instance can see it (once it's mounted and put in maybe the PATH statement).
I was hoping for other possible workarounds, or hoping there was a way to tell WLS to look at a remote location (DNS_NAME)/directory_name.