Sunday, October 7
Trust between SAP EP and a backend system
For the portal to communicate with backend systems, a trust
has to established between them. This is done by public-key certificate. The
party wishing to start communication has to present this certificate and the
other party has to accept it. There is
only one certificate, the only default certificate called as
SAPLOGONTICKETKEYPAIR-CERT.
The sertificate has been exported. You need to import it in the backend system. Login to the system, run transaction strustsso2 and choose Import Certificate and select the certificate that you previously exported. Choose Add to Certificate List. Choose Add to ACL.
System Alias
System Alias is a name given to a system. using this name, Portal objects refer to the system using its Alias. A system can have more than 1 system Alsias. but a Alias can not be assigned to more that 1 system.
Alias is a unique idntifier of a System. So for a R/3 development system, the Alias will be differen from that of a R/3 Quality system. So during transport, Alias will not get transported. So new system Aliases has to be defined after transport.
Portal components identify backend system using its Alias. These Alias are defined at design time in the PCD. But SAP EP also provides the option of dynamic system resolution.
dynamic system resolution
At design time, portal component refers to a Alias. At runtime, this Alias resolves to a system based on the conditions. For this resolution to happen, a custom service must exist. At runtime, the portal runtime checks in the PCD whether a custom service is associated with an Alias or not. If a custom service is there, it is used to resolve the Alias to a system. If it is not there, Alias is resolved to the system that is defined in PCD.
Managing System Aliases
Managing system Alias include adding new aliases, editing existing aliases, removing aliases, assigning
existing, unassigned aliases, and assigning default status to one alias per
specific system. All this can be done in the SAP SLD Overview page of SAP EP.
related posts:
Knowledge management component of SAP Enterprise portal
Implementing external facing portal
Creation of custom navigation connector
Navigation in sap enterprise portal
Trust between sap ep and backend system
J2ee course content it training
It training sap training ear training
Java api to retrieve work sets assigned
Could not find system aliasSap ep web dynpro java error srm portal
Unsupportedclassversionerror in sap
Sap ep 73 upgrade related error
Now there are 2 ways to establish trust ie automatic and
manual.
Automatic :
In system landscape overview, choose a system and say establish trust, username and password will be asked to connect to the backend system. Supply and trust will be established.
In system landscape overview, choose a system and say establish trust, username and password will be asked to connect to the backend system. Supply and trust will be established.
Manual :
Export the certificate from SAP Netweaver administrator and Import it into the backend system. In SAP Netweaver administrator, go to Configuration-security-certificates and keys. Go to the Key Storage tab, to the table Key Storage Views and the details of the TicketKeystore view.Choose the default certificate SAPLogonticketKeypair-cert.Choose Export Entry.
Export the certificate from SAP Netweaver administrator and Import it into the backend system. In SAP Netweaver administrator, go to Configuration-security-certificates and keys. Go to the Key Storage tab, to the table Key Storage Views and the details of the TicketKeystore view.Choose the default certificate SAPLogonticketKeypair-cert.Choose Export Entry.
The sertificate has been exported. You need to import it in the backend system. Login to the system, run transaction strustsso2 and choose Import Certificate and select the certificate that you previously exported. Choose Add to Certificate List. Choose Add to ACL.
System Alias
System Alias is a name given to a system. using this name, Portal objects refer to the system using its Alias. A system can have more than 1 system Alsias. but a Alias can not be assigned to more that 1 system.
Alias is a unique idntifier of a System. So for a R/3 development system, the Alias will be differen from that of a R/3 Quality system. So during transport, Alias will not get transported. So new system Aliases has to be defined after transport.
Portal components identify backend system using its Alias. These Alias are defined at design time in the PCD. But SAP EP also provides the option of dynamic system resolution.
dynamic system resolution
At design time, portal component refers to a Alias. At runtime, this Alias resolves to a system based on the conditions. For this resolution to happen, a custom service must exist. At runtime, the portal runtime checks in the PCD whether a custom service is associated with an Alias or not. If a custom service is there, it is used to resolve the Alias to a system. If it is not there, Alias is resolved to the system that is defined in PCD.
Knowledge management component of SAP Enterprise portal
Implementing external facing portal
Creation of custom navigation connector
Navigation in sap enterprise portal
Trust between sap ep and backend system
J2ee course content it training
It training sap training ear training
Java api to retrieve work sets assigned
Could not find system aliasSap ep web dynpro java error srm portal
Unsupportedclassversionerror in sap
Sap ep 73 upgrade related error
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
You are welcome to express your views here...