1 5 6 7 8 9 27 Previous Next

SAP Enterprise Portal

394 Posts

ASUG.png

ASUG has just announced the “call for presentations” for the upcoming ASUG Annual Conference 2014. This year, we have aligned the portal sub-topics areas to reflect the feedback we got from our customers in previous events and based on the latest SAP UI strategy.

 

The sub-topics in the portal track this year are:

 

  • Portals: Portal, Collaboration, Content Management and Search
  • Portals: Portal usability and mobile consumption of the different UI technologies (e.g. Fiori, SAPUI5, Web Dynpro)
  • Portals: Portal Implementation and integration best practices for the different portal deployment options (On-premise and Cloud)

 

 

Call for action

I would like to invite you all to submit your abstracts and share your experience with other customers – on-premise and cloud, desktop and mobile, intranet and extranet, best practices for implementation, and any other experience you can share with your fellow event participates.

 

Guidelines how to write a (catchy and) successful presentation proposal is provided by ASUG in the following link. One personal recommendation, there is nothing like a first impression – you must have a catchy title and share your unique experience with the product.

 

ASUG365.jpg

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

How to submit

You can submit your abstract in the following link http://callforpresentations.asug.com. For any question regarding the submission process you can contact Speakers@asug.com. The deadline to submit a proposal for the event is Friday, January 10th.

 

Why should you submit a presentation? You get complimentary admission, the opportunity to share your knowledge, and showcase yourself and your company

 

As always, I am happy to help. Comment below or write me an e-mail ( Aviad Rivlin).

Hi,
the next TechED event, in Bangalore this time, is about to start and I would like to draw your attention to the hands-on sessions about the Enterprise Portal portfolio. I have been working on the preparation of both sessions, so I would like to share with you some insights into the session contents and hopefully, make you curious to go and get your hands on the systems yourself.

 

The first session is the POP263 - Experience SAP NetWeaver Portal 7.4 in Action. The idea of this session is to enable every participant to get a broad understanding of what SAP NetWeaver Portal is about, what the benefits are and how easy it is to handle. As our experience at the last TechEDs showed that the audience in these hands-on sessions in generally quite heterogeneous, ranging from highly experienced portal experts who are looking for the newest and greatest stuff to complete newbies who want to get a first overview of the SAP portal offering, we decided to use a modular approach for our hands-on session. So that every one will be able to make the most of the 90 minutes hands-on. The session starts with the portal end user experience, showcasing our new demo framework Ozone that shows that the SAP NetWeaver Portal Framework is highly flexible and can be customized to much different user experience than what most people know as the portal standard. Check out this YouTube video to get a first impression of this portal look and feel:


.
After this end user section which we recommend all users to do, we have different modules to choose from - depending on your focus, e.g. a quick walk through Mobile Portal configuration, a general portal content administration exercise including the creation of RSS feeds iViews and a more detailed exercise about SAP Portal Site Management by OpenText. Ohad Levy, Yogesh Purantharan and Sridevi S will be there to answer your questions.

 

While POP263 will teach you how to configure your SAP NetWeaver Portal for mobile access, the focus of session POP264 - Experience the Mobile Portal in Action is on how to create content for your mobile portal, e.g. adding native mobile iViews, the Mobile Universal Work List, or mobile Portal Content Management for document access to your mobile Launcher.  In the second part, you will learn more about Mobile Homepage, a standardized single point of access for mobile applications and content. In this part, you will configure Enterprise Feeds and native mobile apps. Finally, you will have the opportunity to learn how to customize the look and feel of your mobile portal. Itay Sagiv and Ohad Levy will guide you through this exercise and give you lots of additional information around Mobile Portal.

 

So, if you are at TechED Bangalore, don't miss it!
Regards,
Sibylle

This blog talks about the Portal on device branding, we have certain blogs and SAP help link for creating POD contents, but we don’t have any direct guideline for only implementing POD Branding.

The Branding on POD is not like the Portal Desktop Branding like we can just edit them in Portal Display, this is bit different then PCD theme, theme edit option is not supplied with Theme Editor.

This purely defined in Styles sheet (CSS) and LESS desktop Layout (AJAX framework pages/desktop), which are provided in different option as part of “Web Resource Repository” under Content administration.

Let’s go with actual procedure to do POD Branding.

Refer the below screen shot to locate the CSS & SAP standard layouts in Web Resource Repository.

Pod-1.jpg

The “default” folder contains all POD branding source objects, wherein we will need to find the related objects that need to be modified.

Any sort of requirements related the “POD Desktop Background, Logo, any other theme changes” that can be modified in CSS & LESS file as mentioned in screen shots below.

 

1.    Pod-2.jpg

  2.  Pod-3.jpg  .  

Note: the “Palette.less” file is provided with base color containers for all the POD layout, font & background style.

