Perform End-to-End Validation

Complete the following tasks to validate the pre-installation tasks.

Verify DNS entries from SharePoint hosts to Jive DNS servers.

Using nslookup, verify host names point to correct IPs (both ways).
1. Sign in to each SharePoint server.
2. Perform an nslookup to the Jive URL Host Name (URL minus http:// and /path/).
  
  nslookup giljive.hubteam.jiveland.com Verify IP for host name is correct
3. Sign in to each Jive webapp node.
4. Make an nslookup to the SharePoint Integration Site Collection Host Name (URL minus http:// and /path/)
  
  Verify that the IP for the host name is correct.
Note:
- The source of truth for the correct IP per Host name for SharePoint should be provided by the customer.
- For Jive On-Prem, the customer also needs to provide the correct IP for their Jive instance (Jive URL).
- If nslookup does not work, despite /etc/hosts, try ping or telnet
  - ping – may be blocked, but will show the IP address.
  - telnet - <host domain> <port (ex. 443 or 80)>
    
    Result: immediate then bad port, stuck on trying ... bad host domain.
Test and confirm connectivity between Jive webapp servers and SharePoint.

With a series of curl commands, confirm that Jive can make the necessary network calls to SharePoint and that the WSP is installed and deployed.
1. Sign in to each webapp node.
2. Run the following curl command to verify network calls for SharePoint connection by substituting the following parameters:
  - Integration Admin User - Domain
  - Integration Admin User
  - Integration Admin Password
  - SharePoint Integration Site Collection URL
```
curl -v -k -L --ntlm -u '<domain>\<user>:<password>' -X GET <SharePoint Integration Site Collection URL>ions
```
Run the following Curl command to verify that the WSP is installed and deployed:
```
curl -v -k -L --ntlm -u '<domain>\<user>:<password>' -X GET <SharePoint Integration Site Collection
      URL>/_layouts/15/Jive/rest/service.svc/sitecollection/infov2
```
Note:

The NTLM handshake goes through the following HTTP response codes: 401 => 401 => 200 | 302.
Test and confirm connectivity between SharePoint servers and Jive.
1. Using the provided script, verify that SharePoint can make the necessary calls back to Jive.
2. Update the script with JiveURL.
3. Run the script, from the SharePoint Administration Server PowerSell.
Note:

A 403 or 500 response code is a successful test.

The http-access logs within Jive must be looked at to verify that the 403 or 500 occurred from there and not from somewhere in-between.
Validate Jive SSL Certificates.
1. Use the provided script to test and confirm connectivity from Jive to Jive (shindig). Alternatively, if the script is not available, grep Jive sbs logs for SSL certificate errors related to shindig
2. Update and run the script from the Jive webapp nodes.
  
  Note:
  
  If the script is not yet available, the Jive sbs logs may be checked for any occurrence of SSL certificate errors related to shindig.
Implement and confirm Firewall rules.
1. Show firewall rules that are setup to allow the following URL:
  
  <SharePoint Integration Site Collection URL>/_layouts/15/Jive/rest/service.svc
2. Share firewall rules which satisfy this requirement.
  
  This may also be configured to allow specific IP address instead of Host Name.
Verify installed and deployed WSP version.

Verify correct WSP version is installed and deployed by navigating to the SharePoint Central Admin > System Settings > Manage Farm Solution page.
Confirm user mapping setup on Jive and on SharePoint.
1. Verify user mapping attribute (claims ID) is setup to populate user profiles within Jive.
2. Use the provided PowerShell script to ensure SharePoint recognizes the mapped attribute (claims ID).

Before you Install