Sunday, July 31
Slut Walk - Besharmi Morcha
Delhi is the right place to start such a walk. Delhi has become the most dangerous place for women. Taunting, Molestation, rape and sexual harrasment in schools, colleges and offices and public transport places has become very frequent in Delhi and Gurgaon.
Slut walk is a answer to all those who feel that Women can be treated in any way they want. Slut walk started in Canada in Toronto on the 3rd april 2011. It reached India in Delhi today. Indian as well foriegn women are joining the walk. This walk is indication to men that they should change their attitude towards women and should not pass cheap comments on them. This is a unique way of showing the protest by women but this is very correct. The society is moving in such a direction that if the direction is not changed, the society will become uncivilized.
Thursday, July 28
Rains in Mumbai
It is raining heavily in Mumbai. When it rains in Mumbai, things become irritating sometimes. Though I like rains and the rainy season but when it comes to commute during rains, I am out. I really hate to board a bus of a train or a rick during rainy seasons. they stop at random places bacause of the traffic and the windows rinse with water like anything. When the water rinses to pyjamas and shirts, it gives a very irritating feeling.
Things that we use to save ourselves from rain like umbrellas and raincoats and wind protectors etc are useless in mumbai rains because mumbai rains and massive and continuous. Also they start suddenly, no indication like cloud acculating for few minutes or so and cool winds blowing before the rains etc.
I travel by bus mostly to reach my office. Generally it takes one hour to reach office given that there is no traffic. But during rainy seasons, the commute time increases by 100% and sometimes more than that. My office is located in Navi Mumbai and my home in Kalyan(W). The bus does well till kalyan bypass. But after that the problem begins due to trucks and busses trying to occupy a single lane. The busses and trucks coming and those going take the same lane. The Municipal corporation should look into this matter seriously. The road from Kalyan Bypass to Mahape Circle is full of pits and rainwater accumulate in the pits and it becomes near to impossible to commute on such a road.
So the bus stops and moves like a bullock cart between kalyan bypass and mahape circle. It is really frustrating sometimes especially when it is extremely necessary to reach office on time for a meeting or training etc.
I just step out of the bus and walk towards my office. So on an average I walk 2 kilometres daily in rainy season and that also under heavy rains. I wish I could work from home during rainy seasons. Also this is a loss for the company I work for. I am not able to give my 100% as I am already tired commuting. Same is the case when I have to travel back to home. It is very necessary for me to leave early from the office during rainy season to avoid the rush hours of the bus.
So in all I have 2 wishes. The pits get filled(Municipal Corporation help !) and I get a laptop to work from home during rainy seasons (Project Manager Help !).
Tuesday, July 12
SAP Web Dynpro Component Concept
A Web Dynpro component can be reused in other web dynpro components. It is a collection of all entities required to create an executable Web Dynpro application.Web Dynpro component has a number of advantages:
Programming becomes structured
Application blocks become manageable
Reusability
Entire software projects can be worked upon by various developers in various time zones.
The Web Dynpro component mainly consists of windows and views and their corresponding controllers. Web Dynpro components can be used within web dynpro components.
It is mandatory to create a Web Dynpro Component if you want to create a web dynpro application. The application contains views and windows and their corresponding controllers. All these things can come into existence only when a component is in place. To a Component, a Component can talk. Also to a Component, a user can talk. These two type of communications are possible thourgh Component Interfaces.
So each component has its interface. Data and Functionality of a component can be accessed through this Interface.
For this communication to take place, components need to be enbedded. For example, In a Component called TravelComp, there is a method called Speed(). If you another Component called MainComp wants t ouse the method Speed(), It has to enbed the TravelComp first. Then Through the Interface of the TravelComp, MainComp can call the method called Speed() Provided that method is Public in TravelComp.
Lifetime of a Web Dynpro Component
When you create a Web Dynpro Application, you need to create the web dynpro component first. Web Dynpro Component will beinstantiated on the launch of the web dynpro application. This is the beginning of the lifetime of a web dynpro component. The first method executed when a web dynpro component gets instantiated is wdDoInit(). The lifetime of a web dynpro Component is ended when the application itself is shut down or logged off. For embedded Components, the case is a little different. Embedded components are not instantiated unless they are required. So if you call a method present in a embedded component, they will get instantiated otherwise they won't. It is also possible to control the lifetime of a embedded component. This can be done programatically using a Java API. You can create or destry the embedded component instance as and when required.
Related Posts :
SAP Web Dynpro Component Concept
SAP's Standard UI technology Web Dynpro for ABAP
SAP Web Dynpro Terminology
Sunday, July 10
SAP NetWeaver - an Ambitious Vision
Everbody has got to have a vision in life. In Columbus’ case it was finding a better route to Asia by the way of sailing west. (Viola! there was a new world on his way.) For Galileo it was invention of a telescope for viewing of the planets and discovery of satellites around Jupiter. For you, it can be just making sense of all the technical things your company has to deal with daily so that you and your IT people don’t end up being old for their time.
In such a case, you’ll be glad to hear that SAP NetWeaver is an ambitious vision at its core, for improving Information Technology,that includes the software and hardware running the world of business. But SAP NetWeaver is not just a vision but a set of tools and methodologies that has the ability to take your company to higher places.
Frankly, SAP NetWeaver is not any normal topic for a book. It’s not any kind of hobby like yoga, sailing, or personal finance. It’s not a programming language nor even a word processor. SAP NetWeaver is a super-sized serving of technology and tools that is made up of products and which are useful to the corporate decision maker and also to the technologists who work together for solving huge information challenges.
You can do the following with SAP NetWeaver:
Make a portal which gives each user exactly that which he needs from your applications.
Providing a single view of information from every part of your company and delivering it to employees how and when they need it.
Knitting together into one streamlined interface processes which are distributed in bits across many applications.
Since it is based on the latest technology and approaches the business processes, SAP NetWeaver increases the flexibility and allows change throughout your enterprise. Not bad, right?
Though SAP NetWeaver isn’t a typical topic, SAP and its customers and partners know that it’s a topic which needs the right approach, that puts up complex ideas and processes into terms in such a way that everybody can understand. The world of Information Technology has become complex and vast and hence it’s hard to keep track of all the technical terms and acronyms and how they are related. Enterprise application integration, enterprise portals, data warehouses, model-driven development, business process management, and service-oriented architecture all come under SAP NetWeaver. How does any average guy or girl go to even start to make sense of it?
This article gives you an idea of plowing through the conceptual algebra that you usually get to read in the the McKinsey Quarterly and Harvard Business Review. This book helps you in avoiding the deep complexity of the technology which makes enterprise applications work. On the other hand, it provides a clear and simple explanation for the entire landscape of Information Technology by explaining how this SAP NetWeaver can help you master the complexity of it and helps you to get more value from your investment.
Related Posts:
Major Facts on SAP NetWeaver Portal Implementation
Friday, July 8
Major Facts on SAP NetWeaver Portal Implementation
Whenever you start your work on end-to-end SAP Netweaver Portal Implementation project, there is one question you will. What is that which takes in the Whenever you start your work on end-to-end SAP Netweaver Portal Implementation project, there is one question you will. What is that which takes in the making of a successful SAP NetWeaver Implementation? The required things for successful SAP NetWeaver Implementation would be Usable screens, security, landing pages, rich user experience, stable server landscape etc...
The time for loading the home page or landing page is a major factor that your end users can consider to judge the performance of NetWeaver Portal . The navigation clicks are another important factor which is the number of links that are used to open the required page or an application. Almost every website takes these two factors into consideration.Here comes the role of usability specialist who takes care that the Netweaver has both these factors in favour. Still, mosty 3rd party design firm is used to out sources design documents and wire-frames of the portal page structure.
One other mistake which a portal consultant generally tends to over look is the use of PAM (Product Availability Matrix), which is the most handy tool that helps in hassel free implementation. Few of its features are that it list outs major version dependencies, supported and unsupported features and SP level informations. With the use of PAM, Its advisable to determine the complexity and understand scope of implementation .
Some major facts on NetWeaver Portal Implementation:
Be sure that the homepage images are not heavy.
Use of static pages which consume fewer resources in case you have SSO implemented.
Horizontal scroll bars are best avoided. Minimizing of scrolling effects and scroll bars should be done.
User navigation should be made easy with fewer links.
Make use of cache for improving page load time and performance .
To make it easy for users you can enable help, forgot password links on homepage..
Do not use KM object rendering on homepage whenever possible.
Ensure that server is load balanced and there are properly sized mirror nodes. You can increase virtual memory whenever you have good a RAM.
Excessive use of delta links that navigates deeper in hierarchy to be avoided. Portal renders each object by navigation node. More is the page load time when there are more number of nodes.
While using KM for document management and storage, proper taxonomy should be used. Never stuff documents in a single folder . not more than 50 documents are recommended in one folder.
For the iViews that are relatively slow It is recommended to have iView isolation method as “URL” . This isolation method decreases the usage of portal application thread and eliminates the page load errors .
Hoping that this post would be of some use for smooth and error free end-to-end SAP NetWeaver Portal implementation.
Monday, July 4
Delta Links and Chained Objects
Delta link relates two objects of the Portal Content Directory. The objects are called source and the target object. The source object passes its property values to the target object’s property values. Any changes made to source object get copied to the target object and become visible in the target object. Any change made in the target object do not have any effect on the source object.So target Objects can be reused without changing the source object.
Using the delta link, you can protect your objects and the objects provided by SAP and other vendors from being modified.
Chained objects can be created using the delta link concept. So depending on its position in the chain, an object can be a source object as well as a target object.
Related Posts:
SAP EP Page Builder
SAP EP Knowledge Management
SAP EP CM Components
SAP EP TREX Components
SAP EP Connectors
SAP EP Personalizing Your Portal
SAP EP Delegated Administration
SAP EP Super Administration
SAP EP User Administration
SAP EP Content Administration
Using the delta link, you can protect your objects and the objects provided by SAP and other vendors from being modified.
Chained objects can be created using the delta link concept. So depending on its position in the chain, an object can be a source object as well as a target object.
Related Posts:
SAP EP Page Builder
SAP EP Knowledge Management
SAP EP CM Components
SAP EP TREX Components
SAP EP Connectors
SAP EP Personalizing Your Portal
SAP EP Delegated Administration
SAP EP Super Administration
SAP EP User Administration
SAP EP Content Administration
Saturday, July 2
System Administration
System administration consists of system configuration and monitoring. System configuration consists of content management configuration and TREX configuration and Index administration.
You need to configure various Content Management (CM) components so that CM matches your system environment and your usage scenarios.
Content Management Components to be Configured are
For storing and/or retrieving metadata and content, repositories are needed. You need to configure repositories.
There are few Global services which provide functions to be used in those repositories
These services may be index management service used for classification and retrieval, publishing pipeline that can be used for rendering and transforming content and the notification service which can be used for informing users about content-related functions.
These services include
the subscription service for making users aware of the changes to content
Discussion service for managing discussion groups.
Repository filters to process metadata and content.
Utilities to provide supplementary functions for applications and services
KM user interface
Content access protocols (WebDAV)
Form-based publishing application
Where is Configuration Data Stored It is stored on the portal server:
Where is Configuration Data Stored It is stored on the portal server:
in In the directory which contains central configuration data.
in In the directory that is accessible through /etc repository.
in In the directory which contains Java parameter files related to Knowledge Management.
Central Configuration Data
The CM data is managed by the the configuration framework and it is stored in XML form. You can edit this data in the portal with a configuration iView.This data is stored under
/usr/sap/
The variables
User AdministrationContent Administration
Content Administration
Content creation and maintenance is done by Content Administrator. Content are the objects or components on the portal desktop that bring information to portal users.
iViews are major part of Portal content. Each iView brings to the portal desktop specified data from an information resource such as a ERP system, relational database, CRM system, collaboration tool, enterprise application, e-mail exchange system, World Wide Web, intranet etc. Each time iViews are launched, they bring latest information.
From iViewStudio (www.iviewstudio.com), iViews can be imported into the portal environment Yahoo! content modules also can be integrated into the portal as iViews, There are few templates provided with portal installation; those can be used to create iviews. Also Enterprise Portal administration tools, can be used to create custom iviews.
So where are the iviews displayed ? Generally in portal pages. Again, pages can be created or imported . The page would contain a list of iViews and layout specifications. Also worksets and business packages can be imported. Worksets bring together the pages, iViews and roles. Business packages are groups of worksets. These worksets are related with each other.
Which content will accessed by which user is defined by role definitions. task-oriented content is what a portal contains. Also, role determines the navigation structure in the SAP EP. The navigation structure contain top-level navigation and detailed navigation tree. A user can navigate in the SAP Enterprise portal content by clicking tabs in top-level and detailed navigation.
Unifier projects are part of Additional content. A Unifier project can integrates an external application such as a database, enterprise application, legacy system into the SAP Enterprise Portal. For example, a Unifier project can launch SAP system transactions and enable end-user t use it. Also Drag&Relate can be used to interrelate data from the SAP system transactions and various other portal information resources. You can integrate various Unifier projects into SAP Enterprise portal environment.
Delta Links and Chained Objects
Related Posts:
Delegated Administration
Super Administration
User Administration
System Administration
iViews are major part of Portal content. Each iView brings to the portal desktop specified data from an information resource such as a ERP system, relational database, CRM system, collaboration tool, enterprise application, e-mail exchange system, World Wide Web, intranet etc. Each time iViews are launched, they bring latest information.
From iViewStudio (www.iviewstudio.com), iViews can be imported into the portal environment Yahoo! content modules also can be integrated into the portal as iViews, There are few templates provided with portal installation; those can be used to create iviews. Also Enterprise Portal administration tools, can be used to create custom iviews.
So where are the iviews displayed ? Generally in portal pages. Again, pages can be created or imported . The page would contain a list of iViews and layout specifications. Also worksets and business packages can be imported. Worksets bring together the pages, iViews and roles. Business packages are groups of worksets. These worksets are related with each other.
Which content will accessed by which user is defined by role definitions. task-oriented content is what a portal contains. Also, role determines the navigation structure in the SAP EP. The navigation structure contain top-level navigation and detailed navigation tree. A user can navigate in the SAP Enterprise portal content by clicking tabs in top-level and detailed navigation.
Unifier projects are part of Additional content. A Unifier project can integrates an external application such as a database, enterprise application, legacy system into the SAP Enterprise Portal. For example, a Unifier project can launch SAP system transactions and enable end-user t use it. Also Drag&Relate can be used to interrelate data from the SAP system transactions and various other portal information resources. You can integrate various Unifier projects into SAP Enterprise portal environment.
Delta Links and Chained Objects
Related Posts:
Delegated Administration
Super Administration
User Administration
System Administration
User Administration
User administrator does the tasks that are relevant to role assignments and user management. SAP User Management Engine (UME) provides user management functions in SAP Enterprise Portal. This runs as an integrated service in the SAP EP framework.
Portal Content Directory (PCD) manages the Roles.
In this post we will discuss about the tasks that a user administrator performs. These tasks are mostly routine tasks such as:
Unlocking users, searching for users, creating users etc. User Management Administration Console is used to perform these tasks.
Assigning roles to users and groups
Mapping users
Replication of user data into external systems.
Importing user data
Assigning roles to users and groups
SAP enterprise portal provides a user interface for each user according to the roles allocated to him or her. Things in the top-level navigation and in the portal pages are determined from his or her roles. So based on their function in the company, it is very important to assign users and groups to specific roles.
Prerequisites
To do this, administrator must have following roles: pcd:portal_content/administrator/super_admin/super_admin_role pcd:portal_content/administrator/content_admin/content_admin_role pcd:portal_content/administrator/system_admin/system_admin_role pcd:portal_content/administrator/user_admin/user_admin_role
Procedure
Select user or group to which you wnat to assign a role.
Select Edit in the right column.
Select one or more roles if you want to assign one or more roles to the user or group. select Add. Similarly you can remove one or more roles chosen by you.
Choose Save.
the same procedure is followed to assign users and groups to roles as is followed for assigning roles to users and groups except that Edit needed to chosen for a role in the first screen. And in the second screen, users and groups are chosen.
The user's portal user ID is stored in the user repository for the enterprise portal. To enable Single Sign-On, a user's portal user ID and password must be mapped to the corresponding user ID for each system in which the user ID is different.
Mapping Users
There are two methods of Single Sign-On for which User mapping is required:
SSO using user ID and password:
here, it is necessary to map the portal user ID and password to the user ID and password in component system.
Using SAP logon tickets for Single Sign-On:
If the SAP user IDs are the same as the portal user IDs, user mapping is not needed. If not, we must define a SAP reference system. This system is used for user mapping. In the user's SAP logon ticket, a user's portal user ID and the SAP user ID is stored. When a logon attempt to the component system is made, the system extracts the user ID from the logon ticket.
It is possible to map a user, a group, or a role to a user ID in a system which is connected to the SAP Enterprise portal. But in case of the SAP Systems connected to SAP EP, we cannot map roles or groups to a user in a SAP System. Only a user can be mapped to a user. When a iView that needs data from a connected system is accessed, SAP logon tickets are not supported, the procedure is that SAP Enterprise portal checks whether the user is mapped to a user in the corresponding system and if yes then SAP EP logs on using the mapped user data. If not, it checks for the group to which the user belongs whether the group is mapped in the component system or not. If yes, SAP EP logs on using the mapping. If not, it checks for roles. If not, the iView will prompt the user to enter mapping data but foe this, iView needs to be Programmed.
Related Posts:
Delegated Administration
Super Administration
Content Administration
System Administration
Portal Content Directory (PCD) manages the Roles.
In this post we will discuss about the tasks that a user administrator performs. These tasks are mostly routine tasks such as:
Unlocking users, searching for users, creating users etc. User Management Administration Console is used to perform these tasks.
Assigning roles to users and groups
Mapping users
Replication of user data into external systems.
Importing user data
Assigning roles to users and groups
SAP enterprise portal provides a user interface for each user according to the roles allocated to him or her. Things in the top-level navigation and in the portal pages are determined from his or her roles. So based on their function in the company, it is very important to assign users and groups to specific roles.
Prerequisites
To do this, administrator must have following roles: pcd:portal_content/administrator/super_admin/super_admin_role pcd:portal_content/administrator/content_admin/content_admin_role pcd:portal_content/administrator/system_admin/system_admin_role pcd:portal_content/administrator/user_admin/user_admin_role
Procedure
Select user or group to which you wnat to assign a role.
Select Edit in the right column.
Select one or more roles if you want to assign one or more roles to the user or group. select Add. Similarly you can remove one or more roles chosen by you.
Choose Save.
the same procedure is followed to assign users and groups to roles as is followed for assigning roles to users and groups except that Edit needed to chosen for a role in the first screen. And in the second screen, users and groups are chosen.
The user's portal user ID is stored in the user repository for the enterprise portal. To enable Single Sign-On, a user's portal user ID and password must be mapped to the corresponding user ID for each system in which the user ID is different.
Mapping Users
There are two methods of Single Sign-On for which User mapping is required:
SSO using user ID and password:
here, it is necessary to map the portal user ID and password to the user ID and password in component system.
Using SAP logon tickets for Single Sign-On:
If the SAP user IDs are the same as the portal user IDs, user mapping is not needed. If not, we must define a SAP reference system. This system is used for user mapping. In the user's SAP logon ticket, a user's portal user ID and the SAP user ID is stored. When a logon attempt to the component system is made, the system extracts the user ID from the logon ticket.
It is possible to map a user, a group, or a role to a user ID in a system which is connected to the SAP Enterprise portal. But in case of the SAP Systems connected to SAP EP, we cannot map roles or groups to a user in a SAP System. Only a user can be mapped to a user. When a iView that needs data from a connected system is accessed, SAP logon tickets are not supported, the procedure is that SAP Enterprise portal checks whether the user is mapped to a user in the corresponding system and if yes then SAP EP logs on using the mapped user data. If not, it checks for the group to which the user belongs whether the group is mapped in the component system or not. If yes, SAP EP logs on using the mapping. If not, it checks for roles. If not, the iView will prompt the user to enter mapping data but foe this, iView needs to be Programmed.
Related Posts:
Delegated Administration
Super Administration
Content Administration
System Administration
Super Administration
The role of a super administrator is filled by a person who, after installating the SAP Enterprise Portal, stands responsible for initial administration.
This role holds the permissions given to all the other three administrator roles which include the user administrator, content administrator, and system administrator. For in depth details of the pre-framed administrative roles, I shall write an article for pre-configured roles. The super administrator can access the entire set of tools in this portal administration environment.
Following the installation,the super administrator is the first one to be entering the portal. SAP Enterprise Portal comes with a tough-coded username and also a password for the use of the super administrator. After the installation process, the super administrator can log on to the portal with the help of his user ID. When you go beyond the initial configuration stage, it is better to change the initial user IDs and passwords or disable the super user itself.
The main tasks of the super administrator after logging on to the portal and after qualifying the basic functionality are as follows:
Connecting to the base of users who will be working in the portal so that the super administrator sets up at least the minimal user management configuration. We should know configuration of user management in the Enterprise portal for further information.
The end user and the administrative roles needed for the organization should be planned out carefully. The role structure can be put in gradually, starting with a test environment in mind set up and later on gradually moving towards a live production portal with the primary target audience being the end users.
At this point, the super administrator assigns users for the other administrator roles, thereby distributing the responsibilitiesof administration. The super administrator can modify the pre-configured administration roles when they do not fit the needs of the company,and in turn extend them as needed.Before you begin the modification of the pre-configured roles, delta links and SAP Content objects should be well known.
Now the super administrator distributes the default initial content to relevant system administrators and content administrators in the company by assigning permissions for these users. Initial content has objects and templates and portal components, which can be used as a base for creating portal content.
Once delegating the administrative tasks is done by the super adminostrator, the assigned content managers start the process of importing content and roles which can be from their own sources and iViewStudio, and also in-house content developers can parellally start developing content which is specific to the organization. Needs
One optional thing is that parellal to the steps above , the process of setting up and configuring the Knowledge Management platform in the portal should also be done.
Related Posts:
Delegated Administration
Super Administration
User Administration
Content Administration
This role holds the permissions given to all the other three administrator roles which include the user administrator, content administrator, and system administrator. For in depth details of the pre-framed administrative roles, I shall write an article for pre-configured roles. The super administrator can access the entire set of tools in this portal administration environment.
Following the installation,the super administrator is the first one to be entering the portal. SAP Enterprise Portal comes with a tough-coded username and also a password for the use of the super administrator. After the installation process, the super administrator can log on to the portal with the help of his user ID. When you go beyond the initial configuration stage, it is better to change the initial user IDs and passwords or disable the super user itself.
The main tasks of the super administrator after logging on to the portal and after qualifying the basic functionality are as follows:
Connecting to the base of users who will be working in the portal so that the super administrator sets up at least the minimal user management configuration. We should know configuration of user management in the Enterprise portal for further information.
The end user and the administrative roles needed for the organization should be planned out carefully. The role structure can be put in gradually, starting with a test environment in mind set up and later on gradually moving towards a live production portal with the primary target audience being the end users.
At this point, the super administrator assigns users for the other administrator roles, thereby distributing the responsibilitiesof administration. The super administrator can modify the pre-configured administration roles when they do not fit the needs of the company,and in turn extend them as needed.Before you begin the modification of the pre-configured roles, delta links and SAP Content objects should be well known.
Now the super administrator distributes the default initial content to relevant system administrators and content administrators in the company by assigning permissions for these users. Initial content has objects and templates and portal components, which can be used as a base for creating portal content.
Once delegating the administrative tasks is done by the super adminostrator, the assigned content managers start the process of importing content and roles which can be from their own sources and iViewStudio, and also in-house content developers can parellally start developing content which is specific to the organization. Needs
One optional thing is that parellal to the steps above , the process of setting up and configuring the Knowledge Management platform in the portal should also be done.
Related Posts:
Delegated Administration
Super Administration
User Administration
Content Administration
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
Personalizing Your Portal
SAP Enterprise Portal is necessarily designed to meet work-related needs. The portal delivers a wide spectrum of valuable source of information, with its robust connectivity framework . Additionally , there are its special features which enable you to focus mainly on data that is relevant to your daily processes of decision making. Personalization of your portal in various ways, from finding which available content can be displayed and to how and where you display it.
Features
The customization possibilities of the portal are as follows. Complete information can be found in the SAP Enterprise Portal End User Guide.
Page Preferences
For personalizing your page preferences, select the portal page which you need to update,then click the Personalize link that is located in the masthead, and then choose Page.
The following can be done to personalize your page:
Adding Content: Your portal content administrator is the one which defines the iViews to which you have access. The content that is available to you is displayed byThe Portal Catalog. Right-click an iView that you want to display in the page and then choose Add iView to Page. After saving, in the Personalized Page area of the navigation panel and in the content area you can see the added iView.
Arranging the Content: the layout of the content displayed in the page can be rearranged.
Additional Content: A portal administrator can obtain more iViews from iViewStudio, which can later be assigned to you.
Portal Preferences
click the Personalize link in order to personalize your portal preferences, , located in the masthead, and choose Portal. You can personalize the following things:
Portal Theme: for changing the look and feel of the portal by selection of a theme from the portal's theme library. Select the Portal Theme link, from the Detailed Navigation area, and choose the theme you want
from the Set Portal Theme drop-down list.
Portal Language : you can change the language that appears in portal UI strings. Select the Portal Language link, from the Detailed Navigation area, and the language in which you want to work from the Set Portal Language drop-down list.
User Mapping: You can set User Mapping for enabling Single Sign-in which permits the portal to use your portal logon credentials for accessing various systems which require different logon credentials. select the User Mapping link, from the Detailed Navigation area, a data source (system) from the Data Source Settings dialog, and then enter a username and password with which you can connect.
User Password:You can change your login password. Select the User Password link, from the Detailed Navigation area, and enter your old password in the User Password dialog and now enter and confirm a new password, and choose Save and then Close.
User Profile:You can update the user profile that you created when you are first registering. Select the User Profile link, from the Detailed Navigation area, and update or add any necessary information in the Modify My Profile dialog.
Related Posts:
Page Builder
Knowledge Management
Delegated Administration
Features
The customization possibilities of the portal are as follows. Complete information can be found in the SAP Enterprise Portal End User Guide.
Page Preferences
For personalizing your page preferences, select the portal page which you need to update,then click the Personalize link that is located in the masthead, and then choose Page.
The following can be done to personalize your page:
Adding Content: Your portal content administrator is the one which defines the iViews to which you have access. The content that is available to you is displayed byThe Portal Catalog. Right-click an iView that you want to display in the page and then choose Add iView to Page. After saving, in the Personalized Page area of the navigation panel and in the content area you can see the added iView.
Arranging the Content: the layout of the content displayed in the page can be rearranged.
Additional Content: A portal administrator can obtain more iViews from iViewStudio, which can later be assigned to you.
Portal Preferences
click the Personalize link in order to personalize your portal preferences, , located in the masthead, and choose Portal. You can personalize the following things:
Portal Theme: for changing the look and feel of the portal by selection of a theme from the portal's theme library. Select the Portal Theme link, from the Detailed Navigation area, and choose the theme you want
from the Set Portal Theme drop-down list.
Portal Language : you can change the language that appears in portal UI strings. Select the Portal Language link, from the Detailed Navigation area, and the language in which you want to work from the Set Portal Language drop-down list.
User Mapping: You can set User Mapping for enabling Single Sign-in which permits the portal to use your portal logon credentials for accessing various systems which require different logon credentials. select the User Mapping link, from the Detailed Navigation area, a data source (system) from the Data Source Settings dialog, and then enter a username and password with which you can connect.
User Password:You can change your login password. Select the User Password link, from the Detailed Navigation area, and enter your old password in the User Password dialog and now enter and confirm a new password, and choose Save and then Close.
User Profile:You can update the user profile that you created when you are first registering. Select the User Profile link, from the Detailed Navigation area, and update or add any necessary information in the Modify My Profile dialog.
Related Posts:
Page Builder
Knowledge Management
Delegated Administration
Connectors and Unification
Connectors
Connectors are those which allow integration of application servers with Enterprise Information Systems (EIS) and enterprise applications with into the portal platform. The creation and running of connectors is supported by the portal runtime environment. Various services provided by the portal runtime are including a Web service that make connectors available to external clients, and also it allow these clients to access an enterprise system as if they were local. For doing this, the SOAP XML protocol is implemented to pass requests and responses between applications, like specific connectors and iViews.
Also, other portal services serve to making available a wizard framework for the creation of iViews for specific connectors, as an intermediary for user authentication and security, and also for connecting to back-end applications using existing connectors. Offering APIs for creation of local connectors, a software development kit (SDK) is available. This SDK is a part of the Portal Development Kit (PDK) which can be obtained at http://www.iviewstudio.com from the DevZone.
Unification
Unification helps to integrate the enterprise information sources and to provide unified access for its structured data. It is the engine at the back end which drives the union of databases, enterprise applications, and legacy systems in SAP Enterprise Portal. Through a web service, the Portal Framework helps in connecting the Unification Server, and the unifiers that runs over it.
The most important aspect of the Unification Server is the patented Drag & Relate technology. On top of existing data sources (applications and databases), you implement this technology. As such there are no changes needed to the IT infrastructure of your company. To implement this Drag & Relate technology, you make use of the development environment of the Unification Server which helps to create a Database Unifier project, that helps us in retrieving of structured data from the database. Other unifiers can also be installed on the Unification Server, in order to extend the development tools for handling of enterprise applications like SAP R/3, SAP BW, oracle Applications. The unifiers helpful for leveraging the target applications' own architecture, security mechanism, user interfaces and customizations.
At the front end, the user works from project’s Detailed Navigation Panel in the Portal, and queries data sources with the use of Drag & Relate which consists of user dragging the visual elements that represent data and dropping them on other elements, and also interrelating of the data for creating queries dynamically.
Related Posts:
Knowledge Management
Personalizing Your Portal
Delegated Administration
Connectors are those which allow integration of application servers with Enterprise Information Systems (EIS) and enterprise applications with into the portal platform. The creation and running of connectors is supported by the portal runtime environment. Various services provided by the portal runtime are including a Web service that make connectors available to external clients, and also it allow these clients to access an enterprise system as if they were local. For doing this, the SOAP XML protocol is implemented to pass requests and responses between applications, like specific connectors and iViews.
Also, other portal services serve to making available a wizard framework for the creation of iViews for specific connectors, as an intermediary for user authentication and security, and also for connecting to back-end applications using existing connectors. Offering APIs for creation of local connectors, a software development kit (SDK) is available. This SDK is a part of the Portal Development Kit (PDK) which can be obtained at http://www.iviewstudio.com from the DevZone.
Unification
Unification helps to integrate the enterprise information sources and to provide unified access for its structured data. It is the engine at the back end which drives the union of databases, enterprise applications, and legacy systems in SAP Enterprise Portal. Through a web service, the Portal Framework helps in connecting the Unification Server, and the unifiers that runs over it.
The most important aspect of the Unification Server is the patented Drag & Relate technology. On top of existing data sources (applications and databases), you implement this technology. As such there are no changes needed to the IT infrastructure of your company. To implement this Drag & Relate technology, you make use of the development environment of the Unification Server which helps to create a Database Unifier project, that helps us in retrieving of structured data from the database. Other unifiers can also be installed on the Unification Server, in order to extend the development tools for handling of enterprise applications like SAP R/3, SAP BW, oracle Applications. The unifiers helpful for leveraging the target applications' own architecture, security mechanism, user interfaces and customizations.
At the front end, the user works from project’s Detailed Navigation Panel in the Portal, and queries data sources with the use of Drag & Relate which consists of user dragging the visual elements that represent data and dropping them on other elements, and also interrelating of the data for creating queries dynamically.
Related Posts:
Knowledge Management
Personalizing Your Portal
Delegated Administration
Page Builder Component
The Page Builder Component is the one that assembles the content of a page according to the already defined page layout. For instance, for the first time,when you run the portal, the Page Builder will assemble the initial portal page, and also the content of the iViews in it. A portal page comprises of the following:
Related Posts:
Personalizing Your Portal
Delegated Administration
- a default active layout and list of possible layouts
- iViews that are located in the page
At the time of design, each page has one or more layouts. Later on, when iViews are added to that page, specific active page layout deterrmines their placement. All this is stored in the Portal Content Directory (PCD). SAP Enterprise Portal contains a set of pre-defined page layouts that are based on the layout templates. Additionally , new layouts can also be developed. The definition of a layout is brought out by proprietary tags that are used in Java Server Pages (JSP) which define HTML elements for the pages.
Layout templates can be created by the portal components, like HTML-Business for Java (HTMLB) that manage themes and styles, and also provide with a complete set of easy-to-use Web controls,that describe the HTMLB controls, their usage, types ,attributes, and how to set them with the JSP-tag libraries and the class libraries.
The Page Builder can also assemble iViews in a page like:
- Inserting the output of the iViews into the HTML for a page while retrieval of these iViews.
- as an alternate, IFRAMES in the page request for the content of iViews which can be from the Portal Framework, or from other sources too which can be the Internet Transaction Server (ITS) or any other Web site too.
- For authentication and Single Sign-On,User management and security tasks,
- Obtaining the requested object from the Portal Content Directory (PCD)
- Objects managing the theme and styles of the portal
- Framework that determines wizards in the portal
- Administration of the iViews.
Related Posts:
Personalizing Your Portal
Delegated Administration
Administrative Aspects of SAP Enterprise Portal
This post discusses the administrative aspects, authoring and
deployment of a custom SAP Enterprise Portal. SAP Enterprise Portal is
a scalable portal which can integrate unlimited content because it has open
architecture. Portal content can be integrated from various sources such as groupware
applications, Web sites, enterprise applications, legacy systems, databases,
and document directories.
SAP Enterprise portal provides complete set of tools to manage and
monitor and administer the SAP EP within one coherent environment. These
administrative tools are created as portal pages or iViews enabling you to do
administration tasks according to a particular business scenario.
After Installation and delegation of tasks, portal administrator
tools are used to either import or create custom portal content. After that roles
are built. These roles consist of specific subsets. Each subset consist of
specific portal content. These subsets are assigned to various enterprise
users.
There are various services and procedures that are indirectly
involved in distribution to portal users and information processing for portal
users. These services may include security, monitoring the portal server, user
management, and changing the portal design to reflect a company’s brand.
Also Knowledge Management platform can be implemented.
KM allows portal users to intuitively and selectively target documents and files
and at distributed information sources.
SAP Unification Server helps in
integrating the resources of a enterprise's information systems. Also it provides
unified access to structured data of the enterprise. It drives the unification
of databases, enterprise applications and legacy systems in SAP Enterprise
Portal.
Page Builder
Knowledge Management
CM Components
TREX Components
Unification
Connectors
Personalizing Your Portal
Delegated Administration
Subscribe to:
Posts (Atom)