I installed the perspective Plugin succesfull in my vCO Appliance and logged in through the website to perspectives successfully but if I try to create my first perspective I got the following error
Error in io.bind of vmo.displayWebform: XMLHttpTransport Error: 500 Internal Server Error(type: error)
It is in /opt/vmo/app-server/bin/
Christophe.
The vCO 4.2 appliance has a number of security fixes for avoiding cross site scripting. One consequence is that some url have been escaped leadin gto this error 500.
Perspective should work OK on the Windows version.
One thing you can try is to make it work on the appliance is to edit the orchestrator.sh file in the bin directory with adding -Dwebview.raw.enabled=true java option.
Note that this is unsupported configuration and should not be used in production.
Christophe.
Hi Christophe,
thx for your fast response but I cannot find the orchestrator.sh file in /bin
edit: OK I found the file but where exactly do I have to place this option?
It is in /opt/vmo/app-server/bin/
Christophe.
You need to add this option to JAVA_OPTS
Christophe.
So I did the change and rebootet the VM now the perspectives page isn' t found anymore:smileyconfused:
Odd, the change you did should have brought the appliance one step closer from the Windows version making it more compatible.
Do you mean the webview is not listed or that the link to the webview is not working ? What about the web operator webview ? Is it working properly ?
Unfortunately I have work to prepare and will be busy until the end of the week so I cannot really spend time to investigate this ATM. Maybe some other people can chime in and experiment.
Christophe.
Try to start the "Perspectives" webview manually from the webviews tab in the vCO java client.
It's probably just gone down during the restart.
I don't think something happened to the whole plug-in, more likely it's only the webview.
Otherwise, the property described by Christophe should do the work.
Thanks to chime in Ivan
Ivan is the person who troubleshooted this issue I reported and found the work around.
Christophe.
Thx for your support today it works