I am trying to develop a web view through the Orchestrator Client as per the documentation. We are running version 5.5 of vSphere and Orchestrator. We are using the appliance version of Orchestrator. The problem I'm having is getting my new content published. I have tried several different things.
First, with vCO not in development mode, I exported my web view, made some changes, imported the changes, saved and then published the web view. When I try to browse the web view the new content is shown, it continues to show the old content. I've found that if I restart the vCO service then the new content is shown. Obviously, that's not ideal since every time I restart the service it kicks me out of the client.
Second, I've tried to enable development mode by checking the box and putting in a Web view directory value in the Orchestrator Configuration interface. No matter what I put in for the directory when I try to browse to the web view I get a message stating that the directory doesn't exist. All the paths I've attempted have been file shares located on our network. I'm sure if I used a path on the server itself it would work. The problem with that is that I don't have access to the file system on that server. The system admin I am working with attempted to configure SCP on the server but was unable to get that to work. We're guessing that it didn't work because the Orchestrator Appliance is a SUSE Linux installation with a minimal install. We also trying mounting a Windows share from the vCO server but that was unsuccessful as well.
While the documentation for this product seems to be quite detailed and useful, it completely lacks any information related to the appliance version of Orchestrator.
Can anyone provide any assistance in getting either of the options above working?