Skip Headers
Oracle® Database 2 Day + Application Express Developer's Guide
Release 4.0

Part Number E15516-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF · Mobipocket

5 About Deploying Your Application

This section describes basic information about deploying your Oracle Application Express application. It also shows you how to create end users and to determine the URL of your application.

Topics:

Overview of Deploying Your Application

After building your application in your development environment, you need deploy it so that end users can begin using it. Deploying involves the following steps:

  1. Collect your supporting object definitions (CREATE object statements, sample data, images, files, and so on). Review the Database Object Dependencies report to determine which supporting objects to move. See "Viewing Dashboards and Reports" in Oracle Application Express Application Builder User's Guide.

  2. Define your supporting objects. This includes the object definitions you collected in the previous step and other supporting objects, such as messages and prerequisites.

  3. Export the application with its supporting objects.

  4. Import and install the exported files.

Using Oracle Application Express greatly simplifies the deployment process. It enables you to migrate the application definition, associated files, and all supporting objects in just a few steps.

See also:

"Deploying an Application" in Oracle Application Express Application Builder User's Guide.

Creating End Users

After moving your application to a production environment, you must now create user accounts within Oracle Application Express for all your end users.

To create end user accounts:

  1. Navigate to the Workspace home page.

  2. Click Administration.

  3. Click Manage Users and Groups.

  4. Click the Create User button.

    The Create User page appears.

    Description of deploy_cr_enduser.gif follows
    Description of the illustration deploy_cr_enduser.gif

  5. Under User Identification, enter:

    1. Username - Enter the username used to log in to the system. Restrictions include:

      • Maximum length of 100 characters

      • No spaces

      • Only these special characters are permitted: ampersand (@) and period (.)

    2. Email Address - Enter the valid email address for this user.

    3. First Name - Enter the first or given name to further identify the user (optional).

    4. Last Name - Enter the last or family name to further identify the user (optional).

    5. Description - Enter comments about this user (optional).

  6. Under Account Privileges:

    1. Default Schemas - Specify the default schema used for data browsing, application creation, and SQL script execution.

      When using workspaces that have more than one schema available, this schema is the default. This setting does not control security, only the user's preference.

    2. Accessible Schemas (null for all) - Leave this blank to enable the end user to access all applications in the workspace, or enter a colon-delimited list of schemas for which this user has permissions when using the SQL Workshop.

    3. User is a workspace administrator - Specify if this user should have workspace administrator privileges.

      Administrators are given access to all components. Additionally, they can manage user accounts, groups, and development services. Components may not be available if they are switched off by Instance Administrators.

    4. User is a developer - Specify if this user should have developer privileges.

      Developers must have access to either Application Builder, SQL Workshop, or both. Components may not be available if they are switched off by Instance Administrators.

    5. Application Builder Access - Determines whether a developer has access to the Application Builder.

    6. SQL Workshop Access - Determines whether a developer has access to the SQL Workshop.

    7. Team Development Access - Determines whether a developer has access to the Team Development.

    8. Set Account Availability - Select Locked to prevent the account from being used. Select Unlocked to allow the account to be used.

  7. Under Password:

    • Password - Enter a case sensitive password.

    • Confirm Password - Enter the password again.

    • Require Change of Password On First Use - Select No to allow the user to use the same password until it expires. Select Yes to require the user to change the password immediately when logging in the first time.

  8. Under User Groups, optionally select a user group.

  9. Click Create User or Create and Create Another.

See also:

"Managing Application Express Users" in Oracle Application Express Administration Guide

About Publishing the Application URL

After deploying your application, you must now publish its URL so end users know how to access it.

To determine the URL:

  1. Log in to Oracle Application Express on the production environment.

  2. Select the application.

  3. On the Application home page, position the mouse over the Run Application icon.

  4. Note the URL that displays in the status bar at the bottom of the page.

For example:

http://apex.oracle.com/pls/apex/f?p=11563:1:3397731373043366363

Where:

To run this example application, you would go to this URL:

http://apex.oracle.com/pls/apex/f?p=11563:1

See also:

"Deploying an Application" in Oracle Application Express Application Builder User's Guide