Versions Compared

Old Version 5

changes.mady.by.user Kaylee Law

Saved on

compared with

New Version 6

changes.mady.by.user Kaylee Law

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Modified the sub titles.

...

Section

How to correct this error and create a valid connection.

The actual solution you will want to implement will depend upon how you want to configure your server, but here are some solutions you can implement so that the Profound.js instance has a valid connection to an IBM i.

Section

Solution 1: Create connector credentials.

For applications that will not prompt the user to log in, like for web-services, a set of default credentials can be specified in the Profound.js server's configuration file, and a valid session will attempt to be created from these stored credentials. To specify these credentials you must first use the the store_credentials command line utility to create the encrypted credential file. Then you can use the connectorCredentials configuration setting to specify the location of the encrypted credential file.

Note
titleNote for Instances of Profound.js installed on a non IBM i platform.

You can use another configuration setting to specify the URL to an instance of Profound.js that is installed on an IBM i platform. You can find a tutorial for setting up this connection here.

Section

Solution 2: Pass 'authenticate' token from another valid session.

When calling Profound.js applications from another application that is already connected to a valid session, you can use the authentication token from the calling application to create a valid connection for your new application. When calling the Profound.js application from Genie or a Rich Display File application, this 'authenticate' token is automatically included in the call to the Profound.js application. Here is an example of how to add this authentication token when calling a web service.