How to create application and workspace through script? - sql

I created a workspace provision app, where is possible to create workspace without access to administration services. Now, I want to do the same for applications, to install application on workspace remotely on button click.
How can I achieve this?

Take a look of this tutorial
https://joelkallman.blogspot.com/2018/08/scripting-service-creation-in-oracle.html
But you must need to have sys privileges

You can create the workspace and application by running the script file.
Try to review mentioned link.
https://oracle-base.com/articles/misc/sqlcl-deploying-oracle-application-express-apex-applications-using-sqlcl-and-liquibase

Related

How do we deploy the Backstage App in AWS? What is the deployment architecture work flow?

I am looking how to deploy the backstage in AWS?
I want to know and understand what we have to do if we want to use service catalog of back stage? do we need to write code any back end services, to use service catalog plug-in
Do we need to create the database or the backstage will create? Who creates the database tables?
What do we do if we ant to add another column to the service catalog?
The docs says the backstage is a mono repo? does that mean do we have both the front end and back end development in single repo?
Is there any need or requirement for Java development if we want to use backstage?
I have a lot of other questions, highly appreciated if anyone is using backstage or want to connect and sharing any insights of using the backstage.
That are a couple of questions, let's see if I can help you.
Do we need to create the database or the backstage will create? Who creates the database tables?
Roadie has a nice intro on running Backstage on AWS Fargate. That includes the steps for provisioning an RDS database. In Backstage, each backend plugin that requires a database is itself responsible for managing the database. You provide only the global credentials and the plugins setup the databases by themself (e.g. creating tables, running migrations for new versions).
What do we do if we ant to add another column to the service catalog?
The database structure of the catalog plugin is quite flexible. If you want to add additional data to it you don't have to modify the database. The Backstage documentation provides some details on extending the data model. To display the data, you have to options: You can either create a plugin that provides new display components to display the value. Or you can change the columns of the catalog table. For that you have to modify your Backstage app a bit. I can't provide the full details as I haven't done it yet, but you can pass custom columns into the <CatalogTable>.
The docs says the backstage is a mono repo? does that mean do we have both the front end and back end development in single repo?
Yes, if you create you new Backstage app with npx #backstage/create-app you get both the frontend and backend, as well as an environment for plugin development in the same folder structure. It should also be all set up the create a running container from that that runs the backend and serves the frontend.
Is there any need or requirement for Java development if we want to use backstage?
No, you don't need Java skills. Backstage is written in TypeScript and React in the frontend and TypeScript, NodeJS, and Express in the backend.

Import profile VS Select existing - deployment in Azure app service

I have .net core web application developed in VS 2019 already running in Azure. I installed the VS 2019 in a new system and opened the solution. When I am trying to publish (may be after a simple code change) the application using Visual Studio. The window that is coming up having 3 options to publish. Regarding these options, what is the difference, and when to use what?
Below is the screenshot, options highlighted in red. Create New is for complete new deployment, as per my understanding. However, I'm not able to clearly get, "select Existing" versus "import profile" and when to use what?
Can you download the publish profile from the azure portal for the service in question and reimport it?
The window that is coming up having 3 options to publish. Regarding these options, what is the difference, and when to use what?
1.Create New option enables us to create a new App Service, create or use an existing App Service plan (Hosting Plan) and Resource group within your specific subscription, like below.
If you do not have any existing App Services that you create through Azure portal or VS etc, you can use this option to create a new one before you publish your project.
2.Select Existing option enables us to search and select existing App Services from specific subscription and Resource group.
If you'd like to publish your project to an existing App Service, you can use this option.
3.Import Profile... option provides a way to import publish settings that we got from Azure portal as below and then deploy our app.
Sometimes, developer does not sign in with same account (create Azure App Service etc resources using this account) in Visual Studio, to deploy app to an existing App Service, we can use this option and import a publish settings file.

How can a user access the repository of application with help of an empty Shell component?

I was going through IBM Worklight - Shell documentation, which mentions the following:
A shell can be distributed empty to the user who will then access a
repository of applications stored on the Server.
How can an empty shell be distributed to the user (I assume this not
the developer, but an application user)?
How can a user access the repository of applications with help of
an empty Shell component? Is it related to IBM AppCenter?
Can someone help me in getting the concept behind this?
How can an empty shell be distributed to the user (I assume this not
the developer, but an application user)?
A Shell is made up of a "regular" Worklight project; it's still a project and an application with an environment, so the end result is still for example an Android or iOS application that you install on a device, thus you basically get "an empty shell that can be distributed to the user", like any other application.
How can a user access the repository of applications with help of an
empty Shell component? Is it related to IBM AppCenter?
That is a mystery to me as well.
It is not related to Application Center.

Cannot see option to 'Add Application Insights Telemetry to Project'

I have an existing web role that I deploy to Azure. Now I would like to try out Application Insights but I do not see an option to 'Add Application Insights Telemetry to Project'. I installed all the latest updates and if I try adding another web role project to my Azure deployment that new project has the option to add Application Insights.
Any ideas would be greatly appreciated.
Thank You!
I believe VSIX checks if ApplicationInsights.config is added to the project. If it is present the option to add is not available.
I think I figured this out. Somehow telemetry was already added to my project, and that is probably why the menu option was not available.
I ran into the same problem then found another option called overview after right clicking my project. Option might be available for other people so posting here as I didn't find this information elsewhere.
Right click project > Overview > Connected services > Monitoring with application insights > follow set up with azure account.
Also had to follow this post as .config file didn't add
https://stackoverflow.com/a/38060313/7030091

VB install and SYSTEM user

Hy,
I've create a setup for my vb application with visual studio.
At the end of the install I want to launch the application so i've add a custom action and used the chell to launch it. It's work but... the application is launch as SYSTEM user...
is there a way to launch it in normal user (on win7 as administrator)?
Thanks for your help
If you are installing the application as an Administrator and launching the application, then it will start under that identity.
Try installing the application as a non Admin user and see under what identity the application launches.
If it still requires Admin access, then look at the privileges requested in your config file.