Skip to Content
author's profile photo
Former Member

Exporting .par files from EP6.0 SP2

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.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    author's profile photo
    Former Member
    Posted on Feb 04, 2005 at 12:43 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Feb 04, 2005 at 02:04 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded

    • 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