JMP106 Make Your
Business Open and Social
using IBM Notes Social
Edition 9.0.1
Thomas Evans | Software Engineer | IBM
Yun Zhi Lin | Software Engineer | IBM

© 2014 IBM Corporation

Giving Credit


2

This presentation mentions the following Copyrights and Trademarks
–
IBM® Notes®
–
IBM® iNotes®
–
IBM® Domino® Administrator
–
IBM® Domino®
–
IBM® Connections®
–
IBM® Notes® Social Edition
–
IBM® iNotes® Social Edition
–
Apache Shindig ™

About Us
Yun Zhi has been working at IBM for the past 7 years. He is the lead
template developer for Widget Catalog and OAuth Credential Store.
He has in depth of knowledge in many technical areas, including
XPages and Eclipse plugin development. Over the past year, his
major focus is OpenSocial. He reaches out to help business partners
and other product teams to integrate their applications with
OpenSocial.
Thomas worked for IBM for the past two years. From day one he has
been involved with the Notes/Domino Social Edition release. Mainly
focusing on managing and assisting with the deployment of the Social
Edition releases internally at IBM for testing purposes. Most recently
Thomas has stepped in to assist with the integration and maintenance
of the OpenSocial Component into the IBM enterprise deployments of
Notes and iNotes Social Edition.

3

Agenda









4

Terminology
Deployment Overview
–
High-Level Deployment View
–
Detailed Deployment View
Setup and Configuration
–
Pre-requisites
–
Detailed Steps
●
Database creation and configuration
●
User-centric settings
●
Server centric settings
●
Verification
IBM Connections 4.x Integration
Troubleshooting
Summary

Terminology






5

OpenSocial
–
OpenSocial is an open standard which defines APIs that can be used to build social
applications using HTML, JavaScript, and CSS. The specification includes both
JavaScript and REST APIs. OpenSocial leverages many other standards, such as
Activity Streams and OAuth.
–
See: http://opensocial.org/
Embedded Experiences
–
Embedded experiences is a method of embedding the “experience” or functionality
from one application into a different, host application. The end user experiences the 3rd
party application in their host application environment as if they were using it directly
from the 3rd party provider.
Activity Streams
–
Activity Streams is an open standard which defines a data model to represent a stream
or list of actions performed by users and applications. This specification DOES NOT
define any APIs, it simply defines the data model.
–
See: http://activitystrea.ms/

Terminology






6

Apache Shindig
–
Apache Shindig is an OpenSocial container and helps to start hosting OpenSocial apps
quickly by providing the code to render gadgets, proxy requests, and handle REST and
RPC requests. Shindig is the reference implementation for the OpenSocial
specification.
–
See: http://shindig.apache.org/
Domino Server with Shindig
–
A Domino Server with the OpenSocial Component installed. This server runs portions
of the Apache Shindig project as a web application based on OSGi. This server is
responsible for rendering OpenSocial gadgets.
DOTS
–
An acronym for “Domino OSGi Tasklet Service”, it is a server task that allows OSGi
plugins to contribute scheduled “tasklets” that perform some amount of work on the
server. The Widgets framework in iNotes contributes a DOTS tasklet to push Widgets
to iNotes users by policy.

Terminology






7

OAuth
–
An open standard used used for authorization. Allows the User to grant access to
private resources on a Service Provider to another site, the Consumer, without sharing
user credentials
Widget Catalog
–
A database that is used to store metadata (i.e. a “widget”) about services for use within
Notes and iNotes. In the case of OpenSocial Component, the focus is on OpenSocial
gadgets for which widgets are created and stored in the Widget Catalog.
Credential Store
–
A secure database that is used to store proxy rules, gadget capabilities, and OAuth
information on the Domino Server with Shindig.

Terminology




8

