...
Before doing any changes to the publisher components, the new Repository folder has to have the following:
For the Aspire SP2013 Publisher you only need to change the Repository Path on the publisher's configuration and click save.
Note |
---|
IIS should recycle the AppPool for the AspireBDCService automatically, but if it doesn't, then manually recycle it by selecting "Application Pools", then AspireBDCService and click on Recycle. |
Having more than one Business Data Connectivity Service Applications on the same SharePoint Server causes the Aspire SharePoint 2013 Publisher to fail when trying to create the new content source on the Search Service Application and link it to the corresponding BDC Model. Because of this issue the content source won't start crawling when the Notification Endpoint triggers it.
...
Note |
---|
One of the symptoms of this issue was that on the content source configuration the BDC model checkbox wasn’t checked. This is still happening, but it doesn’t affect the fix because the content source does know the BDC url and starts crawling automatically (when the Notification Endpoint triggers it) and everything is indexed correctly. |
2. On the view drop down, select Service Applications.
3. Now select the BDCS where you want to add the custom Proxy Group.
4. On the group of connections drop down, select custom.
5. Select the all of the Service Applications you need except the other BDCS available on the server. Make sure you set the BDCS as the default for this Proxy Group.
6. Save the custom proxy group by clicking Ok OK.
7. If everything works fine, you'll see the new group on the next screen.
...
...
If the SharePoint 2013 server where the Aspire Notification Service solution was deployed is using https, then the Notification Service will also
...
use said protocol. In this case, Aspire needs to know
...
which certificate is needed to connect to the Notification Service.
Follow these steps to register your certificate.
...
Run the following command:
Code Block | ||||
---|---|---|---|---|
| ||||
keytool -import -noprompt -trustcacerts -alias <AliasName> -file <certificate> -keystore <KeystoreFile> -storepass <Password> |
<AliasName>: an alias for your site certificate
<certificate>: path to the certificate you want to register
<KeystoreFile>: path to the keystore used by your Java installation. The default location is: %JAVA_HOME%\lib\security\cacerts.
<Password>: password for the keystore. The default value is changeit.
Check that your certificate is now registered:
Code Block |
---|
keytool -list -keystore "%JAVA_HOME%/jre/lib/security/cacerts" |
See Aspire BDC Service FAQ page.
See Notification Service FAQ page.
See Security Pre-Trimmer FAQ page.
...
Due to a security issue observed with the protocol, Microsoft has recommended deactivating SMB1 from Windows servers.
This affects the SP2013 Publisher, which uses the JCIFS library to communicate with a file share. The JCIFS library only supports the SMB1 protocol; it does not support the SMB2 or SMB3 protocols currently. As a result, the SP2013 Publisher may be unable to communicate to a Windows file share (using protocol SMB2 or SMB3).
We are working on finding a solution for this scenario (SMB1 deactivated).