Showing posts with label enterprise portal. Show all posts
Create System Object in the Portal for Connecting to SAP Backend Systems

Create System Object in the Portal for Connecting to SAP Backend Systems

Sanjo Thomas•08:24:00

How to Create System Object in the Portal for Connecting to SAP Backend Systems ( R3/BW/BI)

Portal System Landscape: Portal system landscape is nothing but a collection of SAP or NON-SAP systems (SAP R3/CRM/BW etc), to retrieve the data from each system portal needs to create system object.

System Object: System Object is a set of connection properties to represent an external or SAP systems (SAP R3, /CRM/BW) used to retrieve data into portal iViews. We can create a System Object in any one of the three ways The system object can be created from either of the following:

·       Based on System Template (Template)

·       Based on Portal Content (PAR)

·       Coping Existing Systems (System)

The Required Steps to Create a System Object in the portal are as follows:

·       System Alias settings-

·       Connector settings

·       ITS settings

·       WAS settings

·       User Management Settings

 

Procedure to Create System Object in the Portal:

1.       Login to the portal as Administrator

2.       Go to System Administration -> System Configuration -> System Landscape -> Browse -> Portal Content -> System landscape.

3.       Right click on System landscape then select New in Context menu

4.       Select System from template / from PAR, it will display Template Wizard.

5.       Choose Template based on your Backend System either SAP or NON-SAP and click on the NEXT.

6.       Provide the General properties for this System Object (System name, ID, prefix, master language and description) and click on NEXT.

7.       It will display the tab with System name and 3 radio button options. Select the default one is opens the object for editing and then selects the ok button.

8.       Now the name of the System name will appear under the System landscape folder in -> Portal Content and with default display dropdown as Object and Property Category dropdown list as Showl All.

9.       System Alias Settings : Portal access the backend systems through system aliases only which is the part of creating the system object. A System should have at least one alias which can refer only to one system at a time. 9. In the display dropdown list Select System Aliases, it display System Alias Editor, give Alias name generally <SID>CLNT<CLIENTNO> ex: BI7CLNT100 and select the Add button and Save this properties by save button.

Connector Settings :

10.    Select Object in the display dropdown list and then select Connector in the Property Category drop down list and provide minimum connector properties for example

 

ITS Settings : ITS settings are maintained for displaying SAP transactions in the portal as an iViews.

11.    Select Object in the display dropdown list and then select Internet Transaction Server (ITS) in the Property Category dropdown list and provide ITS properties as follows


WAS Settings : Web AS settings are required to display BW reports and for BSP applications in the Backend Systems such as CRM and BW/BI system.

12.   Select Object in the display dropdown list and then select Web Application Server (WAS) in the Property Category dropdown list and provide WAS properties as follows



 

User Management Settings : The following settings are required for user Management in the system object to connect to SAP backend systems.

Logon Method is either one of the following mechanisms,

UIDPW : When the PORTAL uses a user ID/PASSWORD as credentials.

SAPLOGONTICKET : PORTAL authenticating against the SAP backend system.

The X.509 certificate : PORTAL authenticating against the client certificates.

Note: Single Sign on (SSO) is required for SAP logon tickets and client certificates for SAP backend systems. User Mapping Type : User Mapping Type defines who can maintain the user mapping for the system. Thepossible values for this property are Admin, User, and Admin/user.

admin : Only the administrator can maintain the user mapping.

User : Only the end user can maintain the user mapping.

Admin/user : Both the administrator and the end user can maintain the user mapping.

13.    Select Object in the display dropdown list and then select User Management in the Property Categorydropdown list and fill User Management properties as follows


Test the System Object : To logon to the portal as the common user in both portal and sap R3 system, andcheck the test connection whether the system object which you have created is successful or not.

14.    Select the Connection Test in the display Dropdown list to test the connection with theSAP R/3 backendsystem. It displays system connection Tests screen in this select all check boxes and select the Test button.



15.    If the test connection is successful it display the status column as Green checks as shown above,otherwise it will display as Red checks in this case please verify the connection properties like system alias, ITS,WAS and User Management properties.

