Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 27 Next »

Supported Version

From 360 SP8 and up.

Limitations


Permissions

Database system:   

MSSQL 

MSSQL/ORACLE/POSTGRES 

Database server: 


IP or DNS name 

Source database name: 


Source database name minimum of administrative READ access 




SQL login username: 



SQL login user password: 


The password for the Username.

ADindexuserusername:   


User ID needs a minimum of administrative READ  access on fileshares with referenced files 

ADindexuserpassword: 


The password for the Username 

ADindexuserdomain: : 


Domain name of indexuser

P360filesharepath


UNC path for storage location of P360 files

P360 API AD-user:  


 Username of AD-user with "All Access" to P360’s API. The user also has to be a 360 user

P360 API AD-user password: 


 Password of AD-user with "All Access" to P360’s API. The user also has to be a 360 user

360 Enterprise Search API URL – SI.WS.Core 


Servername and port to access the SI.WS.Core service. E.g: http://servername:8088

Webclient URL


 Url for accessing the UI for P360, e.g. http://360

360 Version
Supported versions are 4.1 SP8 and higher


NOTES for P360 Connector 

  • If 360 system language != norwegian you need to replace "Tilgangsgruppe" with "Accessgroup" in connectordefinition.xml
  • Need access to 360 virksomhetssøk api 
    • If error 404.17 while browsing API: .NET 3.5 HTTP Activation need to be enabled
  • If customer is using BLOBs for storing files you need to change ConnectorDefinition.xml to ConnectorDefinition.xml.blob
    • Check this by "select * from dbo.vo_volume where vo_desc = 'Standard'". If vo_rootdir is "NULL" then you have to use BLOB

Installing P360 connector

Installing connector

  1. Install P360 MSI

  2. Add authplugin manually to postgres:

    • Before starting fetch service add following to search.identification_system (in PgAdmin3):
      {{ID}};"P360";"Via.Dbc.P360.AuthenticationPlugins.dll";FALSE, where {{ID}} is generated by sequence

    • Start Fetch Service

    • Make sure config.connector_type have the column "identification_system_id" set to the generated ID for p360 connector

    • Verify authplugin.dll is running by logging in

How To enable "DRAFTS" from search:
There is two types of drafts. Either documentcard's draft or a file draft. Some customers may only want to search within stored cases and files, without getting hit on cases/files that are in progress or on hold.

1.Disable documentcard's drafts:Uncommented Document.Identity.DiscoveryQuery:

--and j1.do2_js_recno in (6,5,10) --journalført,ekspedert,godkjent
2. Disable file drafts:
Uncomment DocumentAttachments.GetistByParentQuery:
--and df.df_dfs_recno=2 --Filstatus=ferdig
To enable "DRAFTS" comment out the lines with "--" in front

How To Use P360 Merged Connector: (Not fully secure. Need accept from customer before using this connector)

Description

Instead of hits from Activity, contact, project, document and case, this connector will merge all those types into one type "Document" with most important metadata. The other metadata is still avaliable but need to make custom search rule to display.


Installing/upgrading connector
When installing and upgrading P360 connector the installer/upgrader will deploy new files for P360:

  • ConnectorDefinition.xml - Rename this to ConnectorDefinitionOrg.xml
  • ConnectorDefinition-Merged.xml -  Rename this to ConnectorDefinition.xml
  • IdentificationDefinition.xml 
  • Via.Dbc.CommunityFetchService.exe.config -  Rename this to Via.Dbc.CommunityFetchServiceOrg.exe.config
  • Via.Dbc.CommunityFetchService-Merged.exe.config -  Rename this to Via.Dbc.CommunityFetchService.exe.config
  • Copy ..\P360\p360Hover.html to \RestService\Resources\Themes\Standard\Templates\Hover and rename to p360.html
  • Copy ..\P360\p360Item.html to \RestService\Resources\Themes\Standard\Templates\Item and rename to p360.html

  • Add authplugin manually to postgres:

    • Before starting fetch service add following to search.identification_system (in PgAdmin3):
      {{ID}};"P360";"Via.Dbc.P360.AuthenticationPlugins.dll";FALSE, where {{ID}} is generated by sequence

    • Start Fetch Service

    • Make sure config.connector_type have the column "identification_system_id" set to the generated ID for p360 connector

    • Verify authplugin.dll is running by logging in

The files without “-merged” in filename while be used as the default files. 

Before upgrade:
Backup following files:
-…\P360\ConnectorDefinition.xml
-…\P360\CommunityFetchService.exe.config
-\RestService\Resources\Themes\Standard\Templates\Hover\p360.html
-\RestService\Resources\Themes\Standard\Templates\Item\p360.html

After upgrade:

  • Stop P360 Fetch service if running!
  • Make sure HTML files are still located in the same locations as mentioned in "Before Upgrade". Else:
    • Copy ..\P360\p360Hover.html to \RestService\Resources\Themes\Standard\Templates\Hover and rename to p360.html
    • Copy ..\P360\p360Item.html to \RestService\Resources\Themes\Standard\Templates\Item and rename to p360.html
  • ConnectorDefinition.xml - Rename this to ConnectorDefinitionOrg.xml
  • ConnectorDefinition-Merged.xml -  Rename this to ConnectorDefinition.xml
  • IdentificationDefinition.xml 
  • Via.Dbc.CommunityFetchService.exe.config -  Rename this to Via.Dbc.CommunityFetchServiceOrg.exe.config
  • Via.Dbc.CommunityFetchService-Merged.exe.config -  Rename this to Via.Dbc.CommunityFetchService.exe.config
  • No labels

ayfie