What will be exported via OAP file?

I am having environment A and B. I have application with 50 outsystems entities in environment A. These entities having the data that are transacted over the year.


If I export the application (.oap) file from environment A and import it in environment B, what are all the things will get installed?

Specifically I am looking on what will happen to the 1+ year data? I guess only the definition of entities will get installed in environment B (with empty data), I will have to handle the data transfer separately.

Am I correct? Please shed some light on this. Thanks

Hi Arunkumar,

The AOP contains the modules of your application, so you are right, no data will be transfered. You can also check it yourself. The AOP-file is basically a ZIP-file, so you can open it and look inside. You will find a Manifest xml-file and a subdirectory containing your modules (OML's and XIF's).

Regards,
Lennart

Please, look to this information:

1. OutSystems application package (.oap, oap) 
 - Maps directly to an application in the OutSystems platform.
 - Allows automatic application installation with dependency management.
 - Ensures that packages that are installed have no impact in your environment.
 - Ideal for ready-to-run content like applications and components.
 - Is available only from Platform 9 and up.

2. OutSystems module (.oml, .xif)
 - Maps directly to a module in the OutSystems platform.
 - Allows fast module access for code inspection and reuse.
 - Is ideal for code samples and snippets.

3. OutSystems solution package (.osp)
 - Allows multiple modules to be packaged into a single file.
 - Is installed via the environment management console.


Cheers

Lennart Kraak wrote:

Hi Arunkumar,

The AOP contains the modules of your application, so you are right, no data will be transfered. You can also check it yourself. The AOP-file is basically a ZIP-file, so you can open it and look inside. You will find a Manifest xml-file and a subdirectory containing your modules (OML's and XIF's).

Regards,
Lennart

Thanks Lennart for conforming.

So the steps I need to do for migrating the application from A to B is,

  1. Export the application from A
  2. Setup extensions & dependencies correctly in B
  3. Import the solution package in B
  4. Migrate the data between A to B (Entity to Entity Data copy) 

Anything I am missing?


Nuno Miguel Verdasca wrote:

Please, look to this information:

1. OutSystems application package (.oap, oap) 
 - Maps directly to an application in the OutSystems platform.
 - Allows automatic application installation with dependency management.
 - Ensures that packages that are installed have no impact in your environment.
 - Ideal for ready-to-run content like applications and components.
 - Is available only from Platform 9 and up.

2. OutSystems module (.oml, .xif)
 - Maps directly to a module in the OutSystems platform.
 - Allows fast module access for code inspection and reuse.
 - Is ideal for code samples and snippets.

3. OutSystems solution package (.osp)
 - Allows multiple modules to be packaged into a single file.
 - Is installed via the environment management console.


Cheers

Thanks this helps!


Solution

If you want migrate the Data too, you can use this forge component.

Solution

Arunkumar Balu wrote:

So the steps I need to do for migrating the application from A to B is,

  1. Export the application from A
  2. Setup extensions & dependencies correctly in B
  3. Import the solution package in B
  4. Migrate the data between A to B (Entity to Entity Data copy) 

Anything I am missing?

Hi Arunkumar,

Basically that. You can double click on the downloaded OAP-file. This will open Service Studio and you'll be asked if you want to publish the application to your environment. Please note that this only works for enviroments with the same license, otherwise you'll get IPP problems. 

Migrating the data can be tricky. For example for autonumber primary keys you cannot simply copy the original value. As Nuno said, there are some tools available to do this.

Regards,
Lennart