For an example, if we are changing a POD desktop background pattern, which is actually used as Image file and it’s multiplied into more than one numbers to fill the background (refer the below the following screen to locate the file).

               Pod-4.jpg

 

To make the changes in CSS & LESS file, and to add the Custom related theme with Logo, we have to download the “Default” folder then we will have modify the standard them to our custom look and feel.

 

Eventually, the modified folder name has to be set with “Theme id” (which is currently referring in Smartphone and Tablet Desktops in Portal Content).

 

By default the Smartphone and Tablet Desktop are using only sap_tradeshow_plus. So, the same name needs to be set as Theme id to the Default folder.

 

Then upload the modified content to Web resource repository as follows.

Pod-5.jpg

 

Now, you will see a different Look and feel for your background and Logo in smartphone/Tablet Desktops

In order to validate the runtime behavior of you modified content of Smartphone & tablet.

You need to set the master rules in portal under System Administration to bring the smartphone & Tablet desktop to display.

Pod-6.jpg

For an optimal way, you need to create a separate User group for smartphone & Tablet.    

User Groups

To differentiate the Mobile/Tablet call, we need to create a Portal user Group for Smartphone & Tablet, so that it would not merge the content which have been created for both

It will be precisely connected if the access is granted through Portal Groups.

Smartphone_grp & Tablet_grp

Role Mapping

Two roles are required to map the Smartphone and Tablet roles, the corresponding role should be mapped with group.

 

Additional Reference / Links /

#

Description

Location

1

Web Resource repository

http://help.sap.com/saphelp_nw73/helpdata/en/51/1fcc73dba141888489f3f316b1026f/frameset.htm

 

 

 

 

 

Thanks

Sathya

Hi All,

 

SAP notes allow customers to get:

  • Important information and updates
  • Recommendations, tips and hints
  • Solutions and workarounds for problems they are facing

 

Until now, there has been no organized way of providing feedback or remarks for these notes - whether it’s missing additional symptoms, prerequisites, provides a solution that is not clear or any other comment on the note.  Positive feedback is also welcome.

 

Introducing the Enterprise Portal Notes Feedback Category:

When you want to provide feedback on an SAP note in the NetWeaver Enterprise Portal area (component EP-PIN*), you can open a discussion in the forum.

We will use your discussions about the notes for further review and improvement of the notes.

This will have two advantages:

  • Notes will improve  and get closer to real issues
  • You, as customers, will be able to find notes more easily, understand the notes better and reach problem resolution faster

 

How to provide feedback on a note:

  1. Create a new discussion in the SAP NetWeaver Portal area (direct link)
  2. Enter the title: “Feedback on EP SAP Note <note number>”
  3. In the Categories area, check the Enterprise Portal Notes checkbox.
  • This is important in order for us to filter other notes and find these posts directly.

 

 

Example:

noteFeeback.png

 

 

Thanks for your cooperation!

Tal

Hi all,

 

in this blog I want to share some details for implementing two workarounds for referencing the EJB DC from the Standalone Portal Application DC in NWDI for 7.3 development.

The reason for the workarounds is very good described by Krum Bakalsky in one of the answers to this question: http://scn.sap.com/thread/1900441

 

Short description: The Portal DC and EJB DC have different Java EE versions (Portal DC => 1.3 and EJB  => 1.5)

 

In my case I faced a little bit different error message during deployment as in the question I mentioned above :

 

* EJB Model Builder: "META-INF/ejb-jar.xml" not found. For applications prior Java EE 5 this file is mandatory in EJB modules.[message resource bundle missing], file: btexx.com~frwk~ejb.jar#META-INF/ejb-jar.xml, severity: error

 

The corresponding ejb-jar.xml was missing at all. It was simply not generated, since I created the EJB via EJB Wizard of the SAP NWDS and the file is not required from Version 5 of Java EE. The deployment of the corresponding EAR file was successful, but the deployment of the Portal Application which referenced the EJB DC failed with the error message above.

 

To avoid such errors there are two workarounds:

 

Workaround 1: Remove the reference for the EJB public part of type ASSEMBLY

Workaround 2: Align the versions of both DC components.

 

In following I want to describe the steps to implement these workarounds in some more details. 

 

Note: The first workaround is a preferred solution from my opinion, because I can't really estimate the risks of potential problems which can come after the aligning the portal application version to 1.5 (aligning ejb version to 1.3 is useless, since it would mean a step in the past of the java enterprise development ). However both workarounds worked for me. 

 

Workaround 1: Remove the reference for the EJB public part of type ASSEMBLY

 

The EJB DC should normally have already two public parts after creation:

 

  • client (of type COMPILATION)
  • ejbjar (of type ASSEMBLY)

 

EJB public parts.PNG

 

If you create a dependency to the EJB DC you should disable the reference to the "ejbjar" public part (just uncheck the "Build Time" property in dependency details):

 

EJB public parts_2.PNG

 

