Refn:
http://blogs.msdn.com/astebner/archive/2005/12/07/501466.aspx
Copied of the XSD file into the folder %ProgramFiles%\Microsoft Visual Studio 8\XML\Schemas
Thursday, May 28, 2009
Successfully implemented SharePoint (MOSS) BDC connection with Oracle
Refn:
http://www.sharepointassist.com/2009/01/08/business-data-catalog-bdc-how-to/
http://thorprojects.com/blog/archive/2008/08/02/moss-single-sign-on-setup-step-by-step.aspx
http://www.sharepointblogs.com/forums/p/14806/29753.aspx
Following high level steps:
I) Setup SSO.
II) Setup Oracle client.
III) Create and Install the Application Definition file.
I) Setup SSO - Main activities
1)Create the SSO service account -- This is the account that the service will run under. - For my prototype used the Sharepoint site collection secondary admin account.
2)Create the SSO groups -- These groups are used to control who has the ability to administer SSO (export the master key) and who has the ability to manage it (add/remove application definitions.) - For my prototype decided to used the "NT AUTHORITY\Authenticated Users" group so skipped this step.
3)Configure the SSO Service - Set SSO to start Automatic in Windows Services and get it to use the service account.
4)Configure SQL Server for SSO Database - Authorize the SSO service account to SQL server.
5)Manage SSO1 - Setup SSO in MOSS Administrative Tools-SharePoint 3.0 Central Administration - Operations - Security Configuration - Service Accounts
6)Manage SSO2 - Setup SSO details in MOSS including the groups and the database (SharePoint 3.0 Central Administration - Operations - Security Configuration - Manage settings for single sign-on link- Manage server settings). 7)Manage the encryption key -- Create the encryption key that will be used for protecting the username and password information on the system.
8)Create the enterprise application definitions used in SSO -- Define what initial applications SSO will be setup to manage passwords for.
(SharePoint 3.0 Central Administration - Operations - Security Configuration - Manage settings for enterprise application definitions).
NOTE: Please give the application name same as the one in your Application-Definition XML file.
Since we are planning to connect to Oracle keep the Field 1 and Field 2 to defaults of Username and Password respectively.
9)Manage the account information for an application definition file. As said above since I decided to go with "NT AUTHORITY\Authenticated Users" group, I entered the same.
Don’t change the default of “Update account information” and click on “Set”. Now you will be prompted to enter the Oracle database user-id and password. Please enter the same.
NOTE: When the connection happens to Oracle this Username and password will be used and whatever exists in the Application-Definition XML file will be ignored.
More later............
http://www.sharepointassist.com/2009/01/08/business-data-catalog-bdc-how-to/
http://thorprojects.com/blog/archive/2008/08/02/moss-single-sign-on-setup-step-by-step.aspx
http://www.sharepointblogs.com/forums/p/14806/29753.aspx
Following high level steps:
I) Setup SSO.
II) Setup Oracle client.
III) Create and Install the Application Definition file.
I) Setup SSO - Main activities
1)Create the SSO service account -- This is the account that the service will run under. - For my prototype used the Sharepoint site collection secondary admin account.
2)Create the SSO groups -- These groups are used to control who has the ability to administer SSO (export the master key) and who has the ability to manage it (add/remove application definitions.) - For my prototype decided to used the "NT AUTHORITY\Authenticated Users" group so skipped this step.
3)Configure the SSO Service - Set SSO to start Automatic in Windows Services and get it to use the service account.
4)Configure SQL Server for SSO Database - Authorize the SSO service account to SQL server.
5)Manage SSO1 - Setup SSO in MOSS Administrative Tools-SharePoint 3.0 Central Administration - Operations - Security Configuration - Service Accounts
6)Manage SSO2 - Setup SSO details in MOSS including the groups and the database (SharePoint 3.0 Central Administration - Operations - Security Configuration - Manage settings for single sign-on link- Manage server settings). 7)Manage the encryption key -- Create the encryption key that will be used for protecting the username and password information on the system.
8)Create the enterprise application definitions used in SSO -- Define what initial applications SSO will be setup to manage passwords for.
(SharePoint 3.0 Central Administration - Operations - Security Configuration - Manage settings for enterprise application definitions).
NOTE: Please give the application name same as the one in your Application-Definition XML file.
Since we are planning to connect to Oracle keep the Field 1 and Field 2 to defaults of Username and Password respectively.
9)Manage the account information for an application definition file. As said above since I decided to go with "NT AUTHORITY\Authenticated Users" group, I entered the same.
Don’t change the default of “Update account information” and click on “Set”. Now you will be prompted to enter the Oracle database user-id and password. Please enter the same.
NOTE: When the connection happens to Oracle this Username and password will be used and whatever exists in the Application-Definition XML file will be ignored.
More later............
Monday, March 30, 2009
South Indian Restaurants to try in Central Jersey
South Indian Restaurants to try in Central Jersey
1) Paradise - Oak Tree Road - Liquor Locker Complex
Following are Chettinad Sytle --
2) Anjappar http://www.anjapparusa.com/
3) KaraiKudi 732-516-0020
1671 Oak Tree Road
1) Paradise - Oak Tree Road - Liquor Locker Complex
Following are Chettinad Sytle --
2) Anjappar http://www.anjapparusa.com/
3) KaraiKudi 732-516-0020
1671 Oak Tree Road
Friday, March 27, 2009
SharePoint or MOSS list backup using template mechanism
To quickly urgently easily backup a SharePoint / MOSS list just use "save as template" and
check "Include Content". You can restore by creating a new list from this template anytime.
check "Include Content". You can restore by creating a new list from this template anytime.
Access Error Trapping OnError macro and send email notification without manual intervention using Sharepoint
Access 2007 has OnError macro.
On error we just add the record to SharePoint linked list in Access.
Alerts are setup on this SharePoint list which generate automatic email.
On error we just add the record to SharePoint linked list in Access.
Alerts are setup on this SharePoint list which generate automatic email.
Sunday, March 15, 2009
Highlight rows in SharePoint or MOSS lists / Highlight the pastdue or overdue tasks
Highlight rows in SharePoint or MOSS lists
Great article
http://pathtosharepoint.wordpress.com/2009/02/26/highlight-rows-in-sharepoint-lists/
This we used to highlight the pastdue or overdue tasks.
Great article
http://pathtosharepoint.wordpress.com/2009/02/26/highlight-rows-in-sharepoint-lists/
This we used to highlight the pastdue or overdue tasks.
Friday, August 29, 2008
MOSS TAM PD (Tivoli Access Manager) Integration - Part (I)
1) Decide on the TAM site URL (https://www.collab.abc.net/).
2) Register this as domain name.
3) Since this is a secure site get a certificate.
4) If this is an external site then get the firewall configured (NAT).
5) If this is an external site then get the firewall holes opened.
6) Get the CSS service configured.
7) On MOSS create a secure FBA site with SQLMembership provider (https://dev.tammossint.abc/)
8) Register this MOSS site domain name.
9) Now get a certificate for this secure MOSS site.
10) On MOSS site create AAM (Alternate Access Mapping) to the TAM site (https://www.collab.abc.net/).
11) Request a virtual host on TAM to the MOSS site (https://dev.tammossint.abc/).
The virtual host methodology is preferred over junction to gid rid of AJAX errors.
12) Copy the “pics” directory from TAM’s Webseal to the root of the MOSS site (https://dev.tammossint.abc/).
2) Register this as domain name.
3) Since this is a secure site get a certificate.
4) If this is an external site then get the firewall configured (NAT).
5) If this is an external site then get the firewall holes opened.
6) Get the CSS service configured.
7) On MOSS create a secure FBA site with SQLMembership provider (https://dev.tammossint.abc/)
8) Register this MOSS site domain name.
9) Now get a certificate for this secure MOSS site.
10) On MOSS site create AAM (Alternate Access Mapping) to the TAM site (https://www.collab.abc.net/).
11) Request a virtual host on TAM to the MOSS site (https://dev.tammossint.abc/).
The virtual host methodology is preferred over junction to gid rid of AJAX errors.
12) Copy the “pics” directory from TAM’s Webseal to the root of the MOSS site (https://dev.tammossint.abc/).
Subscribe to:
Posts (Atom)