Locked Domains
–
A mechanism to isolate individual gadgets from each other. Each gadget is rendered in
a separate iframe such that each iframe's source is unique. Any XHR requests the
gadgets make to the Domino Server with Shindig occurs on a gadget's locked domain.
Other resources,such as images and Javascripts, utilize a common unlocked domain.
–
See: https://cwiki.apache.org/confluence/display/SHINDIG/Locked+Domains
FQDN
–
Fully qualified domain name, ex. somehost.example.com

Agenda









9

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

SaaS / Public Cloud

Dedicated Cloud

On Premises



–

Agility and Price Advantage Customization, Flexibility
●

Pay per use, standard terms of use

●

You own the license or capital

●

Automatic updates

●

Choice of where and how data is managed

●

Shared infrastructure and ops

●

Completely customizable

●

Instant scale

●

Dedicated infrastructure

Considerations

10

How do I buy?
How quickly can I get new features?
Does it matter where data resides?
How important is price?
Do I need to scale up and down rapidly ?
Who manages?
Do I need to customize? Special integrations?



The OpenSocial Component for Domino serves a distinct purpose when deployed on
–
–

A Domino mail server
●
Supports Widgets and LiveText in iNotes

–
–

A Domino server running Shindig
●
Hosts the credential store application
●
Renders OpenSocial Gadgets

–
–



Run the OpenSocial Component installer once per server, and use configure settings to
differentiate purpose
–

11



12

Single server
–
Useful for development, testing, and POCs



13

Single mail server and single Domino Server with Shindig
–
Useful for trying out Social Edition with an existing mail server



14

Clustered mail servers and single Domino Server with Shindig
–
Useful for trying out Social Edition with an existing mail server cluster
–
Likely what small deployments would look like



15

During the course of this session, this is the type of environment that will be configured

Agenda









16

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary



Server-side
–
Domino 9.0 or above with OpenSocial component installed
●
Includes OSGI bundles
- Shindig libraries are included as a bundle
●
Includes toolbox.ntf and websecuritystore.ntf needed for the Widget Catalog and
Credential Store, respectively
●
Required on Mail server and Domino Server with Shindig
●



17

Client-side
–
Notes
●
Install Notes Social Edition 9.0 or above with the OpenSocial Component included
–
iNotes
●
Server side notes.ini settings are used to enable OpenSocial functionality in iNotes
9.0 or above.



18

Single mail server and single Domino server with Shindig

Gadget Rendering Process - iNotes

19

Gadget Rendering Process - Notes


OpenSocial gadgets and Embedded Experience in Notes client may render in one of the two
ways:
–
Rendering locally: The OpenSocial component in Notes client handles the rendering.
–
Rendering remotely: The OpenSocial component on Domino Server with Shindig
handles the rendering.
–



Gadgets using OAuth are rendered remotely and the others, by default, render locally.




20

Notes client can be configured to render all gadgets remotely
–
Add com.ibm.rcp.toolbox.opensocial.provider/remoteServerOverride=true to
<install_dir>/framework/rcp/plugin_cusotmization.ini
–
Useful in environment like Citrix to reduce the client footprint.



21

Rendering locally



22

Rendering remotely

Agenda









23

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Demo Environment Pre-requisites


Mail and Domino server with Shindig
–
IBM Domino 9.0.1 Social Edition with OpenSocial component add-on
–
WebSSO for the Renovations domain
–
iNotes redirect
–
Demo users registered
–



IBM Notes 9.0.1 Social Edition






24

IBM Connections 4.5

Agenda









25

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Creating the Credential Store


On the Domino Server with Shindig





Create the Credential Store network encryption key
–
Run the command “keymgmt create nek nekname” on the Domino Server with Shindig
console
●
Replace nekname with your own value
–
–

26

Verify the NEK is created successfully


27




Issue the command “keymgmt create credstore nekname” on the Domino Server with
Shindig console
–
The nekname is same as previous step




28

Verify credstore.nsf is created under dataIBM_CredStore


29

Creating the Credential Store in a cluster


Export the NEK to a password protected key file
–
Issue the command “keymgmt export nek nekname filename filepassword”
●
The nekname is the same as the previous step
●



