I have following problem:
I created an app and the according oData in frontend system. Everything worked fine. Then I was taught, that this was not correct and I have to create the oData in backend system.
So I made this. I created just the same oData in backend system, created another service for the new oData in transaction /iwfnd/maint_service in frontend system, changed the data source in the manifest of my app, and everything seemed to work fine. To add the app to the launchpad I needed one (or two?) more services in transaction SICF (paths sap/bc/bsp/sap and sap/bc/ui5_ui5/sap). Those were generated automatically for my "frontend-oData". As those weren't generated automatically in frontend system for my new "backend-oData", I added them manually. This seemed to work as well. So I transported everything into quality system (the app from WebIDE to SAP was transported as "updating an already existing application").
And now my problem:
Yesterday after transporting my app ran perfectly in just updated version. Today I get an error in quality system, that says:
"No systemalias for service 'ZEXAMPLE_SRV_0001' and user 'USER1234' found" (I translated this error message from german). This error is new to me and I did not have this before. The settings for my "frontend-oData" were different ones (no systemalias & service processing mode = "Co-deployed only") and they were generated automatically.
Now for my "backend-oData" in development system there is the setting "Routing-based" and the correct systemalias is maintained and the app runs perfectly there. But in quality system there is no systemalias maintained. So I transported the systemalias from development system to quality system, but that didn't work, because the systemalias has to be a different one in quality system.
I tried to make exact the same settings in quality system for my "backend-oData" as the "frontend-oData" has, but then in /IWFND/ERROR_LOG I get the message "No service for namenspace /SAP/, Name ZEXAMPLE_SRV, Version 0001 found."
So can anyone tell me the secret which step I need to do, that everything runs correctly again? I am desperated by now.
Many thanks and best regards
In your dev system open transaction /IWFND/MAINT_SERVICE and select the service in the service catalogue.
You should see the system aliases in the bottom right:
Press on Customizing and in the following view switch to edit mode:
As soon as you are in edit mode, you can select Table view > Transport. It will ask you to select an existing transport or to create a new one.
Two buttons will appear in the customizing view. Add to transport and Remove from transport.
Select the system alias row from the table and press Add to transport.
Now press save!!! Otherwise the alias will not be part of the transport. It's only "put on hold" when you press "Add to transport". Press save!!!
Move the transport to your next system (and eventually into production) if you want to use your OData service in other systems.
Related
I built a dashboard in Qlik Sense and after I published it I noticed the following error -
"Invalid sort order in properties".
When I duplicate the dashboard in order to edit it, the error drops and the data is shown correctly.
What could be the issue?
Had similar issue some time back. In my case the object was an extension and it was trying to modify (apply some patches) to the underlying object. As in your case it was working fine if the app is not published. The reason was that once the app is published you don't have the permission to modify objects that are published.
Modify objects on published apps is forbidden by default. It can be overwritten by changing one of the default security rules but personally I will not advise you to change the security rule because it will be applied to all published apps (unless you change the security rule to target only set of apps)
I am starting from the position of near absolute ignorance here.
I successfully set up a Bluemix account, added devices, got API keys, connected my Raspberry Pi running Node Red and a temperature sensor to Node Red on Bluemix, created a dashboard and was able to get data back and forth between Watson/Bluemix and my Pi. Cool. Unfortunately, I got all that way without ever really understanding the navigation of Watson/Bluemix nor all the terminology. I made NR work both ways and was happy.
Then one day last week, the route to my Bluemix Node Red application stopped being accessible:
404 Not Found: Requested route ('misterpi-01.mybluemix.net') does not exist.
I can browse my devices and see that they are sending data every few minutes, so clearly the connection is there. When I click on IBM Cloud Apps, I am told
There are no IBM Cloud applications bound to your organization
When I am on my IBM Cloud Dashboard and I click on Connections I see I have a connected application that is "Not Running" with a red dot. I can click Stop and the status goes to Stopped. When I click Start, after a short while,
I cannot add an another app because I can only have one.
Where did my NR app go and can I get it back (preferred) and if not, delete it?
At the suggestion of #hardillb I went looking for logs. I found them and it looks like the app is continuously started and crashing. I can't copy the text from the error logs but here is a screenshot.
The first thing you should do is get a copy of your flow source for backup. Go into the IBM Cloud Dashboard and click on Cloudant-ll (the suffix may be different?) and then Launch Cloudant Dashboard (alternatively, click on ...-cloudantNoSQLDB and then alias of Cloudant-ll). From there click on NodeRed and then select the id that ends with "/flow". Then you can extract everything inside "flow": [].
I would recommend emptying it out so you have no flows to ensure that Bluemix can start 'empty'. If you do this you will end up with something similar to mine below (don't change _rev).
{
"_id": "Home Assistant/flow",
"_rev": "102-2b38e1756eeb26def19b20858bc50a40",
"flow": []
}
Later you can paste the extracted code back into Node Red using Import > Clipboard.
You may also want to edit the ".../settings" document to remove any extra node types you installed.
Caveat - I had the same problems with Bluemix and eventually gave up - crashing at least weekly running out of memory and difficulty restarting. I suspect it can't reliably run with 256MB.
I had similar issues with log/errors and endpoint 404:
I followed Michaels advice to backup (nodered:flows and settings) in cloudant.
1. However what works(for now) was cleaning part of the nodered /settings.
2. Basically I removed the nodes part from the Json up until almost the end, leave _credentialSecret part at the end.
3. restart and go to your url, you will see your flows
4. if your flows use some nodes that produce warnings, it might be necessary to remove them to avoid future problems.
UPDATE 2: I saved every flow separately, and then deleted them all from the nodered flows. Then restarted, and have been importing one by one, and it is working.
I have a really bizarre one here...I have developed and deployed to my back end system a launchpad application that currently works OK. Part of this application is a report that, based on certain filters, returns a table and a chart (see snapshot below).
After finishing deployment next step is configuring the app so it runs from the launchpad within the SAP portal. Not familiar with the portal, another colleague undertook the task, application is now running from within the portal as well. With one exception - the chart above is not visible (see 2nd snapshot below).
Noticing the "No Data" message and NO exception in the Chrome debugger, thought as a good idea to debug the OData methods in the back end. To my big surprise, found out that while filters pass to the method just fine both for table and chart (two different entities but almost identical and accepting exactly the same parameters) when running outside portal, when running from within (the portal) parameters "get lost" on their way to the chart entity - no parameters for the chart method. See snapshots below and pay attention to the IT_FILTER_SELECT_OPTIONS at the bottom right.
Outside portal (parameter table filled)
Within Portal (parameter table empty)
Furthermore, the filter table passed to both OData tables is common, you can see the code underneath - just two lines: one for table and one for chart binding.
Closing with a clarification. Mentioned above that there are no errors in the debugger when calling the back end methods. There are actually a couple of them but they take place during the initialization of the app and do not seem to affect anything else in the app, which aside a set of reports has a lot of data operations (dialogs, tables etc), everything else works fine. These errors can be seen below.
Does this situation ring any bells to anyone?
Thanks in advance
Issue solved, it was a deployment issue...
I have extended Manage journal Entries app in Web Ide. Haven't added any extra code. Just saved it and run to check whether the app is opening as expected or not. But I am facing error " Could not open app, Please try again later".
Come across few threads regarding similar issue but my issue is not while launching, It is when extending manage journal entries app.
Fiori : Could not open App
Pre Requisite which I have checked:
SICF Service is Active.
component UIS4HOP1 200 SP 0000 is installed in my FrontEnd Server.
Thanks,
Srilaxmi
From the error message in the commments section it seems like you have problems with the namespace of the component. Did you check that the path and the namespace for your extension project matches the deployed app? This can very easily mess up the component loading mechanism in FLP and lead to the described result...
I am using the web interface, I am trying to make public files that were uploaded and each time I click the checkbox I immediately get the error "Invalid Argument" and the box unchecks.
This also happens while trying to uncheck files already uploaded and public.
I'm not certain if something happened to my account or if this is a service problem for the site but we're in a major jame because of this. Essentially Cloud storage is unusable at this stage.
There was an issue with the web user interface and the JSON interface affecting setting ACLs on objects. That problem has been resolved, and all interfaces should be working correctly now.