IFS Connector Routes Installation

Back to IFS Connector Installation & Configuration

1 Steps
- 1.1 IFS BOLO Platform:
- 1.2 IFS Excalibur Platform:
- 1.3 IFS Enterprise Upstream Platform:
- 1.4 Qbyte FM Platform:
2 Route Compatibility Matrix

Steps

With IFS Connector 2.0, Routes supporting the product to product integrations have been packaged independently of the IFS Connector Engine.

Once the IFS Connector 2.0 Engine has been installed or upgraded from 1.x to 2.0, Routes supporting a product-to-product integration will need to be individually downloaded from the IFS Store, and the following instructions for each route must be followed on the server on which IFS Connector Engine has been installed.

1. Add p2store.p2energysolutions.com to the browser’s trusted sites prior to downloading the pertinent route packages.

2. Download the Route.

For example: download IFS Connector.Integrations.namesandaddresses.zip file from the P2 Store > Product Files > P2 Connector > P2 Connector NamesAndAddresses 1.0.0.0

3. Navigate to the Download folder and Extract the compressed (zipped) file.

4. Copy the extracted DLL (in this example, P2.Connector.Integrations.NamesAndAddresses.dll) to the folder location for the IFS Connector Routes selected during the IFS Connector Engine installation.

5. Right-click the DLL to open the Properties.

6. If the Security for the DLL has the Unblock button highlighted, click the Unblock button > Apply > OK.

7. Repeat steps 2 through 6 for each route pertinent to the product-to-product integration. The following matrix will assist in identifying route packages required per product to product integration.

IFS BOLO Platform:

Product Integration	Route ID	Route Package	Request Route

Product Integration	Route ID	Route Package	Request Route
IFS BOLO - IFS Land
	80/85	IFS Connector Leases	Lease Header
	81/86	IFS Connector Checks	Checks (Payables Invoice)
	82/87	IFS Connector Invoices	Accounts Receivable Invoices
	84	IFS Connector NamesAndAddresses	Addresses
IFS BOLO - iLandMan
		IFS Connector iLandManCommon
	91	IFS Connector iLandManNamesAndAddresses	Addresses
	92	IFS Connector iLandManLeases	Lease Header
	93	IFS Connector iLandManChecks	Checks (Payables Invoice)
	94	IFS Connector iLandManInvoices	Accounts Receivable Invoices
IFS BOLO - IFS Merrick
		IFS Connector ProCountCommon
	100	IFS Connector WellsAndCompletions	Wells and Completions - Site 1
	201	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 1
	401	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 1
	1000	IFS Connector WellsAndCompletions	Wells and Completions - Site 2
	2001	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 2
	4001	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 2
	10000	IFS Connector WellsAndCompletions	Wells and Completions - Site 3
	20001	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 3
	40001	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 3
	100000	IFS Connector WellsAndCompletions	Wells and Completions - Site 4
	200001	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 4
	400001	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 4
IFS BOLO - IFS AFE
		IFS Connector AfeCommon
	52	IFS Connector Vendors	Vendors
	53	IFS Connector Participants	Participants
	54	IFS Connector Actuals	Actual Costs
	55	IFS Connector AfeTemplates	AFE Template
	56	IFS Connector ChartOfAccounts	Chart of Accounts
	57	IFS Connector DivisionOfInterest	Division of Interest
	58	IFS Connector WellHeader	Well Header
	59	IFS Connector AfeHeader	AFE Header
	60	IFS Connector AfeEstimates	AFE Estimates
	61	IFS Connector FieldEstimates	Field Estimates
	62	IFS Connector NonWellCostCenters	Non-Well Cost Center

IFS Excalibur Platform:

Product Integration	Route ID	Route Package	Request Route

Product Integration	Route ID	Route Package	Request Route
IFS Excalibur - IFS Land
	80/85	IFS Connector Leases	Lease Header
	81/86	IFS Connector Checks	Checks (Payables Invoice)
	82/87	IFS Connector Invoices	Accounts Receivable Invoices
	83/88	IFS Connector Suspense	Suspense
IFS Excalibur – IFS AFE
		IFS Connector AfeCommon
	52	IFS Connector Vendors	Vendors
	53	IFS Connector Participants	Participants
	54	IFS Connector Actuals	Actual Costs
	55	IFS Connector AfeTemplates	AFE Template
	56	IFS Connector ChartOfAccounts	Chart of Accounts
	57	IFS Connector DivisionOfInterest	Division of Interest
	58	IFS Connector WellHeader	Well Header
	59	IFS Connector AfeHeader	AFE Header
	60	IFS Connector AfeEstimates	AFE Estimates
	61	IFS Connector FieldEstimates	Field Estimates
	62	IFS Connector NonWellCostCenters	Non-Well Cost Center

IFS Enterprise Upstream Platform:

Product Integration	Route ID	Route Package	Request Route