Copy the key file to all servers in the cluster




Import the NEK from the key file into the ID file of each server
–
Issue the command “keymgmt import nek filename filepassword” on all others in the
Domino servers with Shindig cluster
–




30

Create replicas of the credstore.nsf on all servers in the Domino server with Shindig cluster

Configuring the Credential Store


31

Go to the Access Control List for the credential store database



Add “Admin” to the ACL list
–
–

32



Assign Manager Access
and [Admins] role for
Administrators




33

LocalDomainServers
have Manager access
and the Admins role by
default












Open the OAuth Token Store
database (credstore.nsf)
Open the Configuration view
Click Create Encryption Key
button
Click Create new encryption
key in the pop up dialog
Verify the encryption key is
created successfully
Click OK to close all the
dialogs



The configuration of Credential Store is
complete !
34

Database Creation and Configuration

DEMO

35

Creating the Widget Catalog


Widget Catalog is created on the mail
server




36

Inherit future design changes
–
If selected when catalog updates
agent will need to be re-enabled

Configuring the Widget Catalog


37

Go to the Access Control List for the widget catalog database



Add “Admin” to the ACL list
–

Admins should be listed
individually in the ACLs

–
–

If an admin group is used
every notes client must
contain that group in the
local names.nsf for
OpenSocial widgets to
render




38

Assign Manager Access
and Admins role





39

Open the Widget Catalog database
Open the Configuration view of catalog
Click Configure Credential Store button



Click Browse in the pop
up dialog




Select the credstore.nsf
created in previous steps
and click Open




40

Verify the information is
correct and close OK to
close the dialog.



Click Configure Meta-data button
–
Demo deployment uses all default values
–



●
●









41

See http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Proxy_metadata_configuration



Configure Widget Catalog launch settings




Open Widget catalog database launch
properties
–
“When opening in Notes” select ToolboxMainFrameset-XPage
–
–

“When opening in a browser” select
Open designated XPage and home.xsp

–
–


Catalog administration can only be done from
the classic UI
–
Open in Domino Administrator
–
Click Administration button on XPage UI
–

42



43

Go to View → Agents





Enable the PushToCredStore agent
–
The mail server must be trusted by the Domino Server with Shindig in order
for the PushToCredStore agent to function properly.
More information about Roles & Agents can be found on :
–
http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21459846







44

The configuration of the Widget Catalog is complete!

Database Creation and Configuration

DEMO

45

Agenda









46

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Settings overview and which client they are for :




47

Managed account (Notes only)
Policy
–
Desktop Settings
●
Widgets (Notes and iNotes)
●
Accounts (Notes only)
–
Security Settings
●
Execution Control List (Notes only)
●
Proxies (iNotes only)
–
Mail Settings
●
iNotes user only (iNotes only)

Creating a Managed Account


Created on the Domino Mail server





48

Open the Accounts view
Click the Add Account button in the action bar



49

Under the Basics tab
–
Select a recognizable name and description for this account
–
Account Type: other
–
Account server name: http://<Shindig Server FQDN>/fiesta/container
●
If creating Domino Servers with Shindig in a cluster use FQDN of Reverse
Proxy
–
Use Domino single sign-on if available: Enabled
–
Domino single sign-on server: <Shindig Server FQDN>
●
If creating Domino Servers with Shindig in a cluster use one of the servers
Notes name to allow for fail over
–
Allow other accounts to use this log in information: Disabled
–
Accept the other default values


50

Account Server Name field must be scrolled to view the full path



51

On the Advanced tab select the Edit list... button




52

Add the following parameter
–
Item: PreferredUsernameField
–
Value: fullname



If creating Domino Servers with Shindig in a
Cluster add the following to enable fail over
–
Item: useclustermates
–
Value: 1



53

Verify the information in the properties list and click “Save & Close” to close the new account

Policy Settings


Open the mail servers Policies view
–
Using the Organizational policy will enable OpenSocial features for all users in the Org
–
–
–
–
–
–
–
–
–
–
–
–
–

