I've played with Microsoft Bot Composer and have checked the extensibility points but it looks like it is not possible to deploy the bot to other clouds.
Please confirm my assumption.
My goal is to achieve deploying without additional development if possible.
Deploying a Composer bot is somewhat more complicated than deploying an ordinary Bot Framework bot because the Composer bot is not stored anywhere in a deployable state. Composer must bundle your specific Composer project files together with the centralized Composer runtime in order to create a deployable package.
However, Composer does come with a way to convert your Composer project into an ordinary bot project that can be deployed just like any web app. This is called exporting (or ejecting) the runtime. You can find out how to do that here.
To export your bot runtime:
Navigate to the Project Settings page of your Composer and find the Custom runtime section.
From the Custom runtime section, toggle Use custom runtime then select Get a new copy of the runtime code.
In the pop-up window select C# and select Okay. A copy of your bot's runtime will be added to the bot's project folder and can
be accessed in the following directory: C:\Users\UserName\Documents\Composer\bot\runtime.
Related
I'm working with WSO2 Identity Server and I'm curious if there is a way to run the product in developer mode without building each component of identity server. I found a way to start the "My Account" component in dev mode by following this tutorial ( https://is.docs.wso2.com/en/5.11.0/develop/setting-up-my-account-in-a-dev-environment/ )
but I want to be able to modify different components such as recovery-portal and authentication-portal by forking and cloning the required github repositories and starting the entire app in developer mode in order to see the code changes in real-time.
AFAIK the developer mode will work only for the MyAccount and Console. You can refer to the doc for more details on that.
The recovery portal, the authentication portal etc. cannot be tried with the developer mode. However, there are two ways that you can try this.
Build the war files manually and add them to the WebApps directory. If the server is running, war file changes will automatically get deployed. If the server is not running, you have to delete the existing directory and restart the server.
You can do the changes to the JSPs that are deployed inside the pack. Once the changes are done, you can save the changes and the changes will automatically get deployed.
I'm pretty new to the Google Cloud Platform. I have deployed a Python 3 Flask app in AppEngine Flexible Environment using the Google Cloud SDK and the app works fine. I just want to view the source files deployed, in the cloud. Is there any way to view my project files in GCP?
You can view the source files by clicking on tools > debug next to the app version on your versions page
Alternative, you can go to your instances page, click on SSH next to one of the instances and you will enter the debug mode for that specific instance.
This will open a console in your browser and you can start a shell in the container that is running your app, as described here.
PS: apparently this is possible only for the Flexible Environment
I'm exploring MS Azure, and have a very simple one-app Django project that I'd like to use with Cloud Services, but I can't figure out how to do it.
I've got the Node-based Azure cross-platform CLI tools installed, and I'm trying to figure out the process of creating the necessary infrastructure to stick the Django project on Azure Cloud Services (note: not Azure VM, not Azure Web Sites). The tutorials I've seen use Visual Studio to do this, but I'm on Mac/Linux.
There must be a process how to produce the necessary files (.cspkg, .cscfg etc.) without VS, but I haven't found any tutorials or documentation about it. How do you generate or construct those files, and any other boilerplate, without the use of VS, and what's the process of actually deploying the code to the cloud?
best to use is powershell : you'll need "New-AzureServiceProject", "Add-AzureDjangoWebRole" and in the end you need to package it with Save-AzureServiceProjectPackage, afterwards you can upload it either through the portal or through powershell with the cmdlets New-AzureService and "Publish-AzureServiceProject" hope this helps you?
Summary:
I have an Office 365 E3 account where I'm trying to deploy a Word task pane app that will read some SharePoint list data. Right now, I'm just trying to get the task pane app to load, however, it shows the Office 365 login page (in the pane) but does not do anything after clicking Login.
Details:
I went through the instructions provided here:
http://msdn.microsoft.com/en-us/library/office/fp179815.aspx
Basically, I create an App for SharePoint configured as SharePoint-hosted, then in the same project, added an App for Office (Task Pane App for Word only). The SharePoint app also has a custom document library.
I am able to install the app to my App Catalog, and it correctly shows up in Site Contents where I see it being provisioned to the app web. I can also launch Word 2013 with the Trusted App Catalog configured correctly, and I am able to see my Task Pane App and insert it. When I click Insert, it loads it but prompts for credentials.
I am using the same credentials all throughout this exercise so by virtue of being able to install and deploy the SharePoint app, you can trust that I'm providing the right credentials.
It also appears the custom document library is never created - I wonder if both suffer from the same underlying issue.
I encountered the same problem and the solution provided in the answer below did not help.
After some desparation i created a taskpane app using the Napa Cloud App, opened the application in Visual Studio and went looking for differences.
In the Taskpane app manifest.xml file i found the following entries which were missing in my own application manifest:
<AppDomains>
<AppDomain>https://login.microsoftonline-int.com</AppDomain>
<AppDomain>https://login.microsoftonline.com</AppDomain>
</AppDomains>
This solved my problem and cured one horrible friday.
I was able to get this to work. It turns out doing a Deploy from Visual Studio (whether you right-clicked Deploy or F5-debug), the installation of the app isn't enough.
To make it work, I skipped doing a Deploy all together, but instead published my app. I then took the .app file and loaded it in my App Packages folder, and then deployed it from there.
Unfortunately, I don't know the difference between the two, but I'm assuming it has something to do with provisioning the app web for the Office App.
I have used Spring Template Project to create a Spring MVC Project. It works fine running it on the "VMware vFabric tc Server Developer Edition v2.8"-server. But when I move it to the Tomcat server and I try to run it it doesn't work. When I try to access the site I get following:
HTTP Status 404 - /analyse
type Status report
message /analyse
description The requested resource is not available.
Do I have to convert the project some how? It doesn't have the same structure as the other projects in the webapps-folder.
Any idea?
So basically I need to know what has to be done in order to run my Spring MVC Project on my Tomcat-server.
Aprreciate any help I can get!
What is the name of your *.war file?
Typically you can access your app via a URL by the same name, minus ".war"
The problem is in deployment assembly,you have to check it.
As you are using maven so you can type following command
eclipse:eclipse -Dwtpversion=2.0
so it will solve deployment assembly problem and also download necessary jar's.
Then run command
clean install
and clean the project from
project clean option.
Go to Project --> Properties configure Java, Javascript and Dynamic Web Module.
And now you can access the application in Tomcat Server as well. The problem is in deployment assembly.
Properties Configuration