On SAP Web IDE Multi-Cloud version, when right clicking and going to Run > Run as > Web Application or SAP Fiori Launchpad Sandbox it gets to the SAML authentication and that stops on a white screen, with no errors in the console log.
I've tried this on custom apps I've created and also a new SAPUI5 app from template, nothing works. It only works if I deploy it to the SAP Cloud Platform then register it to my personal Fiori Launchpad.
I've tried the exact same in the standard SAP Web IDE version (non- Multi-Cloud version) and it works.
If anyone knows the solution to this, it would be great.
Thanks
Issue resolved. Turns out the destinations 'webide_di' & 'webide_di_s2s' should be created automatically when you enable the SAP Web IDE Multi Cloud Version service, but in my case they were not. Once I added them manually, it started working.
Related
I have a web app (.Net 4.6.2) running on an Azure App Service with Application Insights. I'm using SQL Azure as a back end. When Application Insights logs sql dependencies, the command text isn't included, just the server name and the database name shows up under 'Command'
I've uninstalled and reinstalled the extension and seem to have exhausted online sources. Can anybody suggest where else I look for a solution?
Is this how you install the extension? (Just double checking) And you tried removing/adding back the extension?
Also - does you application refer to SDK in source code already? (via nuget)
I am new to SAP Fiori, I have been assigned to activate SAP Fiori apps on our SAP S/4HANA 1511 FPS02. I have activated all assigned transactional apps, Our launchpad is running fine, but I am unable to activate FPM/WebDynpro applications.
I have followed this Link step by step, but I am unable to get my FPM/WebDynpro Apps.
Can someone guide me how to activate webdynpro Fiori apps.
I have also tested and activated the webdynpro components from SICF, still I am unable to activate the tile.
WEbDynpro app eg: DynproApp
Thanks in advance.
Regards,
Eliza
It seems that the App Specific Technical Catalog is missing.You must be Experiencing Reference Error in Tile(Launchpad Designer) for your App Business Catalog.
Please refer note 2269272 and refer Link.
Regards,
Sayed
I am migrating worklight hybrid projects from 6.0.2 to 6.3. When i do this and install the application on to android device, I am unable to edit worklight settings and change the URL.However the same feature is working on IOS devices.
But when I create new project on 6.3 , the above feature works fine in android as well.
In application-descriptor.xml worklight settings is enabled though.
.
However when I try to change the URL in android device by editing the settings, below exception is thrown.
02-16 18:48:27.173: E/EnterpriseContainerManager(552): ContainerPolicy Service is not yet ready!!!
02-16 18:48:27.173: E/ViewRootImpl(27590): sendUserActionEvent() mView == null
02-16 18:48:50.155: E/Watchdog(552): !#Sync 706
Settings pop up is not showing up , to change the URL. Please suggest.
Worklight Settings is unreliable on Android devices using API Level 10 and above. The settings screen may appear but not work, or the Options Menu that invokes it may not appear at all, etc.
However, starting MobileFirst Platform 6.3 there is dedicated API for setting & getting the Server URL, enabling you to change it during runtime: WL.App.getServerUrl and WL.App.setServerUrl.
There is a blog post on this new ability that explains how to use the API methods as well as provides a sample application. You can follow it and integrate it in your application instead of using the Worklight Settings screen in Android.
Blog post: https://developer.ibm.com/mobilefirstplatform/2015/02/02/changing-server-url-runtime/
I'm studying the new function provide by 6.3 - Offline Authentication by this document,
https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-6-3/authentication-security/offline-authentication/
and I'm getting a Error from the Adapter,
it's said #78 getInfo is an object, not a function,
Any help ?
Many thanks.
Note that this is not "new functionality". The sample project simply implements one possible way to achieve offline authentication.
I have tested the application by following the below scenario and it is working OK, so you really need to actually mention what you're doing, how you're doing it, what is the scenario and what exactly is the error (copy/paste it).
Steps:
Import project to Eclipse
Start the server (servers view > play button)
Deploy adapter
Deploy project and open in Xcode, install on device
Login when online (for example, using A/A as the username/password)
Logout
Move to airplane mode
Try to login again with A/A
The application successfully logged-in in 'offline mode'.
We have already delivered the 1.0 version of our Worklight application. By mistake we have disabled the Direct update feature by updating the attribute "connectOnStartup = false"
We dont want to redeploy the application to markets (AppStore/GooglePlay) again, but wanted to make our users to utilize the direct update feature. We do have the access to WL server.
Our issue is little different from the one which is already discussed here "IBM Worklight - How to disable Direct Update?"
How can we provide the direct update feature to our end users without redeploying the application to AppStore/Googleplay. And just by changing the Webresources of the application.
We are using the adapters in our application but no where we are explicitly calling the "WL.Client.connect".
The Direct Update feature is always enabled by default.
You need to edit your question and explain what it is you've done in your Worklight project.
The feature will not work if:
You have set connectOnStartup:false
You are not using WL.Client.connect
You are not invoking adapters
You disabled it via the checkbox in Worklight Console
Otherwise, the feature will work, and a check for Direct Update will be performed:
On application startup
On return to foreground
The application will need Re-deployment on the App stores.
So the solution to your problem is
Rebuild the Application with connectOnStartup:true.
Redeploy the Application on App Stores
Once the users download the updated application, future updates will go to the users directly.
While rebuilding, make sure that you change the Version of your application within ApplicationDescriptor.