We used this tutorial to start developing Fiori apps with VS Code:
https://blogs.sap.com/2020/07/16/developing-sap-fiori-app-using-sap-fiori-tools-in-visual-studio-code/
Everything works fine so far, except the connection to the backend services. When we want to start the application locally we get the following error by getting the OData metadata.
Our server config in ui5-local.yaml:
Before switching to VS Code we used the local WebIDE which worked fine. So I guess there is no configuration on the SAP system which blocks the request.
Did anyone face the same issue and has a solution for us? I searched online and couldn't find anything that fits our problem.
Thanks a lot for any hints.
try this npm install ui5-middleware-proxy-basicauth --save-dev
Are you by any chance in corporate network which uses Self-Signed Certificate. If so npm might fail. Change the ignoreCertError: true and give it a try.
Related
I am currently in the process of exploring the possible use of VS Code Server on Sagemaker Studio. Of course, if you sign up through Code Server preview, I was able to set and start it up. However, when I tried to serve it locally, I encountered a blank page after modifying the /default/proxy/XXX part of the url like how we access tensorboard.
Just wondering on whether are there any tinkerers out there that managed to get it working? (and yes, I understand that somebody managed to get it running https://coder.com/docs/code-server/latest/CONTRIBUTING. but wondering whether anybody managed to use the native installation to work properly? Any possible steps that i may be missing?
Check out the blog post here for hosting code-server on SageMaker Studio - https://aws.amazon.com/blogs/machine-learning/host-code-server-on-amazon-sagemaker/
And associated git repo here - https://github.com/aws-samples/amazon-sagemaker-codeserver
I'm having difficulty in integrating AEM 5.6.1 with Site Catalyst. It allows me to connect in the configuration successfully, but does not work on the framework setup.
I've followed the standard procedure to connect AEM to SC and it accepts my login in the configuration, but fails on the framework set up with the browser message 'We were not able to login to SiteCatalyst. Please check your credentials and try again.'. Behind the scenes in the server log;
12.12.2014 14:10:06.967 *WARN* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.SitecatalystHttpClientImpl Data center 'https://api3.omniture.com/admin/1.3/rest/' responded with errors {"error":{"code":500,"message":"Internal Server Error"}}
12.12.2014 14:10:06.967 *ERROR* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.servlets.SitecatalystServlet Call to SiteCatalyst method 'Company.GetReportSuites' failed com.day.cq.analytics.sitecatalyst.SitecatalystException: not authenticated
I've tried accessing via the API Explorer and it works.
I've tried the troubleshooting guide without success.
I can log in to Site Catalyst, I'm an admin, I am in the web services access group.
I've tried using a clean install of CQ5.6.1 with geometrixx - it doesn't work either.
I've tried this from a server and from a localhost/dev machine with the same results. No proxy. I've even tried using the shared secret as the password but then it doesn't connect at all, and fails on the configuration screen.
What might cause this to fail?
If it doesn't work with a fresh install and Geometrixx, then it's probably an Adobe bug. That's typically the first thing support will ask you about.
I would also verify using Geometrixx Outdoors, or a more recent demo site, on your fresh install, just to ensure it's not an outdated ClientLib issue.
I know this isn't a direct answer to your question, but honestly, I would approach the integration differently. I've worked with the AEM-SC framework and it's buggy at best. It's very finicky, it doesn't REALLY work the way the documentation claims, and it requires that you're very specific about what Clientlibs are on the page.
Moving forward, I think using Adobe Dynamic Tag Manager is the better approach, for many reasons. My understanding is that it's Adobe's recommendation as well. I'd consider moving to that. In AEM 5.6.1, you'll have to customize your integration with DTM, but it's not very hard.
Solution: Add a property on the configuration node for sitecatalyst: (eg. /etc/cloudservices/sitecatalyst/my-sc-configuration)
server=https://api.omniture.com/admin/1.2/rest/
it also seems to work with newer API versions such as https://api3.omniture.com/admin/1.3/rest/
It would appear that for 5.6.1 it ignores the OSGi configuration, at least for the configuration screens. With this extra property, the framework page loads without error and allows selection of the RSID.
All,
I have a C# ServiceStack console listener application running on Ubuntu using Mono. Within that application I have one service that must authenticate first at Appcelerator Cloud Services (ACS). I have tested the code locally(Xamarin .NET on OSX) and can see the code is fine. Based on the error and investigation using the almighty Google, Mono doesn't trust any secure sites by default.
So far I have tried using mozroots to import all mozilla root certs, and have used certmgr -ssl to import the certs directly from https://api.cloud.appcelerator.com. Nothing has worked so far.
I don't want to put code in place to bypass SSL in order to accomplish this as I think that is a cheap/insecure hack. There has to be a proper way to make this work.
Any and all suggestions appreciated!
Bruce
All,
I had it right. I was just missing the reboot which allowed Ubuntu to load up all the certs in the store.
Victory is mine, sayeth the coder...
I have a completed meteor project and is currently deployed on the meteor website. I would like to move it to my own website, which is currently hosted by GoDaddy.
How do I install Node and Mongo on my server (linux) and then run my meteor project? I received ssh access to my server, so I assume I can do this, but I'm just not sure how.
So how exactly do I proceed?
Additional Info:
I'm not exactly sure what of linux it is. On GoDaddy, it simply says linux.
When I ssh, it shows me:
-bash-3.2$:
Also, I having my website simply show the myapp.meteor.com webpage would work too. An explanation on how to do this would work.
Discover Meteor has a chapter on deployment which helps to answer this question. For ubuntu-based servers they recommend meteor-up. I haven't used it, but it's probably worth checking out. Previous versions of the book recommended meteoric.
I wrote my own set of bash scripts using a few ideas from meteoric, but I already had a lot of experience doing deployment scripting. Frankly there's nothing quite like figuring it all out yourself, but doing sysadmin tasks doesn't appeal to everyone and it can be hard to pick up in a hurry.
So today, whenever I try to sign My Blackberry app using the WebWorks packager, I get this error...
"General failure. Please try again. Server may be unavailable".
My proxy settings have not changed and I have been using the same command line instruction with success before.
I've also checked the status of the Blackberry signing server using the following link...
http://isthesigningserverdown.com/chart/index.php?sigType=RBB or RCR or RRT
And everything appears to be online!
So, where could I be going wrong? Here's the command line instruction I've been using. First, I navigate to my Blackberry build folder and run the following instruction against it...
bbwp appname.zip –g <password> –o z:\projects\appname\signed
It goes through through parsing the various elements. The signing tool pops up and then the error is generated.
So, after a couple of days of banging my head against the wall-the answer finally came to me. I'm on a MAC but am also using a Windows virtual machine for Blackberry developement, which is running on another network altogether and this specific network is using a firewall, which, according to the network administrator, is currently experiencing a severe technical problem.
The way round it was to sign my Blackberry app using configured proxy settings to communicate with the signing server and viola! It worked!