How do we deploy a webapp in the new AppWorks platform?
We have been able to successfully a mobile app (compressed package), but we need the ability to deploy webapps also that are accessible via a URL. For example, https://www.myworkday.com/m.htm.
Great question Kevin, Web apps are just part of the application package in AppWorks. When you zip up you app payload (index.html, assets, javascript, etc) you zip it into a file called "Mobile.zip". You do the same for web, and call it web.zip (the difference being any web or mobile specific features - ie: the web app may not call cordova).
Then both the web, and mobile zips are zipped once more with a properties file and icon for appworks and deployed to the AppWorks Gateway. By default the web app version for browsers will be available at http(s)://<yourserver.com>/webaccess/
Let me know if that helps!
Adam,
Thanks for the prompt response, but I am not sure I follow your response. Is there a walk-thru like there is for the mobile.zip app install.
These webapps are external (third-party) HTML5 apps that we only have access via the URL, so we do not have the ability to package up source like we did with the mobile.zip app install. Does that make sense?
We only have a URL to this webapp that we need to deploy via the AppWorks runtime. For example, https://www.myworkday.com/m.htm.
Can you also please elaborate on this "By default the web app version for browsers will be available at http(s):///webaccess/" - are you saying we should be able to also access our apps outside of the AppWorks runtime, just via a browser? If so, can you please elaborate?
Kevin,
This site is an example of a web app as Adam described it above.
If you can't package the HTML of the site because it is third party or SaaS or is generated by a dynamic language (ASP.Net or JSP) you have at least these alternatives:
Best,
Tim Davis - OpenText Professional Services
Tim,
Thanks - what if neither of the options you have presented are a viable option? Could we not just 'link' to the third-party app within the runtime app. IE - have an installable 'link' (app.properties, icon.png, and 'link' vs. installable HTML) to this third-party app where we could control access to the 'link' of this third-party app via the admin ui?
Does that make sense, and would this be a viable option?
I believe "Shortcut" apps are the solution here.
If you do this you'll now have an app show up on mobile devices which will bring up the configured URL when clicked. If the site is on a different domain than the AWG it will open in a local browser without access to any session information from AppWorks. This hosted app will also not be able to make cordova calls inside the AppWorks Client.
Is this more what you were looking for Kevin?
Alex,
Yes - this is along the lines of what I am looking to accomplish. I was able to install the app via the admin ui using the following details in the app.properties file.
However it is throwing an error - "Unable to launch application".
Any ideas?
app.properties:
displayName=Workday
description=Workday
url.default=https://www.myworkday.com/m.htm
releaseNumber=1
minimumClientVersion=1
type=shortcut
Any ideas - how to resolve this errors? Alex and I worked through this and we thought it might be an out-dated runtime (app) on my iOS devices. However, that did not resolve the issues and I need to demo these shortcut type apps ASAP.
Hi Kevin,
Since both your app and mine work in our test environments (iOS and Android) would it be possible for you to: 1. Try running the app in Android (apk is available for install on the download page). 2. Update your server to the shipped version (also available on the download page).
