July 18, 2011 Leave a comment
by Andrew Archibald
My name is Andrew Archibald, one of the Oracle consultants at Rocela and I thought it’d be interesting to take this opportunity to write about something a bit different for our blog today. For my first article, I’ll be looking at ApEx and its integration with Oracle E-Business Suite.
Start as you mean to go on
Before starting any development on an ApEx application using Oracle E-Business data, the setup of the ApEx development and production environment must be considered.
There is no right or wrong way of deploying ApEx but in general, the preferred structure is to install ApEx within the Oracle E-Business database. This is because it allows you to leverage the Oracle E-Business objects with little effort and share the benefit of functionality such as security.
As part of the ApEx install, 2 schema will be created: APEX_XXXXXX schema and FLOWS. Once that’s complete, you’re left to your own devices.
Although ApEx needs a web server for deployment, if the client has Discoverer Plus installed then the Discoverer web server would suffice. Otherwise, using the Oracle E-Business Apache server provides another workable alternative. The other consideration to bear in mind is the number of users to be using ApEx and whether these web servers will be able to handle the load.
So we have our ApEx environment and the DBAs have presented us with the internal workspace password (if you are allowed to be let loose!). The next step is to activate the create workspace wizard, upon which you’ll be confronted with the question of whether to reuse an existing schema or create a new one.
And here comes the big question – should you use the APPS schema, try another Oracle E-Business Schema or create a new one purely for our applications?
My advice? Always choose the last option and create a new schema for your ApEx application. Why? Well for a start, it makes migrating from one environment to another much easier – if you’re using SQL Developer then you can simply use the database unload functionality to export all objects.
There’s also a risk that you might end up overwriting an Oracle E-Business object if you use the APPS schema – another good incentive to create all your objects in a separate schema.
I have heard of developers using the APPS schema, and I can see the time advantages in granting access to underlying objects but again there would be a risk of naming an object the same or deleting an object. With ApEx 4.0 and the new websheets I would also be concerned about tablespace usage and so having ApEx applications use there own schema with there own tablespace would make this easier to manage.
Coming soon, my next blog posting will build upon this discussion and take a closer look at Authenticating ApEx using Oracle E-Business credentials. If you have any feedback or questions in the meantime, let me know in the comments below.