Application Deployment in Oracle APEX with Data - Part 40
Summary
TLDRThis Tech mining video tutorial guides viewers through the process of migrating applications and data across Oracle Apex instances using the Data Packager utility. It covers handling unsupported blob data types, creating scripts for database objects, and managing user roles and authorizations post-migration. The video ensures a smooth transition, from exporting applications and data to importing and setting up a new workspace, ultimately allowing users to access their newly deployed application with the complete data intact.
Takeaways
- 🔄 Easily migrate applications between instances with Oracle Apex's Data Packager utility.
- 🚫 Blob data type is not supported for export, requiring removal or modification of blob columns like the product image in the demo products table.
- 📝 Follow a specific sequence when creating scripts: first sequences, then tables, and finally triggers.
- 🔄 Use the Data Packager feature to export application data along with the database objects.
- 🔄 Ensure the 'demo product info' table is placed after the 'demo customers' table to prevent foreign key violations.
- 🔄 The 'product info' table should precede the 'order items' table as it is the master table.
- 📁 Export the application with both the application and underlying data packaged.
- 🔄 Test the import process in a new workspace on the Oracle Apex site.
- 👤 User roles and authorizations are not exported with the application; they must be manually managed post-deployment.
- 👥 Create and assign different roles to users for access to the newly imported application.
- 🏢 Set the application authorization scheme to 'No Application Authorization Required' to access the application.
Q & A
What is the primary purpose of the data packager utility in Oracle Apex?
-The data packager utility in Oracle Apex is used to specify a table or a list of tables for which the data gets exported with an application, allowing for easy migration of applications and their data from one instance to another.
Why can't the demo products table be used directly for the sales web application deployment?
-The demo products table cannot be used directly because it contains a BLOB column, and BLOB data types are not supported for export using the data packager utility.
What steps must be taken before deploying the sales web application?
-Before deploying the sales web application, the product image column must be dropped from the demo products table.
In what order should database objects be created in Oracle Apex?
-In Oracle Apex, database objects should generally be created in the following order: first create a sequence, then a table, and finally a trigger.
Why is it important to move the demo product info table just after the demo customers table?
-Moving the demo product info table just after the demo customers table is important to prevent foreign key violations during the data import process.
What is the relationship between the product info table and the order items table?
-The product info table is the master table to the order items table, so it must be placed before the order items table to avoid constraint violation messages during the import process.
What should be done after exporting the application and data from Oracle Apex?
-After exporting the application and data, a new workspace should be created on the Oracle Apex site to test the import process. The exported application file should then be imported into this new workspace.
What needs to be manually managed after importing the application into a new workspace?
-After importing the application, user to role assignments need to be manually managed, as application users are not exported as part of the application.
What roles should be assigned to the three users created in the new workspace?
-The first user should be assigned the administrator role using the new workspace email ID. The remaining two users can be assigned any name and given the contributor and reader roles.
What setting must be adjusted to access the newly imported application without authorization errors?
-The application scheme should be set to 'no application authorization required' to avoid authorization errors and ensure access to the newly imported application.
Outlines
🔧 Migrating Applications with Oracle Apex Data Packager
This paragraph introduces the process of migrating applications in Oracle Apex, focusing on the use of the Data Packager utility. It explains the limitation of the blob data type and the necessity to handle it by either dropping the product image column or proceeding without exporting it. The speaker outlines the steps for creating scripts for supporting objects and emphasizes the order of creating sequences, tables, and triggers. Additionally, the paragraph covers the importance of arranging database objects correctly to avoid foreign key violations during the import process and concludes with exporting the application for deployment in another environment.
🛠️ Importing and Managing Oracle Apex Applications
The second paragraph delves into the post-export steps of importing an Oracle Apex application into a new workspace. It highlights the need to review the installed application tables, sequences, and triggers through the object browser. The speaker then addresses potential authorization errors that may arise and provides a solution by manually managing user roles and assignments. The process includes creating users with specific roles such as administrator, contributor, and reader, and setting the application authorization scheme. The paragraph concludes with the successful access and review of the newly imported application, ensuring that all pages and data are displayed correctly.
Mindmap
Keywords
💡Tech mining
💡Migrate
💡Data Packager
💡Blob Data Type
💡Sales Web Application
💡Foreign Key
💡Oracle Apex
💡Sequence Script
💡Trigger
💡Workspace
💡Application Users
💡Role Assignments
💡Authorization
Highlights
Migrating applications between instances and including data in tables using Data Packager in Oracle Apex.
Blob data type is not supported for export, requiring removal of the product image column for the demo products table.
Steps to use the Data Packager utility for exporting applications with data.
Creating scripts for supporting objects to package the application for installation in another environment.
Sequence creation is the first step in Oracle Apex, followed by tables and triggers.
Using the Data Packager feature to move data along with the application.
Importance of the order of database object scripts to prevent foreign key violations.
Placing the product info table before the order items table to avoid constraint violation during import.
Exporting the packaged application from the current workspace.
Creating a new workspace on Oracle Apex for testing the import process.
Importing the application file into the new workspace.
Reviewing application tables, sequences, and triggers installed with the application.
Running the newly imported application and potential authorization errors.
Manually managing user role assignments after deploying the application.
Adding users and assigning different roles such as administrator, contributor, and reader.
Setting the scheme to 'No Application Authorization Required' to access the imported application.
Accessing and verifying the newly imported application with complete data and pages.
The video aims to be helpful for understanding the process of migrating and deploying applications in Oracle Apex.
Transcripts
a very warm welcome to Tech mining
you can also easily migrate your
applications from one instance to
another and include data in tables using
data packager in which you specify a
table or a list of tables for which the
data gets exported with an application
here are the steps to use this utility
first because of blob data type is not
supported for export since we have a
blob column in the demo products table
we cannot use this procedure to deploy
sales web application unless we drop
product image column
foreign
product image column from the database
now we can proceed further
in this steps we are creating scripts
for supporting objects to package the
application for installation in other
environment
[Music]
first create sequence script because
generally in Oracle Apex first we create
sequence then table and then trigger
[Music]
thank you
[Music]
foreign
[Music]
button on the right side of the page
move up the demo product info table just
after the demo customers table to
prevent foreign key violation
[Music]
foreign
[Music]
database object scripts in order to move
data as well with the application we use
the data packager feature of Oracle Apex
thank you
foreign
button move the demo product info table
just after the demo customers table
you have to place product info table
before the order items table because the
product table is the master table to the
order items table
if you don't do this you will get
constraint violation message during the
import process
[Music]
foreign
foreign
[Music]
table must be placed before the order
items table now that we have the
application as well as the underlying
data packaged we can export this
application
[Music]
foreign
[Music]
you need a new workspace on Oracle Apex
site to test the import process click
the info icon provided at the top to
learn how to create a new workspace in
Oracle Apex after creating the workspace
log into it
now import the application file that you
just exported
[Music]
foreign
[Music]
after this success Now navigate to
object browser
and review the application tables that
are installed along with the underlying
data
foreign
[Music]
sequences and triggers as well
[Music]
now run the new application you've just
imported
[Music]
you will encounter an error saying you
are not authorized to view this
application
when you deploy your application you
will need to manually manage your user
to roll assignments
application users are not exported as
part of your application
in this step we have to add three users
and assign them different roles
[Music]
create the first user with your new
Workspace Email ID and assign it
administrator role
[Music]
for remaining two users you can use any
name you like
then assign them contributor and reader
role
[Music]
foreign
[Music]
set scheme to no application
authorization required
now you will be able to access your
newly imported application
[Music]
foreign
[Music]
as you can see all the pages are
displaying along with the complete data
same as in previous workspace
that's it for now
hope this video was helpful to you
thanks for watching
[Music]
Посмотреть больше похожих видео
How to Upload PDF, Audio, Video, and other Documents in Oracle APEX - Part 9
Manage Customers Profile using Interactive Grid and Input Form - Part 5
Create Advance PDF Reports in Oracle APEX Comprising Grouping | Chart | Pivot Table - Part 33
Entity Framework Setup - GRAPHQL API IN .NET w/ HOT CHOCOLATE #5.1
Deploying Application in Oracle APEX - Part 39
Create Setup to Display Records In an Order Calendar - Part 28
5.0 / 5 (0 votes)