Skip to Content
author's profile photo Former Member
Former Member

Portal trasnport strategy question

Hello,

We have below configuration in our development portal environment.

Role1

|_____Iview1

|_____Iview2

|_____Iview3

|_____Folder1

_______|_____iview4

_______|_____NewIview5

_______|_____NewIview6

In above configuration we have created two new iviews (in bold) above:

NewIview5

NewIview6

Now we need to migrate these two new iviews to production system.

Now the approach in my mind is :

1. Create a .epa transport package and add NewIview5, NewIview6 in this package and then import it in production.

But I think the iview to folder role mapping of NewIview5->Folder1->Role1 and NewIview6->Folder1->Role1 will be lost in production.

2. Second approach which I am thinking upon is... to create a .epa transport package and add full Role1 in it, and include all dependent objects as well. But here I feel that I will have to unnecessarily migrate other objects i.e. Iview1,Iview2, Iview3, Iview4.

Please comment on the best approach.

Thanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2010 at 10:56 AM

    Saurab,

    Probably you could go with the second approach. What if in the future the rest of your iviews are also wanted? Would you be transporting them again ?

    Regards,

    Sandeep Tudumu

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Maheshchandra VVNS

      Yeah !

      I will go for approach 1 infact.

      Role to iview mapping could be done easily in production as I only have 2 iviews.

      Nyways thanks a lot for your inputs. It really helped me in reaching to a conclusion.

      Mahesh, just in case if you would like to share that method as well, I would really appreciate and keep it in mind for future references.

      Thanks.

  • Posted on Oct 13, 2010 at 10:43 AM

    saurabh,

    if the iviews are related to reports, systems etc they require additional property changes in production. so then first approach seems good. less work.if you have more number of iviews and mapping will be little complex for checking with all iviews in production then second approach seems good, total role change at a time.either way doesn't makes the system more burden. this is the approach what i feel/do

    regards

    Mahesh

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.