Exporting .par files from EP6.0 SP2

[Former Member]

Hi

I've tried to export .par files from EP6.0 SP2 via System Manager -> Support -> Portal runtime -> Browse deployment

but i only find master components and i need to export the java iViews that i create.

somebody can help me?

Thanks in advance.

[Former Member · Accepted solution]

Hi,

Create a transport package of the iviews you would like to export via System administration->Transport

Remember to check the "Include all objects on which the exported objects depend" and leave the id blank.

Then the par files will be included in the transport package.

On the target system you go to System administration->Transport->Import and import the created transport package.

[Former Member]

Hi,

I'm going to explain what i am trying to do.

What i want is to export my new iViews from EP and modify it in my develop enviroment (local).

I tried to transport and download it as you say but i only could get .tpl files.

Thanks in advance.

[Former Member]

Hi,

here is a quick and dirty way to this.

Just copy your par file from this directory:

j2ee_<XX>/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/deployment/pcd/

(e.g. via ftp) to a local folder. Remove the .bak from the filename and import the par file in eclipse. This of course works only if the sourcecode is included in the par file.

Kind regards

Francisco

[detlev_beutner]

Hi Julián,

first, some wordings to clarify:

A PAR is a Portal ARchive. It is a zip in a certain format. It contains a portal application.

A portal application consists of components and/or services.

An iView is somehow an "instance" of a component. It is created within the portal. There are no iViews in a PAR (like: "There are no objects in a JAR (but classes).").

So, if that is understood, you will know that all you can modify by your development env is code (and the default properties of component profiles etc, and in theory some more things I don't want to tell for not being too confusing). Code is in JARs. JARs are in PARs.

It is possible also to export PARs into Transport Packages, but this does not fit your aims.

So, if you want to change code in iViews you did write by yourself, use the project you have created for. If you want to change code of iViews written by third party, get the par (and you will have to decompile it probably). To be serious - such things only should be done with really deep knowledge of all the things around.

Just a comparison: You are able as an adult to use a knife to cut bread, and noone will be bemused if you say "Hey, next week I will start to learn juggling!" But if you say "Hey, until now I used knifes only to cut bread and juggling has never been an issue I have been interested in, but next weekend, I will do the sooper-dooper-workshop: 10 hours juggling with 10 sharpened knifes, half of them burning in addtion, in a totally dark room, no phone to call the doctor within the next 500 miles. Yeah, that will be fun!", people will get irritated...

So far my speak for the weekend...

Hope it helps (to keep you from getting hurt seriously)

Detlev

[Former Member]

Hey Guys, any idea how I can package a set of PAR files from my development portal(EP6 SP2) and then import that package into a different portal(EP6 SP2)?

I read about the sapmake_util tool which I can make use of for this purpose. But am not able to locate it on my portal server.

Please provide your inputs.

Thanks

Shakeel

[detlev_beutner]

Hi Shakeel,

see

There the tool, it's location as well as it's purpose is discussed and a link to the central SAP note is given.

Hope it helps

Detlev

[Former Member]

Hi Detlev,

As per the SAP note 696084, pre-requisite for the make utility is EP6 SP3 and SAP Netweaver Developer Studio.

How do I use this tool with EP6 SP2 and Eclipse?

Am looking for something which will help me in transporting a set of PAR files(which have no iViews depending on them) from one portal to another. Both being EP6 SP2 portals.

Thanks for your help.

Shakeel

[detlev_beutner]

Hi Shakeel,

ah, OK, sorry, for EP6 SP2 the tool doesn't exist and I would be sceptical if you could use the one for SP3++. Anyhow, you could try.

Workarounds for SP2 could be:

- you could use the code of the eclipse plugin to write your own batch uploader for a set of PARs; I don't know if the API / way is documented anywhere in detail, even if not, it shouldn't be too hard to find out how it works.

or

- (that's tricky, I hope you like it) create a set of iViews, each using one component of one portal application, create an export package, which includes all dependent objects ("*"), "export" --> all PARs are taken into the export, too --> now delete the iViews --> now you can create an export package on all PARs ))

Hope it helps

Detlev

[Former Member]

Thanks Detlev!

~Shakeel

[Former Member]

Hi Detlev & Shakeel,

Just to confirm, this "Make Utility" is the recommended way to package PAR files for deployement in EP6 on NW04? Would it not have been easier to allow administrators to package the PAR files into a Transport Package and then follow the standard transport procedures (export/import)?

Detlev I like your workaround above (adding the iviews with dependencies and then removing the iViews just leaving the PARS) but that seems strange, why can we just browse the PCD where the PARS are kept and add them to our transport packages.

My main reason for asking is that I want to follow a multi-package Structure (Navigation) / Content (Pages & iViews) / Application (PARS) approach to transports, as recommended by SAP in their Transport Stategy guide. In an attempt to prevent unexpected suprises during transports!

Thanks for your help.

Simon

[detlev_beutner]

Hi Simon,

> this "Make Utility" is the recommended way

> to package PAR files for deployement in EP6 on NW04?

No, that cannot be said generally. The info Azriel gave in the referred thread is not SAP-official. The official strategy is described in here:

http://help.sap.com/saphelp_nw04/helpdata/en/d6/772240da03e569e10000000a155106/frameset.htm

So this is a bit "it depends".

> I like your workaround above

Yes, it's a bit "outflanking SAP"

> seems strange, why can we just browse the PCD

> where the PARS are kept

> and add them to our transport packages.

Good question, ask SAP I think the idea behind this is that EPAs are primarily <i>content</i>. PARs are somewhat the slaves behind the roles/worksets/pages/iViews. The EPA transport mechanism is reserved for the "valueable" content, and if the slaves are needed, they are allowed to accompany. But not alone...

I also woule like it more to have the flexibility at hand just to add the PARs to a transport package directly.

Hope it helps

Detlev