Read more
SAP Cloud Platform for portal sites

SAP Cloud Platform for portal sites

Sanjo Thomas•10:00:00

In this blog, I am going to introduce you to SAP Cloud Platform and the user experience-related services. SAP offers a comprehensive platform as a service called “SAP Cloud Platform”. SAP’s customers and partners use this platform and the services to design, develop, and run business applications in the cloud.

They address 3 main issues:
1) Extending SAP solutions – both in the cloud and on premise, for example, building a new user interface for an existing business process in the SAP ERP system. 

2) Building new cloud business applications, leveraging SAP HANA in-memory technology for analytics or the innovative Internet of Things services.

3) Enriching the experience by integrating data coming from various non-SAP and SAP data sources.
SAP Cloud Platform offers a variety of enterprise capabilities you need to succeed in the cloud and build better applications. In your portal project, you may benefit from additional capabilities. For example, you can connect to things such as sensors from machines or other assets.
SAP Cloud Platform offers various capabilities to support the end-to-end process of building portal sites and applications.

You can use Build for early prototyping and user feedback, and the UI theme designer for branding your portal. The actual development is done with SAP Web IDE using SAPUI5-based UI controls and templates. The final application can then be made available to your end users via a portal. If needed, you can enhance the scenarios to make use of special mobile qualities such as access to GPS, contact data, or camera for reading a barcode. You can also inject collaborative features into the business process, enabling users to share their feedback or comments.

The best way to learn more about the platform and experience the comprehensive set of functionalities is via the trial environment. If you have not registered yet, you can request a free personal developer account right away (Follow my blog on how to setup a trial account on SCP).
Most of the platform’s capabilities and services are available for testing and evaluation purposes. There are a few limitations on the number of running Java apps, storage, and, of course, productive usage. Luckily, there is a rapidly growing community that can help and share their experiences along the way.

SCP Homepage

What you see on the first screen is the general layout of the SAP Cloud Platform cockpit. You will see menu items on the left side, you have some navigation items on the top right like a settings dialog for language and visual design, and you have a news area about recent enhancements and notifications you get from SAP, and here also additional information, such as the "Log out" button.


Then we have different data centers around the world that you can choose from in case you go with the productive account. The trial account is only available in the Europe data center.

So what you see here is my personal trial account that has been created for me. Here as well, you see the limitations that come along with the trial edition.
When we open the trial account, we jump directly into the cockpit for administrating this particular account.


And on this overview page you see some high- level information about the account, including the types of application that may be created, or you are going to create over time, as well as subscriptions and services.

Applications – We can create Java applications, HTML5 applications, or maybe HANA specific applications. And in this blog series we will concentrate on portal based or ui5 based scenarios.
If you would like to understand the feature set of Cloud Platform, you get a good impression by opening the Services menu, where we see the different capabilities, such as the "Analytics" services, the "Business Services", "Collaboration" with "SAP Jam", "Data & Storage", "DevOps" is the main part where we have, for example, "SAP Web IDE" and the "Git Service", "Integration", "Mobile Services", and so on and so forth.

The "Portal" is covered in the "User Experience" section, along with, for example, "Build" and the "UI Theme Designer".

SCP also have capabilities to administer and configure topics like persistency, connectivity to other systems, security, the repositories that are connected, and so on and so forth.

Prerequisites
Before you can build your first real portal project, you have to perform a few initial tasks to set up your SAP Cloud Platform account and the necessary infrastructure.

1) The very first steps are about adding account members and assigning them to roles, such administrator, developer, or support user. Based on your contract, certain resources and services are available in your account.
2) In most cases, you will need to set up and configure a secure tunnel to your on-premise landscape, using the SAP Cloud connector.
3) The next step is to define connectivity destinations for each system you would like to integrate – either in the cloud or on premise.
4) Afterwards, you can run the technical configurations for authentication and single sign- on, authorizations, roles, and so on.
5) And usually, you would also create additional accounts, for example for development, test, or production systems.

Once you have completed this initial setup successfully, you can focus on the portal.


Read more