54

Explicit policies can be used to restrict the enablement of the OpenSocial features

Policy Settings


The OpenSocial component uses
the following policy documents
–
Desktop settings
–
Security settings
–
Mail settings
●
Required only for iNotes
●



55

Supplement existing policy or create
these policy documents

Policy Settings – Desktop Settings


Open the IBMConnect2014DesktopSettings document in edit mode




56

Go to the Widgets tab

Widget catalog server
–
RenovationsMail/renovations
Widget catalog application name
–
toolbox.nsf
Widget catalog categories to install
–
WidgetsForAll
Read through widget options and Enable or
Disable them
Gadget Server URL
–
Points to Domino Server with Shindig
–
In a Cluster points to Reverse Proxy
–
http://RenovationsShindig.renovations.com/fiesta
Gadget Cache URL
–
Optional













57



Add the Managed Account
–
On the Accounts tab click
Update Links
–
On the resulting dialog click
Selected supported
–
Click OK
–
–

58






59

Select the Security Token
Account
Click OK



The Security Token Account now
appears in the Account Links section



60

Click “Save & Close” to save the Desktop Settings document

Policy Settings – Security Settings




61

Open the IBMConnect2014SecuritySettings document in edit mode
Push an ECL setting to Notes users
In the Execution Control List tab, click Edit



62

In the resulting dialog, click Add...



Add “Admin” to the ECL and
check the “Ability to configure
Widget capabilities” checkbox
–




63

Click OK




64

Whitelist the server requests
In the Proxies tab, click Edit list...






65

Add a proxy rule
–
Context: /xsp/proxy/BasicProxy
–
URL: http://RenovationsShindig.renovations.com
–
Actions: GET,POST
–
Cookies: DomAuthSessId,LtpaToken,LtpaToken2
–
Mime-types: *
–
Headers: *
Click Add/Modify Value >>
Click OK


66



Verify the proxy rule










67

Click “Save & Close” to save
the Security Settings
document

Policy Settings – Mail Settings


No specific Mail policy settings need to be set
–
My Widgets specific Mail settings have been deprecated in favor of desktop settings in
Domino 9
–
–






68

For Desktop policy settings to apply to iNotes users, a Mail policy is required
–
See this technote
●
http://www-01.ibm.com/support/docview.wss?uid=swg21384073
●
Reference # 1384073

Policy Settings


To ensure iNotes users receive the policies applied to them the Admin Process much
process mail policies




Default interval is 12 hours





69

Execute manually via “tell adminp process mailpolicy” in the Mail server console

User-Centric Settings

DEMO

71

Agenda









72

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Configuration Settings


Configuration Settings are used to configure the OpenSocial component on the Domino
Server




73

The Mail server and Domino server with Shindig require different server configuration

Configuration Settings – Mail server




74

Go to the Configuration tab
Select the Server → Configurations view
Select the configuration document for the server and select Edit Configuration






75

Go to the NOTES.INI Settings tab
Click Set/Modify Parameters



Add the following parameters by entering each Item and Value pair into the corresponding
fields and clicking Add/Update



Item

Value

iNotes_WA_Widgets

1

iNotes_WA_LiveText

1



iNotes_WA_OpenSocial

1



iNotes_WA_EnableEE

1



iNotes_WA_Widgets_AutoUpdate_Group

iNotesUsers

iNotes_WA_Widgets_AutoUpdate_Day

1









–


76

Any group name can be used for the AutoUpdate group and there is no default value




77

Enter each Item-Value pair
Once all values are entered click OK



Verify the NOTES.INI Settings




Click “Save & Close” to save
the Configuration Settings
document




78

The server needs to be
restarted for all changes to
take affect

Configuration Settings – Domino Server with Shindig


Switch to the Domino Server with Shindig






79

Go to the Configuration tab
Select the Server → Configurations view
Select the configuration document for the server and select Edit Configuration



Enable Configuration for
Domino server with Shindig
in Basics tab
–
–

80

