cancel
Showing results for 
Search instead for 
Did you mean: 

New PAR file not appearing in the Portal Archive Selection list

Former Member
0 Kudos

Hello Knowledgeable Portal Ones,

I am on EP6.0 SP13.

A developer on the team created a new PAR. It was uploaded, and it is now showing in my portalapps directory. A super-admin for the portal can successfully create an iView using it (New from PAR), but developers (who have lesser security access) can not. When developers attempt to do so, no portal archives appear in the portal archive selection list. In fact, developers would not be able to create a new iView from any PAR.

I see that the portalapp.xml has placed the PAR in "high-safety". I suppose this may be causing the problem.

How do I address this problem?

Thank you for your feedback.

Kevin

Accepted Solutions (1)

Accepted Solutions (1)

pravesh_verma
Active Contributor
0 Kudos

Hi Kelvin,

Thats true that a devloper cannot create an iView using the PAR. The only reason for this is the devloper may not have the <b>Content Administration</b> role with him/her. Please ask the portal administrator to assign the Content administrator role to the user.

<b>Role ID:</b> content_admin_role

<b>Role Name:</b> pcd:portal_content/administrator/content_admin

Then definately the user can create the iView from par.

<b>>>I see that the portalapp.xml has placed the PAR in "high-safety". I suppose this may be causing the problem.</b>

Ans: No, this property is nothing to do with the creation of iView. So no need to worry for this. This will not create any problem.

Hope this solves your Problem!!

Regards

Pravesh

PS: Please do reward points for helpful Answer.

Former Member
0 Kudos

The developers already do have the content_admin role assigned to their userids. However, they still cannot create an iView from a PAR ("New from PAR").

I always reward points on replies. However, for some reason the radio buttons are not showing up on your first reply. Do you know why that is?

Thanks,

Kevin

pravesh_verma
Active Contributor
0 Kudos

Hi Kelvin,

If the content_admin role is assigned to the user then he can create the iView. Please try and give the <b>Content manager</b> role also to him. But I dont know whether this could make any difference becuase you just need to have the content admin role to create the iView.

Also Log off and then re-logon to the portal with the userid who has been assigned the role of content admin.

I hope this helps you!! Its good that you reward points. No problem if you cannot see the radio buttons for assigning points. Sometimes this also happen with me. You can always come back to the same post at any time and then assign the points, and close the thread. Hope you do it

Regards

Pravesh

Former Member
0 Kudos

Yes, the content_admin role is assigned to the user as well. And the users have logged off/on and that didn't change things.

Thanks for the thoughts, however.

Kevin

detlev_beutner
Active Contributor
0 Kudos

Hi Kevin,

there are two known possibilities for this behaviour:

1.) Within the portalapp.xml, the property com.sap.portal.pcm.Category has been set to "platform". This should only occur if someone imported an existing PAR to modify it. Also see

2.) Someone has changed the permissions for application access (under System Administration - Permissions - Portal Permissions - Applications - <YourApplication> --- There the one who should create an iView from a component must have Read permission for the corresponding application, also see http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604e505fd11d7b84200047582c9f7/frameset.htm - Administrator Permissions - For portal components

Hope it helps

Detlev

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Kevin

I'm facing the same issue. We uploaded some PAR files to the PCD but cannot see them under Portal Archive Selection list when creating a new iview from PAR. We are on EP6 SP14.

Any pointers will be highly appreciated.

Thanks in advance

Premal

Former Member
0 Kudos

Hi Permal,

One things that helped me was to turn off security zones in my development environment. By default, it was turned on. As a result, this "high" PAR file could only be seen by Super Admins. In the development environment, turn off the security zones, this will resolve the security problems in development.

Turning off security zones in testing and production is not always a good idea, however.

Kevin