I got started with oracle apex 5 and lately finished apex installation, I want to start building first application. I found in apex documentation that I should start with application builder but I didn't find it in my environment.
When I login to APEX, the environment appears as in this image:
You are logged into Oracle Application Express Administration Services (apex admin short) and not Application Express Workspace.
Apex Admin is the place where you manage Oracle Application Express instances and work-spaces and a workspace is an area within the Oracle Application Express development environment where developers can create applications.
If you just finish installing APEX I suggest you go over this configuration tutorial to configure the workspace and be able to build applications.
Cristian is correct, but this may help more:
You should go to this URL: http://localhost:8080/apex/ . You have to know the name of one of the workspaces you created, and a user with Admin or Developer role. These Workspace users can be created in the apex_admin site ( http://localhost:8080/apex/apex_admin/ ), under "Manage Workspaces" / "Manage Developers and Users". Also, Admin users of each Workspace can create new users once you get in.
Related
When I want to create WebCenter Portal Application from JDeveloper 12c, I can't find this option in the gallery, how I usually do this from JDeveloper 11g.
You need to install the WebCenter extension using help->check for updates
(or get it from here - http://www.oracle.com/ocom/groups/public/#otn/documents/webcontent/156082.xml#oracle.asset-publishing-ext )
The Portal Asset Application lets you create the portal assets (page templates, layouts, skins, content presenter templates, etc) that can be deployed to your webcenter portal. Portlet producer similarly let's you create portlet producer applications that can be used in webcenter.
I was trying ot build a web application using Oracle application expressOnce. I logged out from APEX and logged in again leter. I couldn't located my incomplete application. How can I find my application so I can continue work on it?
I have a short question.
After I install Oracle SOA Suite, the managed servers soa_server1 and bam_server1 are created and configured automatically ( the only thing I need is to start them ?), or I need to do this by myself ( create and configure)?
Thank you.
After installing the SOA Suite, you need to create and configure a domain.
You define managed servers that you need in your domain.
11g links:
https://docs.oracle.com/cd/E12839_01/install.1111/e13925/configure.htm#INSOA218
https://udayarocks.wordpress.com/2011/03/29/how-to-create-a-domain-with-soa-managed-server-in-weblogic-server-11g/
(If you used the SOA Quickstart installer for 12c for development purposes, an "integrated domain" might get created automatically when you run some code from within JDeveloper - this integrated domain typically has everything (soa/osb/bam) on a single server and is suitable only for development)
On SQL Server 2008R2, we have a SQL login tagged with the sysadmin server role. Anytime a db is created, this login is automatically added as a user to the db. Is there a switch that will prevent this from happening?
EDIT:
Based on the answer below, I am adding more background info to explain why we want to do this.
When we publish to a new database from a Visual Studio SQL project, the publishing engine wants to add a user to the database. The username already exists as a login to the database (in the sysadmin server role -- and not much we can do about that), so the publish fails as the user gets auto-added by SQL server after the 'create database' statement. I was hoping for a switch that would tell SQL Server to not add the user automatically. So it seems we will have to find another solution on the VS side that tells the publishing engine to ignore the SQL DB user.
Assuming you're talking about the sql-server role, I don't think so. TBH if you're contemplating keeping a sys-admin out of a db, then you've got a different problem than the one you think you have...
I have a resolution to this. Download the latest SSDT package from MS and now there are new options under the Publishing Wizard Advanced... button to exclude the publishing of logins, roles, etc. The SSDT package I downloaded I found here...
https://msdn.microsoft.com/en-US/dn864412
I'm working through this tutorial:
Deploying an ASP.NET Web Application to a Windows Azure Web Site and SQL Database
In the second part "Enable Migrations and create the database" I need to use the NuGet Package Manager console to enter a series of commends:
enable-migrations -ContextTypeName ToDoListApp.Models.ToDoDb
add-migration-initial
update-database
Why do I need to do this explicitly? Shouldn't this be wrapped up in the publish process?
Thanks
Dave
The migrations process is separate from Azure. You can have an MVC 4 project that uses database migrations but the database is not hosted on Azure. The commands you are referencing simply enable the migrations in any MVC 4 project.
I find updating the database dangerous, so I actually prefer it to be separated from the publishing process because this way someone on your team is able to update the logic of the website without pushing updates to the database.