As a result the jar file of the EJB DC will not be included in the generated deployable artifact of your portal applications (you can check it in <DC project name>/gen/default/deploy/<name>.sda) and the next deployment should be successfull.

 

 

Workaround 2: Align the versions of both DC components.


The other workaround requires the update of the application.xml file in the generated sda artifact of your Portal application. The generated file by default looks like this:

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">

<application>

 

...

 

</application>

 

 

Indeed for the Java EE 5 applications the content of the application file should be:

 

<?xml version="1.0" encoding="UTF-8"?>

<application xmlns="http://java.sun.com/xml/ns/javaee"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5"

xsi:schemaLocation="http://java.sun.com/xml/ns/javaeehttp://java.sun.com/xml/ns/javaee/application_5.xsd">

 

...

 

</application>

 

This change can be accomplished with following steps:

 

  1. Extract the file application.xml from <Portal DC project name>/gen/default/deploy/<name>.sda/META-INF
  2. Change the schema as shown above
  3. Create META-INF folder under the root folder of your Portal Application DC project and place the modified file there
  4. Add the newly created META-INF folder as a resource root in DC configuration:

EJB public parts_3.PNG

5. Build and deploy the DC

 

I hope this information will be helpful for all which want to combine the portal and JEE development in the projects. Happy coding!  

 

Best regards,

Artem

This blog brings you a clear approach to replace the SAP standard Favicon with Custom Favicon for the Portal URL, there are few significant places where the custom favicon needs to be updated.

Replacing SAP standard Favicon which requires OS level location and few system’s directory in Portal system. The adding custom Favicon would show the look and feel and to align with organization branding.

I have just captured few Recommendations.

1. To update in OS level directory, you should have right permission else you would require a help from SAP Basis.

2. Favicon should be designed with some conversion sites (Favicon can be designed from GIF to ICO which always advisable).

3. If there is any Load balancing system which also needs to figured out and replaced with custom favicon by you or Basis team.

4. Replacing Favicon would require system restart.

5. If there are any multiple instances in the server which also needs to be replaced

The custom URL Favicon would be displaying during Java runtime iview loading.Irj_Url_screen.jpg

As per my landscape directory, I replaced the sap standard Favicon with my custom icon in the following locations.

Location 1:

root > adm_prt > sap > SID > J00 > j2ee > cluster > apps > sap.com > com.sap.engine.docs.example> servlet_jsp > _default > root

 

Location1_screen.jpg

Location 2:

root > adm_prt > sap > SID > J00 > j2ee > cluster > apps > sap.com > com.sap.lcr > servlet_jsp > sld > root

Location2_screen.jpg

Location 3:

root > adm_prt > sap > SID > J00 > j2ee > cluster > apps > sap.com > com.sap.lcr > servlet_jsp > sld > root > img

Location3_screen.jpg

 

Location 4:

root > adm_prt > sap > SDI > J00 > j2ee > cluster > server0 > apps > sap.com > irj > servlet_jsp > irj > root

 

Location4_screen.jpg

 

Post Favicon changes, please perform the below steps to get this reflected in runtime,

  1. The system needs to be restarted.
  2. Clear browser cache and try with new IE session for immediate response.

 

Additional Reference

#

Description

Location

1

Help link

http://wiki.sdn.sap.com/wiki/display/Snippets/tutorial+-+Favicon+icon+change

2

Favicon generation

http://favicon-generator.org/

 

Thanks

Sathya

System Landscape

 

SAP Netweaver Portal 7.3 SPS 7

SAP HR 604  SP 0061

EA HR 605 SP 0038

 

General Recommendations

 

SAML requires Single Sign On with a 2048 Bit certificate.

 

Enable trust between Backend and Portal using 2048 bit certs

 

Logon to http://host:port/nwa

Navigate to Configuration > Security > Certificates and Keys > Ticket Keystore

Delete entry SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert

 

Click on Create to create a new SAPLogonTicketKeypair:

create LogonTicketKeyPair1.png

 

In the popup name the new entry SAPLogonTicketKeypair, be sure that the algorithm is DSA and the checkbox Store Certificate is checked

 

create LogonTicketKeyPair2.png

 

In the next step fill the form according to your company needs and click Finish:

 

create LogonTicketKeyPair3.png

 

Now export the newly created TicketKeypair and import it to your backend system (according to the release you have to import in client 000 or the production client (check for messages when opening TA strustsso2))

 

Also do this the other way round:

Export the backend certificate and import it into your portal.

 

Preparing the backend for SAML Authentication

 

In your backend system you have to run the report WSS_SETUP

Go to transaction SA38 and run WSS_SETUP, the program creates a user DELAY_LOGON, this user is used for any Webservice using Message Based Authentication for example SAML Authentication. The ICF Framework cannot acces SOAP Messages, that's why you first get logged in with the Delay Logon user and afterwards it switches to the user maintained in table USREXTID.

 

Maintain users for table usrextid:

Goto transaction SM30 and maintain table rsusrextid:

