Developing a Full-Stack JavaScript web app with Caché requires you to bring together the right building blocks. Previously, I outlined the basic steps to install and connect Node.js to Caché and make it's powerful multi-model database capabilites available for use with Node.js. You can use Caché as a NoSQL-, document- (with unique key-level access!), SQL- and object-database with Node.js. When developing JavaScript applications, you'll see how powerful this combination is and makes Caché a perfect fit for Node.js.

In the first part of this article series I will show how to get started with the React framework, one of the most popular frameworks currently taking over front-end development. In the next parts you'll learn how to connect a basic web app to a Caché back-end.

You'll see, it's very easy to get started with this technology - you can even compare the amount of basic knowledge you need to COS because you only need to know a few basic concepts to start!

Last comment 8 August 2017
+ 8   1 14
3367

views

+ 8

rating

So, one day you're working away at WidgetsDirect, the leading supplier of widget and widget accessories, when your boss asks you to develop the new customer facing portal to allow the client base to access the next generation of Widgets..... and he wants you to use Angular 1.x to read into the department's Caché server.   

There's only one problem:  You've never used Angular, and don't know how to make it talk to Caché.

This guide is going to walk through the process of setting up a full Angular stack which communicates with a Caché backend using JSON over REST.  

Last comment 25 April 2019
+ 14   1 7
2624

views

+ 14

rating

When creating a filter located on a dashboard that targets all, is there a way to narrow that filter down?

For example, in our data we have some dates that are well out of range due to data quality issues, but they still appear in the drop downs. Is there a way to say, only make available the below dates in the filter?

Another example, If we want to only look at Emergency data, it still provides all the wards for inpatient activity and activity in other hospitals, meaning, to get to just the Emergency wards you have to scroll through everything?

Hope that makes sense.

Last answer 23 November 2016 Last comment 23 November 2016
0   0 4
197

views

0

rating

The DeepSee TroubleShooting Guide helps you track down and fix problems occurring in your DeepSee project. A common problem is finding less records than expected in a DeepSee Cube or a related Subject Area. The DeepSee TroubleShooting Guide suggests starting your investigation by checking the following:

Check cube for build restrictions

Check if maxFacts is used

Check if Build Errors are occurring

+ 2   0 2
0

comments

227

views

+ 2

rating

This post provides further detail on the suggestions from the DeepSee Troubleshooting Guide about what to do if a user is not able to view a listing in a DeepSee cube, but instead sees errors like this:

ERROR #5540: SQLCODE: -99 Message: User <username> is not privileged for the operation [zfindStatement+118^%SQL.DynamicStatement.1:<namespace>] (8)

+ 1   0 2
0

comments

286

views

+ 1

rating

I tried using the DeepSee Troubleshooting guide but the suggestions weren't working.  Let's say that the source data we are using to build the cube on has a value out of range. This would cause the cube build/update to fail. How do I see the error log that explains which field has the value out of range? Please be detailed on exactly what command I should enter and where I should enter it in.

Last answer 7 November 2016 Last comment 10 November 2016
0   0 4
280

views

0

rating

Whether you are accessing DeepSee for the first time ever or you are configuring DeepSee on a new instance, there are two common issues that are encountered after clicking on the “DeepSee” option in the System Management Portal.

Issue #1: Architect/Analyzer is grayed out!

Issue #2: DeepSee must be enabled before use.

Issue #1: Architect/Analyzer is grayed out!

Last comment 7 November 2016
+ 5   0 5
839

views

+ 5

rating

The goal of this “DeepSee Troubleshooting Guide” is to help you track down and fix problems in your DeepSee project.

If the problem can’t be fixed by following the guidelines, you will at least have enough information to submit a WRC issue with DeepSee Support and provide all the evidence to us, so we can continue the investigation together and resolve it faster!

Last comment 29 November 2018
+ 11   0 15
1210

views

+ 11

rating