Product Integration	Route ID	Route Package	Request Route
IFS Enterprise Upstream – IFS Merrick
		IFS Connector ProCount Common
	100	IFS Connector WellsAndCompletions	Wells and Completions - Site 1
	110	IFS Connector ProducingStatus	Completions Producing Status - Site 1
	201	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 1
	301	IFS Connector CompletionDailyDispositions	Completion Daily Dispositions (EDD) - Site 1
	310	IFS Connector SummarizedDailyVolumes	Summarized Daily Volumes - Site 1
	401	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 1
	500	IFS Connector CompletionMonthlyDispUsedFlag	Completion Monthly Dispositions used by Accounting Flag - Site 1
	1000	IFS Connector WellsAndCompletions	Wells and Completions - Site 2
	1100	IFS Connector ProducingStatus	Completions Producing Status - Site 2
	2001	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 2
	3001	IFS Connector CompletionDailyDispositions	Completion Daily Dispositions (EDD) - Site 2
	3010	IFS Connector SummarizedDailyVolumes	Summarized Daily Volumes - Site 2
	4001	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 2
	5000	IFS Connector CompletionMonthlyDispUsedFlag	Completion Monthly Dispositions used by Accounting Flag - Site 2
	10000	IFS Connector WellsAndCompletions	Wells and Completions - Site 3
	11000	IFS Connector ProducingStatus	Completions Producing Status - Site 3
	20001	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 3
	30001	IFS Connector CompletionDailyDispositions	Completion Daily Dispositions (EDD) - Site 3
	30010	IFS Connector SummarizedDailyVolumes	Summarized Daily Volumes - Site 3
	40001	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 3
	50000	IFS Connector CompletionMonthlyDispUsedFlag	Completion Monthly Dispositions used by Accounting Flag - Site 3
	100000	IFS Connector WellsAndCompletions	Wells and Completions - Site 4
	110000	IFS Connector ProducingStatus	Completions Producing Status - Site 4
	200001	IFS Connector BusinessEntities	Business Entity and Business Entity Locations (Parties and Sites) - Site 4
	300001	IFS Connector CompletionDailyDispositions	Completion Daily Dispositions (EDD) - Site 4
	300010	IFS Connector SummarizedDailyVolumes	Summarized Daily Volumes - Site 4
	400001	IFS Connector CompletionMonthlyDispositions	Completion Monthly Dispositions (APT) - Site 4
	500000	IFS Connector CompletionMonthlyDispUsedFlag	Completion Monthly Dispositions used by Accounting Flag - Site 4
IFS Enterprise Upstream – IFS AFE
		IFS Connector AfeCommon
	52	IFS Connector Vendors	Vendors
	53	IFS Connector Participants	Participants
	54	IFS Connector Actuals	Actual Costs
	55	IFS Connector AfeTemplates	AFE Template
	56	IFS Connector ChartOfAccounts	Chart of Accounts
	57	IFS Connector DivisionOfInterest	Division of Interest
	58	IFS Connector WellHeader	Well Header
	59	IFS Connector AfeHeader	AFE Header
	60	IFS Connector AfeEstimates	AFE Estimates
	61	IFS Connector FieldEstimates	Field Estimates
	62	IFS Connector NonWellCostCenters	Non-Well Cost Center

Qbyte FM Platform:

Product Integration	Route ID	Route Package	Request Route

Product Integration	Route ID	Route Package	Request Route
Qbyte FM - IFS AFE
		IFS Connector AfeCommon
	50	IFS Connector AfeHeader	AFE Header - FM
	51	IFS Connector AfeEstimates	AFE Estimates - FM
	63	IFS Connector AfeOverheadMethods	AFE Overhead Methods
	64	IFS Connector Actuals	Actual Costs - FM

Note:

IFS Connector AfeCommon, though not a separate route, is required to be deployed to the IFS Connector Routes folder to allow for the IFS AFE Request Routes to function.
IFS Connector ProCountCommon, though not a separate route, is required to be deployed to the IFS Connector Routes folder to allow for the IFS Merrick Request Routes to function.
IFS Connector iLandManCommon, though not a separate route, is required to be deployed to the IFS Connector Routes folder to allow for the iLandMan Request Routes to function.
If upgrading from IFS Connector 1.x to 2.0, you may want to consider updating the route ID being used for those cases, where a v2 version of the route existed as in these cases the original Request Route will be obsoleted in a future IFS Connector release. The v2 Request Routes are backward compatible with the original version. For example, In IFS Connector 1.x both Lease Header (route ID = 80) and Lease Header v2 (route ID = 85) existed. When deployed with the IFS Connector Leases Route Package these will both be available, but the original route will be marked as deprecated for future removal as the functionality will be covered by the newer version. As such, usage of the route ID 85 for Lease Header should be considered instead of Lease Header v2 after the upgrade.

8. Once the routes and pertinent common packages have been deployed to the IFS Connector Routes folder, restart the IFS Connector Windows Service and the IFS Connector Dashboard website in IIS.

9. Navigate to the IFS Connector Dashboard. The Connector Log tab will display the Routes and their respective versions deployed in the Request Route picklist.