The Social Edition tab is
now visible in the
Configuration document



Switch to Social Edition tab




On the Basics tab fill out the following fields
–
Locked domain suffix: -locked.renovations-gadgets.com
–
Domain name for unlocked gadgets and content fetching: unlocked.renovationsgadgets.com
–
Shindig server(s) host name: RenovationsShindig.renovations.com
●
When using a Shindig cluster use the FQDN of the reverse proxy/load balancer
–
Use HTTPS for OAuth redirect URLs: Disabled
●
SSL is not enabled for this deployment
–

81


82



Click “Save & Close” to save the Configuration Settings document









83

The server needs to be restarted for all changes to take affect

Server Centric Settings

DEMO

84

Agenda









85

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Verify Policy in Notes



86

In Notes, go to File → Preferences
In the Accounts section, verify the “Security Token Account” configured earlier is listed

Verify Policy in Notes


In the Widgets section,
verify the “Catalog server”
and “Catalog name” fields
are populated




87

Note: The “Categories to
install” field will be
populated once some
Widgets are added to the
catalog

Verify Policy in iNotes




88

In iNotes, verify that the My Widgets sidebar panel appears
In the My Widgets sidebar menu, verify that “Browse Widgets Catalog...” appears
Note: The catalog can be opened, but no Widgets have been populated yet

Importing a Widget into the Widget Catalog







89

A Widget can be imported into the Widget Catalog as a series of files
–
A file for the Widget definition, e.g., <gadget name>.extension.xml
–
A file for the proxy rules, e.g., <gadget name>.proxy.xml
–
A file for the OAuth information, e.g., <gadget name>.oauth.xml
Only the Widget definition file is required
Selecting the Widget definition file for import will automatically locate the other files in the
same directory





90

Open the Widget Catalog in Domino Administrator
Click Import





Browse to the widget's extension.xml file
in the dialog
Click Open




91

Note: There are no proxy.xml or
oauth.xml files because the gadget
doesn't use OAuth and the default proxy
rules are acceptable




92

The newly created widget document will open automatically
Click Edit




93

Assign this widget to the “WidgetsForAll” category
Reminder: “WidgetsForAll” is the category that is setup to be pushed by policy



94

Click the Approve button


Click OK to close the proxy dialog



95



96

The Widget is approved ! We are ready to test it !

Unit Test Verification in Notes



97

Open the Notes client
Replicate the Widget Catalog
–
This happens automatically during the normal replication schedule, but is done here for
expediency



98

You will see the widget is installed in Notes.




99

Double click the widget to render it in a new window

Unit Test Verification in iNotes


In the Mail server console, execute tell dots run UpdateWidgetsTask to push Widgets to
iNotes users by policy




100

Note: This would normally happen on a daily basis based on the
“iNotes_WA_Widgets_AutoUpdate_Day” value set in configuration settings


101



In iNotes, in the My Widgets sidebar, the widget should be installed




102

The asterisk next to the widget indicates it was pushed by policy and cannot be removed



Double-click on the widget to render it in a new Tab




●

103

Unit Test Verification

DEMO

104

Agenda









105

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary



IBM Connections 4 provides two OpenSocial Gadgets for use within IBM Notes and Domino
deployments.




An Embedded Experiences gadget transforms Connections notifications into rich, interactive
experiences




106

An Updates gadget brings the activity stream experience from the Connections homepage
into your Notes client



Export the IC4 widget configuration
–
Launch a WSAdmin console on your connections server







–
–

107

Load the “gadgetAdmin.py” file



108

Execute the NotesRegistrar.registerGadgets command with these arguments
–
appId – the ID of the OAuth2 application to register for the gadgets
–
appLabel – the label for the OAuth2 application to be registered
–
callbackURL – the OAuth2 callback URL for the Domino environment
●
Protocol here must match OAuth redirect url protocol in the Domion Server with
Shindig Configurations document
–
outputDir – the directory in which the Widget configuration files will be created



