Google+ SAP MiniApplications Programming and Set up - SAP ABAP

SAP MiniApplications Programming and Set up

SAP MiniApps type the push portion of the mySAP Office that delivers all kinds of content to the user. They're the home windows to underlying functions and productivity tools and deliver data and services to the person in a easy way.

The questions about MiniApps programming and installation to be answered are:



  1. Which MiniApps are required?
  2. Which users need which MiniApps?
  3. Can I use existing MiniApps or do I've to develop own and new ones?

Recommendations and suggestions embody:

  1. In the SAP MiniApps Neighborhood, yow will discover design guides and improvement libraries to scale back the event effort for MiniApps.
  2. MiniApps have totally different contents. You find general and position-particular ones. To scale back the administration in the first phase, it's helpful to integrate only normal ones.
  3. When you write your personal MiniApps that present particular person information that depends on the person logging in, and you want to use SSO (Single Sign-On) performance for Mini Apps that are not based mostly on SAP’s ITS know-how, SSO tickets or digital certificates (X.509) are required. As a abstract of the significance of this subject, the following factors should be noticed:
  4. One other foremost part within the mission if you do not use Mini Apps from the community
  5. To program your individual MiniApps can take a couple of days, depending on the applying and complexity
Integration of Third-Celebration Purposes and mySAP

Elements

Info is one of the most necessary kinds of content in an Enterprise Portal. The Enterprise Portal has to offer the likelihood to integrate functions and external services, resembling delivery providers, for example. Only such a consumer-centered mixture of information, functions, and companies will guarantee the success and acceptance of an Enterprise Portal. The mySAP Workplace offers this possibility. The inquiries to be answered about integrating third-celebration functions and mySAP parts are:

  1. How can I call an utility from the LaunchPad or MiniApps?
  2. How can I integrate a sure function or transaction from a third-occasion software?
  3. My mainframe application should seem like a Web application, if possible. How do I integrate this?
  4. How can I integrate an application without altering the back-end utility?
  5. Users should not must kind in information from one function into another function. Is there a way to mechanically switch information, for example, utilizing Drag&Relate or XML?
  6. My users employ totally different computers.What do I have to do so that they can take their Office with them wherever they go?
  7. How can I design it so that every user only has to log on as soon as a day, while on the similar time being secure?
  8. Can I synchronize user grasp data from all programs so that I do not need to maintain the information in multiple systems? Can I use our LDAP listing?
  9. Will SSO work with third-social gathering applications built-in into the mySAP Office?
Recommendations and suggestions embrace:

  1. From the outset, the mySAP Workplace has been designed in such a approach that options to the above questions will be discovered utilizing a minimal of resources.
  2. The objective is that users can entry all of the purposes that they require for their work with a minimum of restrictions and with out having to depart the mySAP Workplace. Other than SAP parts, it is possible to combine some other functions within the mySAP Workplace. These include Net-enabled functions, that is, functions which can be based mostly on HTML or Java. Obviously, integrating such a purposes is a comparatively straightforward task.
  3. In addition, non-SAP applications might embrace purposes that aren't Net-enabled. The multitude of present PC functions should even be taken into account.Windows Terminal Companies (WTS) are available to cope with these applications.
  4. Existing non-SAP intranet functions can only use the SSO functionality if the SSO is based on SSO tickets or X.509 certificates. SAP presents a library for utilizing SSO logon tickets with non-SAP applications.
Safety

mySAP Workplace Enterprise Portal ensures excessive safety for e-enterprise by supporting Web security standards, as nicely as by offering state-of-the-art authentication and authorization mechanisms. Authentication and authorization aren't the same.

  1. Authentication identifies a user as to who she or he is.
  2. Authorization supplies access rights to certain content.
Authorization resides within the part systems. No mirroring to mySAP Office is necessary.

Digital certificates (X.509) are supported by mySAP Workplace. To help your company to set up a Public Key Infrastructure (PKI), SAP supports the setup of a PKI through its mySAP Belief Middle Service. Tickets are a solution provided by SAP. The advantage of this approach is that no further infrastructure is required for SSO to work on external systems.

The inquiries to be answered relating to security when implementing an Enterprise Portal are:

  1. Which degree of security is required? Is it adequate to encrypt the data, or should the user be recognized with a digital certificate (X.509, for instance, on a sensible card)?
  2. How do I combine exterior purposes securely over the Web?
  3. Do I would like a new firewall concept?
  4. How do I monitor all network connections, especially from and to the ITS in a worldwide network?
  5. Is it essential to arrange a new PKI, or can I use an present PKI like the mySAP Trust Center Service or VeriSign?

Suggestions and suggestions embrace:

  1. If you want to use a cookie-based mostly SSO mechanism, you should consider utilizing SSO log on tickets instead of ordinary SSO cookies, because tickets are signed with a public key mechanism by the Office server, and no personal data, just like the consumer’s password, is stored. In normal SSO cookies, the username and password are stored.
  2. For a productive system, it's highly recommended to not use cookies, as SSO cookies only work with the same user ID and password in all part systems. Logon tickets solely require the identical consumer ID.
  3. Log on tickets can be licensed by the Office server itself or by the SAP Belief Center. The first choice is very easily installed.
  4. It's at all times a good selection to use SSL encryption (HTTPS) as an alternative of regular HTTP for the communication from Internet browser to Web server as a outcome of HTTP transports all data as plain textual content (also logon info like username and password).
  5. mySAP Passports (X.509 certificates licensed by the SAP Belief Middle) offer a high safety and are freed from charge. This resolution requires an Web connection to SAP.
  6. If you need to maintain the overview over the digital certificates used, you can set up your individual PKI to sign the certificates with your individual certificates authority.
  7. For security causes, customers and roles should be administrated by one individual only.
  8. At all times work based on the “two heads are higher than one principle”: have a second set of eyes look over your work.
As a summary of the importance of this topic, the next points should be noticed:
  1. Vital part of the venture
  2. Planning of this duties takes most of the time
  3. Many alternative departments are involved in these duties

Drag&Relate Operate

The Drag&Relate perform lets you link information from one application with one other application. You presumably can navigate between the various objects within the transactions and the LaunchPad utilizing Drag&Relate. By simply choosing an object (for instance, a purchase order) and dragging it onto another object in the LaunchPad (for example, a Net web page), an exercise is carried out (for example, the delivery status of the acquisition order is displayed). There is not any such factor as a need to remember order numbers or the proper underlying methods; users just do it in probably the most pure way. The Drag&Relate function works between SAP applications; for example, you'll be able to drag an object from the SAPGUI for HTML to another SAP application in the LaunchPad. But additionally it is doable to make use of the Drag&Relate perform with “regular” Internet applications. For instance, the person can drag a material quantity into the online store of the supplier or other functions that help Drag&Relate technology (TopTier technology).

The inquiries to be answered about Drag&Relate performance are:
  1. Which enterprise relations can be utilized for Drag&Relate?
  2. Which exterior functions can be utilized for Drag&Relate?
Recommendations and ideas include:

  1. Verify your business applications.
  2. It is not easy to integrate, especially for non-SAP products.
As a summary of the significance of this topic, the following factors have to be noticed:
  1. These tasks should happen at the end of your mission
  2. Relies upon of the variety of applications to be integrated over

No comments :

Post a Comment