Adding new connections for version 8.8

When you upgrade to NexJ CRM version 8.8, you must update the environment file or the connection file for your deployment to reflect new structures and support new functionality.

Consult with your development team to confirm whether customized channels have been added to your project.

To update the environment or connection file for your deployment:

In NexJ Studio, open the Deployment layer.
In the Environments tab, open the environment or connection file for your deployment.
Make the following changes:
1. In the Data Source Connections tab, in the Advanced subtab, ensure that the Path field displays the correct version of the JDBC driver. For example, jtds-1.2.2-7.jar.
2. Optional: In the Channel Connections tab, verify that a MailConnection channel connection exists.
  Users can choose to receive two types of new message notifications in their conversations: email notifications and toast popup notifications. To enable users to receive email notifications for new messages, ensure that a MailConnection channel has been added to the environment file.
  Email notification functionality does not require an additional mail channel to be created. An existing mail connection channel is sufficient, for example:
```
<MailConnection channel="Mail" from="outmail@example.com" inFolder="INBOX" inHost="mailserver.example.com" inProtocol="pop3" outHost="outmailserver.example.com" outProtocol="smtp" password="Email_Password" user="user.name@example.com"/> 
```
3. Optional: In the Channel Connections tab, if you are deploying Client Insights functionality, add a HTTP connection that specifies the Grapevine6 URL and client-specific token using the following format.
```
<HTTPConnection channel="insights:ArticleSearch" url="https://hostname/api/v1/searchinterests?token=tokenvalue"/>
```
4. In the Data Source Connections tab, select the FileStorageConnection that you want to configure. In the General subtab, click the Select Data Sources button , remove the CSVExport data source, and add the FileExport data source.
  Note: You can make the same change by modifying the FileStorageConnection element in the Source tab in your environment file:
  1. In NexJ Studio, navigate to the in the Deployment layer.
  2. In the Environments tab, open the environment file for your NexJ application.
  3. In the Source tab, and in the <FileStorageConnection ...> element, locate the <DataSource name="CSVExport"/> property.
  4. Change the <DataSource name="CSVExport"/> property to <DataSource name="FileExport"/>.
  5. Click Save in the toolbar to save the change to the environment file.
5. In the SOA Connections tab, add the required SOA connections.
  The following SOA connections were introduced after NexJ Contact version 6.1 and are required for NexJ CRM version 8.8:
  - nexj:crm:Household:1.0
  - nexj:crm:Interaction:1.0
  - nexj:crm:Note:1.0
  - nexj:crm:Person:1.0
  - nexj:crm:ScheduleItem:1.0
  - nexj:crm:Task:1.0
  - nexj:crm:User:1.0
  - nexj:portal:PortalNotification:1.0
  - nexj:rules:ActionCommandClient:1.0
  - nexj:rules:RuleContainer:1.0
  - nexj:soa:AuthenticationAction:1.0
  - nexj:soa:BaseSOATypeLibrary:1.0
  - nexj:soa:DataMatchServiceUnitTestObjectTypes:1.0
  - nexj:soa:Message:1.0
  - nexj:soa:NotificationService:1.0
  - nexj:soa:PersonMatch:1.0
  - nexj:soa:PortalConfiguration:1.0
  - nexj:soa:PortalIntegration:1.0
  - nexj:sso:Authentication:1.0
  - nexj:ui:AddressComponentClient:1.0
  - nexj:ui:CompanyComponentClient:1.0
  - nexj:ui:EntityComponentClient:1.0
  - nexj:ui:EntityCoverageComponentClient:1.0
  - nexj:ui:OpportunityComponentClient:1.0
  - nexj:ui:OpportunityCoverageComponentClient:1.0
  - nexj:ui:ProgressedOpportunityComponentClient:1.0
  - nexj:ui:RoadshowComponentClient:1.0
  - nexj:ui:RoadshowCoverageComponentClient:1.0
  - nexj:ui:RoadshowLegComponentClient:1.0
  - nexj:ui:RoadshowMeetingRequestComponentClient:1.0
  - nexj:ui:RoadshowScheduleItemComponentClient:1.0
  - nexj:ui:RoadshowTemplateComponentClient:1.0
  - nexj:ui:ScheduleItemComponentClient:1.0
  - nexj:ui:TaxonomyComponentClient:1.0
  - nexj:ui:UserComponentClient:1.0
  - nexj:ui:WorkQueueItemRelatedObject:1.0
  For example:
```
<SOAConnection auth="basic" service="nexj:crm:Household:1.0"/>
<SOAConnection auth="basic" service="nexj:crm:Interaction:1.0"/>
<SOAConnection auth="basic" service="nexj:crm:Note:1.0"/>
<SOAConnection auth="basic" service="nexj:crm:Person:1.0"/>
<SOAConnection auth="basic" service="nexj:crm:ScheduleItem:1.0"/>
<SOAConnection auth="basic" service="nexj:crm:Task:1.0"/>
<SOAConnection auth="basic" service="nexj:crm:User:1.0"/>
<SOAConnection auth="basic" service="nexj:portal:PortalNotification:1.0"/>
<SOAConnection auth="basic" service="nexj:rules:ActionCommandClient:1.0"/>
<SOAConnection auth="basic" service="nexj:rules:RuleContainer:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:AuthenticationAction:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:BaseSOATypeLibrary:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:DataMatchServiceUnitTestObjectTypes:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:Message:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:NotificationService:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:PersonMatch:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:PortalConfiguration:1.0"/>
<SOAConnection auth="basic" service="nexj:soa:PortalIntegration:1.0"/>
<SOAConnection auth="basic" service="nexj:sso:Authentication:1.0">
<SOAConnection auth="basic" service="nexj:ui:AddressComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:CompanyComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:EntityComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:EntityCoverageComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:OpportunityComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:OpportunityCoverageComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:ProgressedOpportunityComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:RoadshowComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:RoadshowCoverageComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:RoadshowLegComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:RoadshowMeetingRequestComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:RoadshowScheduleItemComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:RoadshowTemplateComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:ScheduleItemComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:TaxonomyComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:UserComponentClient:1.0"/>
<SOAConnection auth="basic" service="nexj:ui:WorkQueueItemRelatedObject:1.0"/>
```
Save and close the environment or connection file.

The connections are updated.

After updating the environment file, use the Database Schema Tool in NexJ Studio to issue the create command for your data sources. This generates the appropriate SQL scripts that should be provided to your database administrator.

In a test or development environment, you can use the Data Load Tool in NexJ Studio to issue the recreate command for your data sources. To execute this command, you must have the appropriate security and permissions configured on the database.