I'd like to create a sap fiori launchpad from scratch. What the should I do? For example, now I just have a develop system. I need a fiori launchpad. How to create it?
thank you.
In Addition to SAP Fiori Crew's answer, make sure:
Fiori Application is hosted
oData Service hosted in the sap system same as UI Code with the RFC connection to the oData backend.
Use the above to create a tile and catalog.
Related
i want to open SOLMAN_WORKCENTER Tcode in mobile device.
what should i prefer web browser or FIORI client application?
Please suggest the prerequisite for this and possible solution?
The official SAP docu might be helpful:
Starting the Work Center
You can start all work centers for which you are authorized, as follows:
1) In the SAP GUI for Windows using transaction SOLMAN_WORKCENTER
2) In a Web browser using the Web Dynpro application AGS_WORKCENTER
Note
By default, the URL for calling up the Web Dynpro application (in the SAP namespace) has the following syntax:
http://< host >:< port >/sap/bc/webdynpro/sap/ags_workcenter?sap-language=< e.g.: EN>.
Do not use the Back button for navigating in your Web browser.
You can also start an individual work center directly using the corresponding Web Dynpro application. To call up the URL, for example, for Incident Management (in the SAP namespace), use the following syntax:
http://< host >:< port >/sap/bc/webdynpro/sap/ags_work_incident_man?sap-language=< e.g.: EN>
3) In SAP NetWeaver Business Client (NWBC)
Here you have the same navigation options as in the Web browser but the system arranges the UI elements differently: In NWBC, the navigation bar is vertical and the navigation area is horizontal. For more information, see SAP Library for SAP NetWeaver Business Client on SAP Help Portal at http://help.sap.com/netweaver -> SAP NetWeaver Platform -> -> Application Help -> Function-Oriented View -> UI Technologies in SAP NetWeaver -> User Interface Clients .
Assumptions:
Multiple SAPUI5 apps are build
they should be deliverable (via SAP transport system, potentially over transport files) into different clients
technical steps to create roles and launchpads are known
a SAP namespace is registered and available
Question:
Is there any guide to design the launchpads/roles for these apps especially to make it deliverable to different customers?
There are guidelines in the FLP documentation.
This documentation describes how to create your own Fiori Launchpad content, such as catalogs, groups, and so on. Delivery however differs depending on whether its ABAP on premise, HCP, the delivery channel, and so on.
I need to make an iOS application that can consume a web service on Microsoft Dynamics NAV system. The web service is given in WSDL. I tried to access the service by sending SOAP request but without success. Is there a different approach to consume a WSDL web service on a NAV system ? I am really stuck in here. I would really appreciate some help. Thank you in advance !
My suggestion in this situation is always to create a C# Web Service that will act as a bridge between NAV and your iOS application.
The Web Service use .NET so can easily pull the data from NAV, and because is a Web Service you can consume it by any platform (with SOAP or REST is your decision)
I'm planning to develop a SharePoint 2010 native iOS solution with some basic features like login and fetch content. Are there any RESTFul web services exposed by SharePoint to work on, which lists the RESTFul web services that we can use?
Is there any initial steps that I need to follow to start up, provided the RESTFul web services are available?
Thanks
Sudheer
I have already checked the information related to WSO2 ESB SAP Adapter from this link:
http://wso2.org/premium/summer-school-2011-session4-enterprise-integration-with-sap-and-wso2-esb
Is this the only information i can found about it?
I didn't find anything related to it in the official documentation of WSO2 ESB...
An example showing how to configure this adapter in the ESB will be very helpfull!
Thanks in advance,
Santiago.
You can refer following documentation for more info about WSO2 ESB integration with SAP.
http://docs.wso2.org/wiki/display/ESB460/Enterprise+Integration+with+SAP+and+WSO2+ESB
This documentation was added recently and I hope you will be able to find the information you are looking for.
WSO2 ESB comes with a variety of adapters to connect to all sorts of different systems. One of these adapters is the SAP adapter.
The WSO2 SAP adapter has full iDOC and experimental BAPI support. It used the SAP JCO library as underlying framework to communicate with SAP.
Installing the adapter couldn’t be easier. Its shipped with WSO2 ESB and the WSO2 ESB documentation website describes the installation procedure from the WSO2 perspective.
The installation procedure however does not guide you on how to find the settings you need in SAP.
That’s where this blogpost steps in. It is actually the first in a series of three. I’ll first take you through setting up the SAP connection. Then the next blogpost will introduce sending iDOCs and the last post will take you through invoking BAPIs at SAP.
So, let’s start off with some SAP adapter knowledge. I’ll refer to the WSO2 ESB SAP adapter as ‘SA’ in the following guide.
The SA is capable to be used as a Client as well as a Server. To setup the SA as client to a SAP system you’ll need to setup a client-side configuration fle. This file should be named [SAP-GWHOST].dest and must be placed in the [WSO2_HOME]/repository/conf/sap folder. This folder does not exist per default so make sure you create it and provide enough access rights for the WSO2 user to read the files within it.
To setup the WSO2 as an idoc server you must create a configuration file named [SAP-GWHOST].server.
Let’s first handle the client configuration file. There might be some differences based on your SAP system but the following settings should cover a lot of installations. The screenshots are based on SAP ECC version 6.0
In the examples here the SAP gateway is known as SAPSYS01.