James0611

SNOW to vFire Integration Issue

Discussion created by James0611 on Jul 3, 2018
Latest reply on Jul 30, 2018 by James0611

Hello everyone,

 

We have another tool for Asset Management which is Alemba vFire which we used to integrate in SNOW and EMC-SAS... vFire used to work with my old SNOW environment. When I created a new environment I cannot any more via this URL  http(s)://<server>/api/customers/1/ located on the source of vFire. 

 

my Integration method are as follow below 

 

 

Install the connector*

·       Unzip file (Alemba.Connector.API.v9.8.1.zip)

·       Copy these files to the system config folder (e.g. C:\Program Files\Alemba\vFire\vFire\Config)

o   Alemba.Connector.Snow.Rest.icnf

·       Copy these files to the root folder (e.g. C:\Program Files\Alemba\vFire\)   

o   Alemba.Connector.Generic.REST.dll

o   Alemba.Connector.Snow.Rest.dll

o   Infra.Connector.dll

o   Infra.Connector.Generic.dll

·       Copy these files to the system bin folder (e.g. C:\Program Files\Alemba\vFire\vFire\bin)

o   Alemba.Connector.Generic.REST.dll

o   Alemba.Connector.Snow.Rest.dll

o   Infra.Connector.dll

o   Infra.Connector.Generic.dll

·       Using the Alemba Server Console, run the custom sql file:

o   Alemba.Connector.Snow.Rest.Install.scp

o    Log off from full app and self service portal  

o    Stop vfire service 

o    Do iisreset on CMD

 

Setup the Source

·       Use the integration platform to do the following steps (Admin->Integration)

·       Test the Alemba Snow Inventory Connector

·       Create a new Alemba Snow integration source

o   Enter connection details and test

o   URL: http(s)://<server>/api/customers/1/

o   Customers may not be 1 if Snow is installed in multi-tenanted scenario

o   User must have api access

Resources

·       Application

·       Computer

·       Mobile Device

·       User

Links

·       Application Computer

·       Application Mobile Device

·       Application User

·       *Computer User

·       *Mobile Device User

* TBD

Suggested Field Mappings

·       Application

Ref

{Resource:Name}

Title

{Resource:Name}

Description

{Resource:Application Types}

CMDB Item Type

App

Compliant

{Profile Map:Compliant Map}

Use Compliance < 0 => No

Licence Required

{Profile Map:LicReq Map}

Licence Type

{Resource:Metric}

Compliance

{Resource:Compliance}

Available Licences

{Resource:Available Licences}

Required Licences

{Resource:License Required}

Upgrade Paths

{Resource:Upgrade Options}

Downgrade Paths

{Resource:Downgrade Options}

Total Coverage

{Resource:Total Coverage}

Installations

{Resource:Installation Count}

Users

{Resource:User Count}

·       Computer

Ref

{Resource:Name}

Title

{Resource:Name}

Description

{Resource:Hypervisor Name}

CMDB Item Type

{Profile Map:CMDB Type Map}

Operating System

{Resource:Operating System}

Manufacturer

{Profile Map:Manufacturer Map}

Model

{Profile Map:Model Map}

Serial No

{Resource:Bios Serial Number}

Internal IP Addresses

{Resource:IP Addresses}

·       Mobile Device

TBD

·       User

TBD

·       Links

o   All

·       Link Discovery Status Ref = Discovered

o   Application User

·       Last Used = Last Logon

 

c:\alemba\ION Production\config

 

vfire services needed to open

Connector =

Core Service

messaging

 

==========

 

Here is my test connection This works but the URL should http://10.250.8.116/api/customers/1/ and http://10.250.8.116/ as my sole URL will not populate the assets

On this image it looks to be working but my URL is incorrect

This is the correct URL but my result fails

The URL shown is correct but my results fail

Outcomes