Joel: Deploying several pages of a multilingual application

Question

Hi,
do anybody have experience how to deploy only some pages of an application with their translation files, without be forced to deploy the whole application.
I do know the site to deploy a whole multilingual application:
[http://iadvise.blogspot.com/2006/12/apex-deploy-your-multilingual.html]
What I tried:
- deploy the application from the development system to a different APP_ID on the target system
- copy the concerned pages from the deployed application to the target application
- importing the translated textfile for the concerned pages from the development system to the target system
--> this doesn't work!
Background is, we are several developers on a master application. This master application consists of page bundles. Each page bundle represents a closed function within the master application.
I'm searching for a possibility to deploy a special function (represented by several pages) without to be forced to deploy the whole application everytime.
Thanks for any hint.
Joel, Arie told me you are the real expert of that issue.
Norbert
Edited by: Norbert2 on Jul 15, 2009 11:23 PM

Answer 1

Hello Norbert,
>> Is there a chance to alter the id on one system to make it the same?
The workspace ID is a column in more than one APEX metadata table (and not always under the same name), so externally and manually changing it is not really an option.
>> …what do I have to do with the existing application before I delete the workspace from the target system …
Deleting a workspace with live applications is a bit radical. I understand that the target workspace don’t share the destination workspace ID. Do they share the same name? If not, you can create a new workspace, by importing the original (source) one. It’s possible for more than one workspace to be associated with the same database schema, so all the other applications will share one workspace, and the multi-lingual application will have its own workspace. Of course, this will not work if source and target workspaces share the same name.
In this case, deleting the destination workspace, and creating a new one, by importing the source workspace is an option, although a scary one. First, you should make sure you have viable and working backups on the database level. Only then, you should export all the current applications, and continue with deleting the current workspace, and importing a new one. With the new workspace in place, you can import all the applications back.
You can use the APEXExport.class (Java) utility, which allows you to export all the applications in a specific workspace. You can find it under the ‘utilities’ directory, in the APEX distribution files. Searching this forum will yield several threads on this utility, including a specific blog entry made by Jes (John Scott).
Another option you have is to use Oracle SQL Developer to export all the applications, although similar to the internal APEX export wizard, you’ll have to do this one application at a time.
>> Do I have to translate all again after import the applications to the new generated workspace …
No. As you basically have the same workspace as the original one, you can seed the main language application, and then to upload your original XLIFF, which contains all the translations you made.
Deleting a live workspace and creating a new one can be a tedious task, and very risky one. Don’t look for shortcuts, and make sure you have good backups to fall back on.
Regards,
Arie.
Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.