Import the Connections Activity Stream widget into Widget Catalog
–
Open the Widget Catalog and click Import
–



109



Select the “AS.Gadget.extension.xml” file
–
The import process will automatically find the co-located oauth.xml and proxy.xml for
the same prefix “AS.Gadget”
–

110



Select Yes, to replace existing Widget Documents if they exist









Select OK
–
–

111



A newly created Widget Document will open automatically
–
Put this Widget Document in Edit mode
–

112



113

Select the Category drop down and add this widget to the WidgetsForAll category




114

Approve the Widget




115

Select OK on the Widgets Proxy Information dialog



Select OK on the Widgets OAuth Information dialog
–
Consumer Key and Consumer Secret will NOT be displayed in the UI
–



116



117

Confirm the Approval



Import the Connections Embedded Experiences widget into Widget Catalog
–
Open the Widget Catalog and click Import
–



118



Select the “EE.Gadget.extension.xml” file
–
The import process will automatically find the co-located oauth.xml and proxy.xml for
the same prefix “EE.Gadget”
–

119



Select Yes, to replace existing Widget Documents if they exist









Select OK
–
–

120



A newly created Widget Document will open automatically
–
Put this Widget Document in Edit mode
–

121



122

Select the Category drop down and add this widget to the WidgetsForAll category




123

Approve the Widget




124

Select OK on the Widgets Proxy Information dialog



Select OK on the Widgets OAuth Information dialog
–
Consumer Key and Consumer Secret will NOT be displayed in the UI
–



125



126

Confirm the Approval



127

In the server console, execute tell dots run UpdateWidgetsTask
–
This process pushes widgets to iNotes users
–
By default this happens once a day
–
“iNotes_WA_Widgets_AutoUpdate_Day” value set in configuration settings controls this
●
“iNotes_WA_Widgets_AutoUpdate_Min” can be used aswell


128















129

Open IBM Notes Social Edition as Samantha Daryn
The two IBM Connections 4 Widgets appear in the My Widgets sidebar
















130

Launch Mail for Samantha
Open a notification from IBM Connections 4
When prompted, authorize the gadget – this is the “OAuth Dance”

Agenda









131

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Collecting Support Data


OpenSocial component functionality spans many components and across client and server.
Therefore support data may also need to collect across client and server.




Support data should be collected from all components involved in gadget rendering process.
–
For example, if an OpenSocial gadget that uses OAuth fails in Notes client, both Notes
client and Domino Server with Shindig logs need to be collected.
–



132

Collecting Support Data guide can be found on:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Collecting_support_data_OSC90

Collecting Support Data in Notes



133

Support Data in Notes can be collected via IBM Support Assistant(ISA)



134

Enable customized tracing for “Embedded Experience”



135

Pause the collector and reproduce the issue




136

Go back to Help → Support → Collect Support Data
“Collect” the ISA

Collecting Support Data in iNotes






137

The iNotes client provides a console, the console content can be viewed and copied from
browser.
More details can be found on:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/using-the-inotes-console-log-to-inspect-and-copy
The iNotes console provides a build number for WCAN, which is the build number of
OpenSocial Component.

Collecting Support Data in Domino


OpenSocial component on Domino generates logs in osgi workspace. There are two
workspace folders that should be checked for logs
–
OSGI on HTTP tasks: <Domino Data>/domino/workspace/logs
–
OSGI on DOTS: <Domino Data>/domino/workspace-dots/logs
–



Custom logging must be enabled by modifying rcpinstall.properties file, and related task
need to be restarted after making changes
–
OSGI on HTTP tasks: <Domino Data>/domino/workspace/.config/rcpinstall.properties
–
OSGI on DOTS: <Domino Data>/domino/workspace-dots/.config/rcpinstall.properties
–



138

Refer to the Collecting Support Data guide about what custom tracing can be enabled

Troubleshooting guide


There is an online troubleshooting guide for OpenSocial Component to help to quickly
identify the deployment problem:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Troubleshooting_OSC90




