This Space has blogs on various topics in the field of SAP. These blogs point out solutions to various technical and functional issues that consultants face during implementation or support of SAP Projects. Readers/followers are welcome to contribute to this space by emailing your content at bohra.mohammadi@gmail.com. You will be rewarded according to the topic/number of words/complexity of the topic/issue which are you addressing in your blog.
Showing posts with label worksets. Show all posts
Showing posts with label worksets. Show all posts
Sunday, August 14
How to make WDJ Component available on SAP EP
You need to create Iview to hold the web dynpro java component in SAP Enterprise portal. The iview can be assigned to a role. Generally an iview is assigned to a workset first and then that workset is assigned to a role. Many users c belong to that role. All the users belonging to that role will be able to see the web dynpro component present in the iview.
Iview has a parameter called entry point. The value of this parameter should be set to "Yes". By doing this we make sure that the Web dynpro component appear in the top level navigation area of the sap enterprise portal.
To create Iview, workset and role and other PCD objects like pages etc you need to have administrator role in the sap ep. So if you login using the super administrator role, go to content admin tab of sap ep then go to portal content. In portal content, you can create a folder which is a PCD object. In that folder, you can create roles, worksets etc.
Before you start learning and developing portal objects and customizing sap ep for your client, it is important to learn what are roles,pages, iviews, worksets etc...
Labels:
component,
learn sap ep online,
pages,
web dynpro java,
worksets
Saturday, July 2
Delegated Administration
The process of "distributing" the administrative content and tasks in the portal to one or more administrators or group administrators is delegating administration. As opposed to the non-delegated portal environment this capability allows you to confining of each administrator or group of administrator, data, the tools, and tasks that is restricted to a specific user or group—, that can expose each administrator to all other administration tools, connected systems,and company data, without restriction.
Delegated administration allows you to do the following:
organizing of the administration framework totally according to your business scenario.
controlling the distribution of portal-related administrative tasks,hence reduces the total cost of ownership (TCO) significantly which is a key function for the "global portal" scenario.
managing large scale portal implementations.
SAP Enterprise Portal offers delegated administration that is fully customisable with user permissions, at these levels:
work sets and Portal roles , and the services (tools) provided by them.
Portal objects like content of the Portal Catalog
Features
1. Administrative Tasks delegation:
All administrative tools available in the portal are in effect iViews, that are integrated subsequently for task-oriented worksets. These worksets are assigned to a predefined sub-administration role in an off-the-shelf installation of SAP Enterprise Portal.
The worksets and pre-configured administration roles serve the purposes of:
Delivering the portal administration like modular building blocks, and hence providing the flexibility of addressing variations in administrative tasks that are performed by one administrator or a group of them.
Providing an example that resembles how one should structure the delegation of administration tasks.
Since the standard SAP role concept is followed by the the pre-configured administration roles you can easily adapt the pre-configured task delegation according to your own admininistration roles or vice versa to suit your environment.
2. Delegating Administration on the Portal Catalog
SAP Enterprise Portal allows the assigning of delegated administration at the level of the Portal Catalog.
The Portal Catalog may include the following objects:
System Landscape objects
Content Objects (iViews, pages, layouts, roles, worksets, packages)
Unification presentation components
KM Objects (resource, taxonomy)
The Portal Catalog does the organization of portal objects, that include the content objects, in a hierarchy. You can set permissions to a node, like a folder containing a group of iViews, or for one object. When objects are below a given node Permissions are inherited to the child . Permissions are editing and reading capabilities of the objects.
You assign permission to folders and objects per role, or user or user group; and hence define who is responsible for customization of object and who is able to just see the objects. After the initial deployment process, the first task of the super administrator is being assignment of default initial content given in the portal, to the which have been defined in the system.
Related Posts:
Page Builder
Knowledge Management
More on Administration:
Super Administration
User Administration
Content Administration
System Administration
Delegated administration allows you to do the following:
organizing of the administration framework totally according to your business scenario.
controlling the distribution of portal-related administrative tasks,hence reduces the total cost of ownership (TCO) significantly which is a key function for the "global portal" scenario.
managing large scale portal implementations.
SAP Enterprise Portal offers delegated administration that is fully customisable with user permissions, at these levels:
work sets and Portal roles , and the services (tools) provided by them.
Portal objects like content of the Portal Catalog
Features
1. Administrative Tasks delegation:
All administrative tools available in the portal are in effect iViews, that are integrated subsequently for task-oriented worksets. These worksets are assigned to a predefined sub-administration role in an off-the-shelf installation of SAP Enterprise Portal.
The worksets and pre-configured administration roles serve the purposes of:
Delivering the portal administration like modular building blocks, and hence providing the flexibility of addressing variations in administrative tasks that are performed by one administrator or a group of them.
Providing an example that resembles how one should structure the delegation of administration tasks.
Since the standard SAP role concept is followed by the the pre-configured administration roles you can easily adapt the pre-configured task delegation according to your own admininistration roles or vice versa to suit your environment.
2. Delegating Administration on the Portal Catalog
SAP Enterprise Portal allows the assigning of delegated administration at the level of the Portal Catalog.
The Portal Catalog may include the following objects:
System Landscape objects
Content Objects (iViews, pages, layouts, roles, worksets, packages)
Unification presentation components
KM Objects (resource, taxonomy)
The Portal Catalog does the organization of portal objects, that include the content objects, in a hierarchy. You can set permissions to a node, like a folder containing a group of iViews, or for one object. When objects are below a given node Permissions are inherited to the child . Permissions are editing and reading capabilities of the objects.
You assign permission to folders and objects per role, or user or user group; and hence define who is responsible for customization of object and who is able to just see the objects. After the initial deployment process, the first task of the super administrator is being assignment of default initial content given in the portal, to the which have been defined in the system.
Related Posts:
Page Builder
Knowledge Management
More on Administration:
Super Administration
User Administration
Content Administration
System Administration
Sunday, June 26
Instant start to Netweaver portal administration
This post will provide you a basic and instant start to Netweaver portal administration. Definitions of the most important things that you much know for portal administration are covered in this post.
Usage Types
Before I tell you what are usage types, I must tell you that usage types made a SAP Portal administrator's life easy. Usage types were introduced when SAP Came up with SAP Netweaver Portal 7.0.
Usage types of SAP NetWeaver are software units to be installed. The usage types Application Server ABAP and Application Server Java are used as a foundation for other units. You can select one or more usage types during NetWeaver installation.
SLD
If you are a portal administrator you must know how to configure SLD. This can be done manually also and there is an automated way of doing this. You can chose one depending on your situation and requirements.
The SLD configuration is included in the AS Java installation. In some cases, the SLD configuration has to be changed. Below are main steps to be followed while changing the SLD Configuration.
- Specify the Groups and Users That Can Operate in the SLD
- Specify Where to Persist the SLD Information and Who Can Alter It
- Fine Tuning the SLD Server
- Initial Import of the SAP CIM model or the CR Content
- Configuring the Channel for Receiving SLD Reports
JCO
JCO or the Java Connectors connect SAP EP applications to SAP R/3 systems. So basically they fetch data and functionality from the SAP systems to be used and displayed in SAP EP or in applications which are used by SAP EP. For example, SAP Web Dynpro Java applications can talk with the SAP systems using JCO. As a portal administrator, you must know how to created, edit, check and activate a JCO. How to delete a JCO, how to troubleshoot a JCO in case of errors in connection.
Properties of Iview, workset and roles
Various properties of Iviews, worksets, roles are a must to know. This is important when administrator is asked to create/modify these PCD objects. Based on various business requirements, portal administrator may have to change the properties at runtime or design time and achieve what is needed.
Admin Tools
Various tools like Visual admin, Config tool and offline config editor are must.
SSO and System Configurations
Single Sign On means that portal user will have to punch in his/her username and passord only once and after that he/she will not be asked for login credentials no matter which system he/she tries to access through portal. This feature of SAP Netweaver portal helps you a lot by providing you the freedom to forget passwords. SAP EP connects to various backend SAP systems on your behalf. It is very important topic to be known by a portal administrator. Frequently asked in interview questions. How to create a SSO. How to change SSO settings etc etc...
Labels:
admin tools,
default sap roles,
iviews,
Jco,
portal administrator,
portal solutions,
sap enterprise portal tutorial,
sap enterptise portal,
single sign on,
SLD,
Usage Types,
worksets
Subscribe to:
Posts (Atom)