PI server to be used by TWO teams without intervening each others objects

[former_member188019]

We have one PI dev server, and two integration projects (Project A and Project B) are going on.

Project A's team members, developers are different from those of Project B.

We want to allow both teams to work on the same PI server i.e in same ESR and ID, but Project A's team members should not be able to edit Project B's objects and vice-versa.

for e.g. In ESR,

Software Component versions SWCV_A_one, SWCV_A_two belong to Team A

Software Component versions SWCV_B_alpha, SWCV_B_gamma belong to Team B

can we restrict such that B's Team members should not be able to add/edit/reuse objects in SWCV_A_one, SWCV_A_two

In ID, is there anyway to have a set of objects to be edited by only a select set of users.

thanks,

Madhu_1980

[former_member200962 · Accepted solution]

Did you check this: /people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects

In SAP PI 7.1 there is an option Edit Authorizations....check if that helps.

Regards,

Abhishek.

[Former Member]

but then you could end up with lots of duplicate SWCV....

in projects i have worked on, we try and include details of the scenario in the namespace within the SWCV.

then everyone can work within the same SWCV, but have different namespaces for each scenario.

for example..

com.sap.ecc.fi.bankstatementin

com.sap.ecc.fi.invoicesout

com.sap.ecc.sd.salesordersin

then you can have and share common objects too....

as let's face it, the SWCV means very little and will hardly ever be changed...

i think you should use the same authorisation object mentioned above and restrict by namespace. but either way it will prove to have an administration overhead.

[former_member188019]

>Barry Neaves wrote:

>>but either way it will prove to have an administration overhead.

yes i agree, it will lead to adminstration overhead, but they are doing the project for two different customers, and in the future they would like to have two different servers.

>Gabriel Sagaya ... wrote:

>>This feature will be available in PI 7.3. (You can restrict whole SWCV to team B)

>>Since you are in PI 7.1 EHP1, You can use Edit Authorization for each individual objects as an Administratior role.

may be its better handled in 7.3 version then, Having this mechanism in 7.1 will have to do a lot of work in setting up authorizations for each object.

is there any doc that confirms that authorations present at SWCV level in 7.3.

[samiullah_qureshi]

Check the follwoing presenation:-

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a005629b-c063-2910-0fb8-f57dc68a...

Check the section

Limit Authorizations on PI Content Objects

Edited by: Samiullah Qureshi on Jun 7, 2010 5:09 PM

[GabrielSagaya]

This feature will be available in PI 7.3. (You can restrict whole SWCV to team B)

Since you are in PI 7.1 EHP1, You can use Edit Authorization for each individual objects as an Administratior role.

Also you can create Usage Profile to have list of objects to be visible for the user.