NOTE: Only common problems and solutions are documented in this guide.




139

How to use this guide
–
Determine the symptom of your environment by the collected support data or the errors
on the UI
–
Check the guide to see what are the possible problems to this symptom
–
Check your environment for the possible problems and diagnose what's the root cause
in your environment
–
Apply the possible solutions to the root cause


141















142

The Connections 4 notification now
renders as an Embedded
Experience!





143

There is a new Shortcut icon for “Updates”
There is also an entry in the Open list for “Updates”





144

Opening “Updates” via the Shortcut icon or the Open list will open “Updates” in a new tab
–
The “OAuth Dance” is not required again since OAuth is configured with Shared Tokens
enabled for this service





145

Clicking on individual entries will open an Embedded Experience, just like the IBM
Connections 4 homepage and the notification in mail




Open IBM iNotes Social Edition as Samantha Daryn
The IBM Connections 4 EE Widget appears in the My Widgets sidebar









146

Reminder: the “Updates” Widget is for Notes only, and it not installed in iNotes per the
Platform field in the Widget document








147

Open a notification from IBM
Connections 4
It is now renders as an Embedded
Experience!


DEMO



148

Agenda









149

Terminology
Deployment Overview
–
–
–
Pre-requisites
–
Detailed Steps
●
●
●
●
Verification
Troubleshooting
Summary

Summary








The OpenSocial Component deployed and configured as two server components
–
Mail server and Domino Server with Shindig
–
Domino 9.0 or above and OpenSocial component 9.0 or above need to be installed on
the two server components. The server components are configured to be different.
–
The two server components can be deployed on a same Domino server or different
Domino servers, or clustered Domino servers
OpenSocial widgets need to be trusted and configured to render in Notes and iNotes
By default, there are some intervals for certain settings (policy , DOTS, OAuth and proxy
data) applied to end users or Domino server. Administrator can issue commands to apply
the changes immediately.
Connections gadgets can be easily exported and imported into Domino.
Troubleshooting guide is helpful to identify and resolve deployment issues.



–
–
150

Resources















152

OpenSocial Tutorials: https://opensocial.atlassian.net/wiki/display/OS/Home
OpenSocial Explorer: http://opensocial.github.io/explorer/download.html
IBM Domino 9.0 Social Edition OpenSocial Component Deployment Cookbook:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/IBM_Domino_9.0_Social_Edition_OpenSocial_D
IBM Domino 9.0 Social Edition OpenSocial Component Troubleshooting:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Troubleshooting_OSC90
Adding IBM Connections Activity Stream and Embedded Experience gadgets to the IBM
Notes Widget Catalog: http://www-01.ibm.com/support/docview.wss?uid=swg21627570
Using HTTPS When Rendering OpenSocial Gadgets:
Configuring the OpenSocial component SSO account in a clustered environment:

Engage Online




SocialBiz User Group socialbizug.org
– Join the epicenter of Notes and Collaboration user groups
Follow us on Twitter
Engage
– @IBMConnect and @IBMSocialBiz

Online



LinkedIn http://bit.ly/SBComm
– Participate in the IBM Social Business group on LinkedIn:



Facebook https://www.facebook.com/IBMSocialBiz
– Like IBM Social Business on Facebook



Social Business Insights blog ibm.com/blogs/socialbusiness
– Read and engage with our bloggers

153

 Access Connect Online to complete your session surveys using any:
– Web or mobile browser
– Connect Online kiosk onsite

154

Acknowledgements and Disclaimers
Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither
intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information
contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise
related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or
its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and
performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you
will result in any specific sales, revenue growth or other results.

© Copyright IBM Corporation 2014. All rights reserved.
 U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
 IBM, the IBM logo, ibm.com, IBM Connections, IBM Notes Social Edition, IBM iNotes Social Edition, IBM Domino Social Edition are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a
trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be
registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml
Other company, product, or service names may be trademarks or service marks of others.

155

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Dernier

Dernier (20)

Notes de l'éditeur