rsusrextid.png

rsusrextid2.png

Add new entries:

rsusrextid3.png

 

The external ID has to be set as follows Issuer:ExtUserID, in the field user the mapped backend user has to be maintained.

 

Sample Entry in Table usrextid

the following Screenshot shows a sample entry of the user mapping table usrextid

 

usrextid_sample_entry.png

 

 

Set the SAML Issuer

 

Logon to http://host:port/nwa

Navigate to Configuration > Security > Trusted Systems > Web Service Security SAML > Local SAML Attesters

 

MaintainIssuer.png

 

Confifure the Services

In the backend system call Transaction soamanager to maintain your webservice, you have to select the checkbox single sign on with saml

maintain_webservice_backend.png

On the portal side we implemented consumer proxies to consume the webservices provided by the backend system. To maintain the consumer proxis logon to http://host:port/nwa and navigate to SOA > Application and Scenario Communication > Single Service Administration > Consumer Proxies
 

maintain_webservice_portal.png
 
 
 
 
 
 
 
 
 
 





Hi,
today I would like to talk about what to keep in mind, when you are using a custom framework page. In the last years, we set up some demo portals with real nice look and feel, quite different from the standard, e.g. the following ones.

OzoneS.pngSupplier ViewS.pngVintageS.png

 


There are some nice blogs out there on SCN that give you lots of tipps and information how to setup your own custom portal look and feel, but there is also a very comprehensive wiki page that contains links to blogs for beginners and experienced users and that I highly recommend for all that are interested in this topic.

 

So, you can easily find lots of resources with lots of options how to set up a cool UI, but there are also some things to keep in mind, especially if you are using some of our add-ons that complete the portal, e.g. Enterprise Workspaces or SAP Portal Content Management by OpenText.

 

  1. Enterprise Workspaces:

    
a. Enterprise Workspaces use their own flex and html styles to define their appearance. Therefore, in most cases, it will be necessary to adapt the standard appearance to fit your new portal branding. Otherwise, the standard bluish Workspace directory might look quite strange in a reddish portal.
You can find help on creating a new flex or html style in the Enterprise Workspaces documentation  or read the blog about Enterprise Workspaces – Mobile Homepage Branding on SCN, which explains editing HTML styles in detail. The focus is on mobile, but the description works for all HTML UIs.

b. Adding the Tab Strip: The Tab Strip is a control that enables the user to create and open different pages in a workspace and to access administration pages. If you create a custom framework page, you have to make sure it contains the tab strip at the right location. See  the documentation on how to do it.

Tabstrip.png

 

c. Some additional configuration steps are necessary to make your custom framework page run with Enterprise Workspaces, see the documentation for details.

 

   2. SAP Portal Content Management by OpenText

 

Most elements of the PCM look and feel automatically adapt to the portal look and feel, since they are built in Web Dynpro. But there are some pieces like pop-ups or the dialog window when creating a discussion that are determined by the Content Server appearance. These appearances define the look of the Content Server.

 

With PCM delivery, you get an appearance that optimally fits the portal theme SAP Tradeshow Plus and that is automatically mapped to it, so you do not have to care about that. But, as soon as you are using a theme different from Tradeshow Plus, there is no more preconfigured mapping, but the default is used which might not work correctly with your portal. In this case, you should map your theme to the same appearance as the SAP Tradeshow Plus theme and then check if that fits to your new theme in terms of colors. Otherwise, you would need to create your own copy of the SAP appearance, adapt it to your needs and then map it to your theme. This can be easily done by adding the mapping to the configuration file opentext.ini. In PCM documentation you can find more details about that topic.

 

  3. Using Flex Framework

 

When the framework page is Flex, it might happen that parts of the Top Level Navigation are hidden behind the main page content, e.g. if you are using drop down lists for the second level navigation. In these cases,try wrapping the drop-down as a portal component and it will stay on top.

 

 

If this blog was interesting to you, please check out the other blogs in my series about creating sites with SAP NetWeaver Portal.

Wishing you success with building your own custom portal framework,

Sibylle

Welcome to the October and November edition of the SAP Portal News Blog 2013. Read our SAP TechEd recap and all the news around our product portfolio:

 

  • SAP TechEd Impressions
  • HANA Cloud Portal
  • Mobile Portal
  • SAP Portal Deployment Options
  • New Blog Series "Creating Sites"
  • New Training openSAP
  • Announcements
  • Blogs from the Portal Community

 

SAP TechEd 2013: Impressions and Recap

 

SAP TechEd period was again a very busy time for the SAP Portal team. This year we sent 9 people to Las Vegas and 7 people to Amsterdam, ready to deliver a full set of educational sessions on the SAP Portal and HANA Cloud Portal product portfolio.

