Solved

connecting Mobile application to the Software Factory

  • 17 February 2020
  • 1 reply
  • 92 views

Userlevel 3
Badge +11

 

I have a mobile application in development and I want to connect the mobile gui to the SF so we can see what we are developing. I already have a working connection to our test-IAM, which is located on a different instance .

I am using SF 2018.3, Indicium

To connect to our test-IAM I am using these settings:

Meta source = IAM

URL = https://url/mprod/api/iam

 

Where  mprod is the application in the IIS and the corresponding IAM is located at SERVER/test_instance.

 

I want to connect to our SF which is located at SERVER/dev_instance. This does not work. Now I have the following questions:

 

  1. Do I need to make a separate application in the IIS to connect tot he SF?
  2. I already did so, and I called the application sf, in the appsetting: server = SERVER\\dev_instance ;database = sf_database. Is this correct?
  3. What will my URL look like?
    I think it should be https://url/sf/api/sf. However, this leads to a 404 error.
  4. When I try to retrieve the metadata (https://url/sf/api/sf/$metadata) I receive a 401 not authorized error. In the runtime config I have activated my login, what else could be wrong?
  5. Finally, what more could I do to find the source of the problem?
  6. Little side-question: why do I need to use /api in the URL? There is nothing in the documentation that refers tot his part of the URL. The original URL was provided by Thinkwise, I have no clue what this /api is needed for.

 

icon

Best answer by Anne Buit 19 February 2020, 08:25

View original

1 reply

Userlevel 7
Badge +5

Hi Hugo,

To test the mobile application directly on the Software Factory, you need an Indicium installed which is configured to use the IAM providing the Software Factory. This is the IAM where the developers are registered and granted access to the Software Factory.

The url will be something like https://url/iam/sf. The api segment is indeed a bit weird and has been replaced in 2018.3 with the alias of the meta-application (iam).

More information can be found in the documentation regarding mobile GUI deployment.

Reply