I generated my Service over Transaction "SEGW" and everything is fine, but after I generated the services (MPC and DPC) no "Service maintenance" occurs like in all tutorials i've done.
Is there a way to generate an entry in the maintenance folder?
You don't see any entry in the Service Maintenance folder because you are missing some system alias settings that are used by the service generator. Anyhow, you can also register your service via transaction /IWFND/MAINT_SERVICE.
For more details about the missing settings, take a look at the following topic on SCN.
Cheers,
SePo
If the deployment system is absent in Service Maintenance you can add it manually that way.
In SPRO:
SAP NetWeaver -> Gateway Service Enablement -> Backend OData Channel -> Connection Settings to SAP NetWeaver Gateway -> SAP NetWeaver Gateway Settings
Create the new entry and put RFC connection of local system from SM59 there.
Related
In Development Server, I had ran Task "SAP_FIORI_LAUNCHPAD_INIT_SETUP" through stc01 transaction which created the below Odata Services with respective SICF services.
o ZINTEROP
o ZPAGE_BUILDER_PERS
o ZPAGE_BUILDER_CONF
o ZPAGE_BUILDER_CUST
o ZTRANSPORT
But since I wanted to get all the above ODATA Services and it's respective SICF services in TR to get it released for Quality.Therefore, I deleted all the above odata services and added manually through /IWFND/MAINT_SERVICE transaction.
But the SICF Services is not captured in the TR, hence after releasing to Quality,I can only see the ODATA Services and it's ICF node is showing Initial .PFB the TR screenshot.
Please Guide.
Regards,
Sayed
In development system, did you create your services as part of a development package or as temporary local objects?
Please see the prerequisites in: Transporting ICF Services
You should be able to add your services to a transport request, using transaction SICF: “Right-click on your service -> Object Directory Entry”
as mentioned here in the following:
Missing entry in SICF services after webservice transporting,
How to get a SICF Node for a imported BSP?,
How to transport web dynpro application, and
Help, SICF Service is not transported
1)
Your ICF node “ODATA” shown in your screenshot is active?
2)
When you saved your service in the transport request, it should be included as R3TR SICF YourServiceName.
When you transported this transport request to your Quality system, there should be a log of the import. You should see that your service was imported with returncode=0.
When I start transaction SICF, I get the following screen:
When I click “Execute (F8)”, I get the following screen:
Here I can search for services, e.g. by expanding “default_host”.
How does this look in your system ?
In hana cloud platform , there is a "New project from sample application" (I think it is recently added ? ), I created a "Approve Purchase Orders", but when I run it, there is a 500 error:
Produced by
"requestUri": "/sap/opu/odata/sap/SEPMRA_PO_APV/$metadata"
How to config RefAppsBackend data source in destionation?
When I new project from template, there is a place to config data connection , but why the sample application didn't provide it ?
When you create from sample application, it copies the data connection configuration of that app. Hence it doesn't provide the choice to config.
If you have already configured a backend system for your WebIDE -> Replace RefAppsBackend in file neo-app.json with your backend system
If you don’t have a backend system configured for your WebIDE: Start the SAP HANA Cloud Platform.
Then open the WebIDE and choose Tools -> SAP HANA Cloud Platform Cockpit.
In this Cockpit select ‘Destinations’ on the left side and then ‘New Destination’
I am developing a service layer app which provides a catalog of webservices, then I am orchestrating them using OpenESB.
I create my BPELs importing external WSDL definitions using http://localhost:8080/services/myService?wsdl.
The problem is -- these BPELs strongly depend on this specific URL, and when I deploy on production server, my ESB layer stops working.
How can I make my BPELs independent of the specific endpoint? Can I refer the URIs to an external config file?
To do it you must create application configuration and application variable and add them on your http address. Example: "http://${MyHtttpAddress}:${MyHttpPort}/service1/myService?wsdl"/>.
Applications and variable are set up in the administrative console and can be changed for each environment.
Regards
Paul
I have service (Web Service Proxy) running on DataPower. I am able to test the service from SOAPUI.
Client application / service is trying pull WSDL from URL like http://host:port/uri?WSDL
It is mandatory to pull the WSDL from URL to develop their code.
I have upload the WSDL and share the
http://host:port/system/dpViewer/ServiceName.wsdl?filename=local:/Path/ServiceName.wsdl
Still They were not able to access the URL from their system.
We performed the connectivity to both system. Everything is working fine.
Any help?
You can't access using
http://host:port/system/dpViewer/ServiceName.wsdl?filename=local:/Path/ServiceName.wsd
As it is internal for your reference and It will open your file in Management / Admin IP. (Most of the place there will be different IP for transactions)
http://host:port/uri?WSDL is possible in DataPower
Please follow the below step in your Web Service Proxy (WSP)
Edit front side handler (HTTP SOURCE HANDLER)
Enable 'GET method'
Apply changes and Save Config.
By Default , 'Get method' will not be enabled in WSProxy. As it is disabled, All WSDL get requests are rejected by DataPower.
I hope after this , We can access the WSDL using URL.
I am trying to implement My Leave Request App. I have I have implemented all the SAP Notes and Add-on Components mentioned in
http://help.sap.com/saphelp_fiori/fiori10_install_en.pdf
But when I try to execute the service ZLEAVEREQUEST in the Gateway Client I am getting the following error
Model 'ZLEAVEREQUEST_0002_BE' contains errors. Contact Adminstrator
Please help me fix it!
Log on to the Front End System
Transaction: SPRO
Click on SAP Reference IMG
Browse to: SAP Netweaver -> Gateway -> OData Channel -> Configuration -> Connection Settings
-> SAP Netweaver Gateway to SAP System -> Manage SAP System Aliases
Select the SAP System Alias name and uncheck Local GW and For Local App both the check boxes.
This will resolve the error.
Make sure all the correction notes are applied . You can check the SAP Service Market place to find the available support packages. Also make sure all the relevant Business Catalog Roles are assigned to the user.