First day of TechEd Las Vegas started with Vishal's Keynote in which the new solution SAP HANA® Cloud Platform, extension package for SuccessFactors was highlighted (section starts at 49:50 in the recording). The demo part showed how HANA Cloud Portal, as part of the HANA Cloud Platform, is used to deliver and manage extensions on top of the platform. For more information on the extension package for SuccessFactors, see section "HANA Cloud Portal" in this blog.

 

The teams in Las Vegas and Amsterdam had a busy schedule: in between customer and partner meetings, the team delivered about 70 sessions and presented demos at different demo pods as well as at the mini code jam area in Las Vegas.

 

Read also the recaps:

Las Vegas (October 22-25):

First Day Recap (Vishal's keynote with two announcements closely related to the portal team), Second Day Recap and Third Day Recap.

Amsterdam (November 5-8):

....and one recap with the poetic title "My Head and My Apps are in the Cloud" by Ifat Shwartz

 

The Las Vegas team having a rest after a long day:

team_teched.png

 

Hands-On Session "Mobile Portal in Action" in Amsterdam with David Kviti:

mobile_portal_in_action_amst.jpg

SAP Portal Product Manager Thomas Hensel giving a networking session in Amsterdam:

networking_thomas_amst.jpg

Cloud Portal News

 

SAP HANA Cloud Platforum, Extension Package for SuccessFactors
SAP and SuccessFactors, an SAP company, announced on October 10 the availability of the SAP HANA® Cloud Platform, extension package for SuccessFactors, making it easier for customers, partners and developers to extend deployments and build entirely new applications. SAP HANA Cloud Portal works in this scenario as the enabler for the extensions. For more information, watch this video:

 

 

The extension package for SuccessFactors makes it quick and easy for companies to adapt and integrate SuccessFactors cloud applications to their existing business processes, thus helping them maintain competitive advantage, engage their workforce and improve their bottom line. Read also this blog by Amir Blich to understand how HANA Cloud Portal is connected in this new solution. 


Cloud Portal Developer Guide
A new version of the Cloud Portal Developer Guide is available.

 

SAP HANA Cloud Portal on Smartphone

Starting from the October release, SAP Hana Cloud Portal supports consuming sites from smartphones (starting from the iPhone). More in this blog by Ben Aflalo.

 

We also produced this new movie on SAP HANA Cloud Portal on Smartphone:

 

 

Mobile Portal
The new version of the SAP NetWeaver Portal, mobile edition  (a.k.a "mobile portal") is now available for customers. It provides end users with a superior mobile experience, a mobile application gallery, an enhanced personalization capabilities and integration with the customer's Mobile Device Management systems. All, fully integrated with SAP Fiori applications.

The mobile application gallery enables IT to create a role based "catalog" of mobile apps that users can access, discover and select relevant apps from. It provides a superior user experience and a native-like user interaction pattern. For more information, see in this blog by Aviad Rivlin.
mobile_app_gallery_new.png

 

SAP Portal and HANA Cloud Portal Deployment Options

Over the past years, the portfolio of SAP’s portal products has evolved from the single SAP NetWeaver Portal to include several additional options: (1) The SAP HANA Cloud Portal, (2) a managed Portal based on the HANA Enterprise Cloud, hosted by SAP (HEC) and (3) a virtualized portal based on the SAP Cloud Appliance Library (CAL). Read this new White Paper by Yariv Zur describing the various deployment options for an SAP based Portal and providing a guideline for choosing the right one for a specific business project.

 

New Blog Series "Creating Sites with SAP NW Portal"

We would like to introduce to you a new blogger on SCN from the Portal Product management team: Sibylle Brehm started on SCN a new series of blogs on "Creating Sites with SAP NetWeaver Portal". Sibylle has a lot of experience on the integration of SAP Portal Content and Site Management of OpenText with SAP NetWeaver Portal, on the benefits of using these add-ons to the portal, on configuration and administration. It is her experience that she would like to share with you in her blog series.


Trainings and Webinars

Join the openSAP training Introduction to SAP HANA Cloud Platform. It started already on October 28 and it will take 6 weeks. You can still register for the training. This course will introduce you to the SAP HANA Cloud Platform and show you how to take advantage of the various services it provides. Besides the fundamentals of the platform (e.g. persistency, connectivity, security) this course is also highlighting SAP HANA Cloud Portal for creating attractive user experiences and business-driven web sites – for consumption on desktop and mobile devices. For more information, see this blog by Thomas Hensel.


Announcements

We are very pleased to inform you that SAP Portal Product Manager Aviad Rivlin was announced as a SAP Mentor for 2013. Aviad is working as Product Manager for the SAP Portal product management team. He’s also a driving force behind the new "Mobile Portal" product. Aviad is an expert on UI technologies and mobility. More information on the announcement of this year’s SAP mentors in this blog

 

Blogs from the Portal Community

We recommend reading the following blogs:

Hello,

 

Time goes by and so this is already the third and last recap of my impressions from SAP TechEd after day 1 and day 2.

 

After three intense days I feel like to showfloor became my second home, switching between different rooms for the various networking, lecture and hands-on sessions. Our customers still seem to be very hungry for any insight and information they can get from the portal experts about the portal portfolio's recent enhancements and strategic directions! Some faces I knew already from previous sessions or the interactive discussions on Twitter via #SAPPortal and #SAPTechEd

 

The third day started again very early in the morning with a well-attended Mobile Portal hands-on session that went quite smoothly. More and more customer appreciate our end-to-end web-based offering for mobile portal scenarios for accessing portal services on smartphones or tablets. With SAP Fiori we finally have the mobile-ready suite content in place to be centrally launched from the mobile portal (leveraging new iView templates for SAPUI5 or even native apps). Customers also become more and more familiar with the new approach of exposing lightweight services via SAP Gateway and creating appealing UIs on top using SAP's HTML5 libraries, SAPUI5.

3_MO_Sm.png

 

The session was followed by the impressive hands-on exercises on the new UI theme designer. People stood in lines to get into the room and experience the new tool live and literally in colors. Great to see so many UI and portal designers with bright eyes when trying to customize their SAP UI screens.

3_UITHD_small.png

 

Next highlight was the Cloud Portal in Action hands-on session. More and more customers are interested in learning how to extend their on premise or cloud solutoins with the SAP HANA Cloud Platform and its portal services. In the sessions they experienced the ease-of-use for creating interactive and mobile ready business sites with HANA Cloud Portal. We also showcased the integration scenarios with SAP Lumira and SAP JAM.

 

For further impressions from the Cloud Portal perspective, I highly recommend Ifat Shwartz's blog: My head and my apps are in the cloud

SAP JAM HCP Small.png

Another highlight was the customer session about Mobile Portal / AppStore @ LEGO group. Jan Thomas presented their real-life project experience from using the mobile portal at LEGO to create a central access point to launch and personalize access to mobile applications. The hugh number of participants proved the high interest in such lessons learned and recommendation. Learn more about Lego's Mobile AppStore in Tim Clark's blog.

3_Lego_Small.png

Day 3 also gave us the opportunity for networking and discussions with portal customer and partners in order to share latest news from the Labs and gather feedback on our portfolio roadmap. I really enjoyed the time in Amsterdam. Now it time to travel home and get back to work for next year's TechEd highlights....

 

ByeBye Amsterdam! Looking forward to CU all at the next SAP TechEd convention!

Thomas

Hello,

 

As an update to yesterday’s blog impressions from SAP TechEd Amsterdam Day 1 , I’d like to share additional feedback from today.

 

Our second day at SAP TechEd Amsterdam started as the first day ended – with engaged and interested customers asking even more technical questions on the various products of our portfolio.

 

The day began very early in the morning with well attended hands-on sessions for HANA Cloud Portal and Mobile Portal – all laptops taken! The new topics made people wake up early and only enjoy a quick breakfast in order to get their hands on our demo systems

MobilePortal_Small.png

 

After the lecture presentations of the first day, we recognized an increasing number of open discussions with customer and partners in our networking and Q&A sessions going beyond the pure informational purpose and into concrete customer business scenarios and how SAP Portal Portfolio may help them.

 

Main focus in Portal 7.4 discussion was again around the recent mobile portal capabilities (AppGallery, Mobile UWL, SAP Fiori Integration), the new UI theme designer for  and the enhanced content management capabilities together with OpenText

 

Customer especially engaged in discussions around Cloud Portal showcases and integration scenarios with on prem / cloud during the lectures about Cloud Portal overview and deep dive and an intense 4hours end-to-end developer session on HANA Cloud Platform. Watch our videos to learn more. You can also follow some of the discussions online via twitter: #hanacloudportal

CP_L-Ohad-small.png

 

The hands-on session on HANA native development including UI integration services was packed with various people waiting just to get a seat to do exercises.

UIS SMall.png

 

So all in all another busy day with interesting customer discussions and lots of opportunities to showcase our latest enhancements.

Now it's time to rock the convention center with The Fray in Concert....

 

Stay tuned for further feedback!

Thomas

Hi,

 

As a follow up to my initial blog about Portal Innovations at SAP TechEd 2013 in Amsterdam, I’d like to share some early feedback and insights from our first day.

 

First impressions from the Amsterdam include very smart taxi drivers and event staff, typical November weather with wind & rain and the famous Holland bikes all over the place

    

Our day started with an exciting keynote and demos highlighting the “HANA Platform” and its impact on overall SAP technology stack (incl development environments), the SAP applications on premise (SAP Fiori Launchpad) / on the cloud (Cloud Extensions) and the endless opportunities for our partner ecosystem.

 

We had various interesting sessions starting with the big picture in the “Portal Portfolio Roadmap” to dedicated focus areas such as “Cloud Portal Overview”, “Portal 7.4 Overview” and the “Portal 7.4 Hands-On” sessions. All these session were pretty well attended with people queuing up in front of the doors to get some of the rare seats.

 

 

My main key takeaways:

  • Impressive quote of 9 out of 10 customer in the portal lecture (POP205) mentioned that are already running Portal 7.3
  • Mobile portal scenarios received hugh interest in the community – especially with the latest enhancements of Fiori integation, mobile App Gallery and personalizable launcher
  • Cloud Portal scenarios gaining momentum pushed by the keynote messages that highlighted HANA Cloud Platform for extension scenarios. Check out our tutorials and trials for details
  • Portal Deployment Options (classic on premise, via HANA Enterprise cloud and HANA Cloud Platform) brought up interesting discussions how the future model might look like - e.g. hybrid landscapes where Portal 7.4 is used as internal user experience platform (Intranet) and Cloud Portal for customer-facing extensions scenarios (Extranet). Details

 

Impressions from the Portal 7.4 hands-on, Roadmap Q&A session and Cloud Portal lecture:

EP_Small.pngNetworking_small.png

CP_small.png

After a busy convention we concluded the day with a nice team dinner and delicious Ravioli & fish in a small Italian restaurant.

We are looking forward to day 2 and further interesting sessions.

 

Please feel free to follow our live reporting via Twitter using #SAPPortal and #SAPTechEd.

 

Cheers,

Thomas

SAPUI5 is HTML5 with additional SAP features - MVC architecture in development, number of libraries. SAPUI5 is based on principle - Build and run on any device. With mobility becoming important requirement for enterprise applications, SAPUI5 gains weightage in new developments across organizations.

 

We have been developing custom applications or customizing SAP standard objects which majorly make use of BAPI, Z function modules, UI is created either using wizard or using tag library code(JSP Dynpage). How and in what all areas does SAPUI5 development differs from these UI technologies? I have tried to collate major points in this context.

 

SAPUI5 is lighter UI technology compared to Web Dynpro. Major difference in development is in the way interaction is done with backend system. In case of Web Dynpro for Java model is created out of BAPI, Z function module or Web Service and interaction is done with backend. In case of Web Dynpro ABAP, interaction happens by directly calling BAPI or Z function module, tables can be directly queried.

 

When it comes SAPUI5, it supports ODATA compliant services for interacting with backend system. It means if we need to transact huge data with backend system, then performance will be at risk. UI Development using SAPUI5 has wizard based UI creation option also. When it comes to usage, SAPUI5 can be run on any device, but not the case with Web Dynpro. SAPUI5 has UI elements specific to mobile platforms.

 

SAPUI5 look and feel is much better compared to Web Dynpro, JSP Dynpage. We can reuse all the developments of Web Dynpro i.e. business logic packaged in function modules. For this we need to wrap them in ODATA compliant services.

 

There are many scenarios for which we need to explore when it comes to development of SAPUI5 applications. Some of them are: Consider a scenario where we need Adobe  print option in SAPUI5 application; consider a scenario where the workflow is involved; consider a scenario in which status has to be saved.

Summary:

Passing Inspection Lot No from Portal to the QE51N Tcode.

 

Symptom:

As soon as access to the QE51N transaction will load the Material Tab. As we are trying to pass Variable (Inspection Lot) from portal which is available in another tab Portal can not find the required value to push to the QE51N.

 

Reason and Prerequisites:

 

From portal we can pass the variables which are available after immediate load of the transaction. In this perspective we can manipulate the QE51N transaction from portal control.

 

To achieve this we need to perform below steps. For the same required to create screen variant for QE51N Tcode to load Inspection Lot Tab as default.

Need full access toe QE51N transition to create a screen variant.

 

Solution: Steps to Implement the solution:

 

Standard Screen of QE51N in ECC

 

11-5-2013 2-56-23 PM.jpg

Calling QE51N web gui transaction before we implement these steps. As portal could not find the inspection Lot filed this transaction will not execute hence will give blanks screen even if we pass value from portal.

 

In our case we are passing value from Portal POWL application. Same case application if pass values from any portal applications.

 

11-5-2013 2-57-26 PM.jpg

 

When calling standard QE51n from Portal the Inspection Lot Number tab should be appear by default.

 

11-5-2013 2-58-41 PM.jpg

Now navigate to QE51N and click on Inspection Lot Number Tab --> Save

 

To avoid standard variant(SAP&TCODE_QE51N) modify the Variant as below.

 

Enter Variant Name, Description and Unchecked all screen assignments except Inspection Lot screen Number. Here Inspection Lot Screen no is 0510.

 

Now here important point to be noted, The name of the variant should be always starts with "SAP_" or "SAP&". Id we user SAP/User Variant we can not transport this Variant to another landscapes. We should implement this variant manually in each layers as part of Cut over activity.

 

If we want to transport these variant we need to maintain the variant name starts with "Cust_" or "Cust&" only. As we all know to manage name with out Z/Y we should need SAP Access Key.

 

If we create variant with user variant like with "U_" this should in user perspective.

 

These all variant naming conditions logic has maintained in the Program "SAPLQEES" which we can see it from Inspection lot Number tab (F1 --> Technical Name). To navigate to this logic: SE38 - SAPLQEES - INCLUDE lqeesf01 - PERFORM VARIANT_START_F10.

 

Code Snippet as below:

 

IF sy-slset IS INITIAL AND sy-calld IS INITIAL AND
sy
-tcode <> 'SE38' AND sy-tcode <> 'SA38'.
*
h_repid
= sy-repid.
CLEAR h_variant.
h_variant
= 'U_'.
WRITE sy-uname TO h_variant+2.
*   User Variant U_<username>
CALL FUNCTION 'RS_VARIANT_EXISTS'
EXPORTING
report  = h_repid
variant
= h_variant
IMPORTING
r_c    
= h_subrc.
IF h_subrc <> 0.
CLEAR h_variant.
h_variant
= 'CUS&TCODE_'.
WRITE sy-tcode TO h_variant+10.
*     Customer variant CUS&TCODE_<sy-tcode>
CALL FUNCTION 'RS_VARIANT_EXISTS'
EXPORTING
report  = h_repid
variant
= h_variant
IMPORTING
r_c    
= h_subrc.
ENDIF.
IF h_subrc <> 0.
CLEAR h_variant.
h_variant
= 'CUS&'.
WRITE sy-tcode TO h_variant+5.
*     Customer variant CUS&<sy-tcode>
CALL FUNCTION 'RS_VARIANT_EXISTS'
EXPORTING
report  = h_repid
variant
= h_variant
IMPORTING
r_c    
= h_subrc.
ENDIF.
IF h_subrc <> 0.
CLEAR h_variant.
h_variant
= 'SAP_TCODE_'.
WRITE sy-tcode TO h_variant+10.
*       SAP variant SAP_TCODE_<sy-tcode>
CALL FUNCTION 'RS_VARIANT_EXISTS'
EXPORTING
report  = h_repid
variant
= h_variant
IMPORTING
r_c    
= h_subrc.
ENDIF.
IF h_subrc <> 0.
CLEAR h_variant.
h_variant
= 'SAP&TCODE_'.
WRITE sy-tcode TO h_variant+10.
*       SAP variant SAP&TCODE_<sy-tcode>
CALL FUNCTION 'RS_VARIANT_EXISTS'
EXPORTING
report  = h_repid
variant
= h_variant
IMPORTING
r_c    
= h_subrc.
ENDIF.

 

11-5-2013 2-58-55 PM.jpg


Here I have given Variant Name as SAP_TCODE_QE51 (Variant Name should starts with SAP_).  Uncheck all screens except 0510 under Screen Assignments.

And Save.

11-5-2013 2-59-17 PM.jpg

 

Restart GUI

 

11-5-2013 2-59-30 PM.jpg

Test QE51N Again now always this transaction will loads Inspection Lot Number tab by default. Should be looks as below

11-5-2013 2-59-57 PM.jpg

 

Testing from Portal – Login Portal - Navigate to Application where you want to pass this inspection Lot no.

 

Should be able to launch executed QE51n web gui transaction which is relevant to the selected value from portal screen.

 

11-5-2013 3-01-22 PM.jpg

 

HAPPY SHARING!

Venky

This is very simple to do. When I needed to do this, I searched scn and found some solutions but all where in terms of Javascript and other things..

I started thinking about the simple solution with my basic HTML knowledge. I am happy that I found a very simple way to do this and would like to share.

 

Step1) If you are new to logon page customisation, you can refer the below given link which explains the steps nicely:

 

http://scn.sap.com/docs/DOC-27909

 

Now you know how to customise logon page and run the project on server from step1. So, the next task is to put a background image for logon page.

 

Step2) put the image that you want as background in the layout folder. In my case the image name is bg3.jpg. better in the resolution is good (around 1350X600)

 

Step3) You need to change the logonPage.jsp for this, below is simple html (shown in bold) that I added to logonPage.jsp:

 

<%@ include file="/mobile/logonPageMobile.jsp" %>

<% } %>

<% if (!otherUiLoaded) {%>

<html><body

    background = "<%=webpath%>layout/bg3.jpg" style=padding:5px;width:1350px;height:500px;border:1px;background-repeat:no-repeat;>

   </body> </html>

<table id="tblFrmUI" width="150px" valign="middle" dir="ltr" align="<%=uiFrameAllign%>" cellPadding="0" cellSpacing="0" style="background-color:#FFFFFF; <%=uiFrameTopMargin%>">

  <% if(uiFrameVisible){ %>

 

Step4) Save and run the project as you did in step1.

 

This would set the image bg3.jpg as background image in logon page.

 

 

bg_logon_screen.png

Actions

Filter Blog

By author:
By date:
By tag: