FAST ESP 5.3 for Windows is only available in 32 bit. However, the software can be installed on either 32 Bit or 64 Bit versions of the Windows operating system.
Consequently, prior to installing FAST ESP, you must install the 32 Bit versions of Java SE Runtime (JRE) and Java SE Development Kit (JDK): http://java.sun.com/javase/downloads/index.jsp.
Concepts: Information Architecture, Knowledge Management, Portals, Enterprise Search, Collaboration, Extranets, Intranets, Business Intelligence, Business Process Automation, ECM, Records Management, CRM, ERP, Mobile, Web
Approach: Project Management, Business Analysis, Strategy, Design, Development, Implementation
Technologies: Microsoft SharePoint, Office 365, Azure, SQL Server, Windows, HTML5, CSS, JavaScript, ASP.NET
Tuesday, March 31, 2009
Saturday, March 28, 2009
Links: MS SQL Server Reporting Services Add-In for MOSS
Here are the links for downloading:
Microsoft SQL Server 2008 Reporting Services Add-in for Microsoft SharePoint Technologies:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=200fd7b5-db7c-4b8c-a7dc-5efee6e19005
Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies:
http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en
Microsoft SQL Server 2008 Reporting Services Add-in for Microsoft SharePoint Technologies:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=200fd7b5-db7c-4b8c-a7dc-5efee6e19005
Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies:
http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en
Friday, March 27, 2009
Taking Cloud Platform Services Seriously
(Perspective from early 2009)
Based on conversations with colleagues and clients, I still don't think that the majority of long term, enterprise architecture strategies even consider Cloud Platform Services (referring to PAAS)...but I think this strategy may eventually become mainstream.
Despite the fact that the cost of hosting systems on-premises is reducing with time due to improved virtualization and management technologies, I think that in the not too distant future, there will be a point when the costs and risks of serving up certain types of applications in house will actually be greater than any compromise made by moving the same systems to a PAAS, cloud based platform.
The biggest drawbacks I see with PAAS are:
1. Perceived loss of security controls at the infrastructure level.
2. Perceived loss of control over infrastructure configurations.
3. Vendor lock-in.
4. Vendor price gouging.
5. WAN/Bandwidth limitations.
Despite the risks, I do think that visionaries are beginning to consider PAAS for certain aspects of their computing environment road map. I'm just not sure how much longer it will take before this approach is generally accepted and considered mainstream.
Based on conversations with colleagues and clients, I still don't think that the majority of long term, enterprise architecture strategies even consider Cloud Platform Services (referring to PAAS)...but I think this strategy may eventually become mainstream.
Despite the fact that the cost of hosting systems on-premises is reducing with time due to improved virtualization and management technologies, I think that in the not too distant future, there will be a point when the costs and risks of serving up certain types of applications in house will actually be greater than any compromise made by moving the same systems to a PAAS, cloud based platform.
The biggest drawbacks I see with PAAS are:
1. Perceived loss of security controls at the infrastructure level.
2. Perceived loss of control over infrastructure configurations.
3. Vendor lock-in.
4. Vendor price gouging.
5. WAN/Bandwidth limitations.
Despite the risks, I do think that visionaries are beginning to consider PAAS for certain aspects of their computing environment road map. I'm just not sure how much longer it will take before this approach is generally accepted and considered mainstream.
Where is the FAST Search Community?
I am truly excited about Microsoft's acquisition of FAST Search as well as the recent news about Microsoft's new Enterprise Search road map. Anyone who has deployed Microsoft Office SharePoint Server (MOSS) as an Enterprise Search solution or internet facing solution probably can appreciate all of the considerations that go into planning and implementing as well as some of the limitations that force you to think outside the box.
Prior to becoming proficient in MOSS Search, and prior to doing numerous Search Proof of Concepts on behalf of Microsoft, I spent quite a bit of time locked inside of a small office in the North End of Boston, researching, building and testing MOSS Search on a Microsoft VM. My primary sources of information included TechNet webcasts, blogs, Codeplex, MSDN articles, and the Microsoft Partner Support contacts. I've come to really appreciate the abundance of free flowing ideas and information that exists on the Web related to MOSS. The community is fantastic.
As I embark on new and exciting adventures working with FAST ESP, I am certain that the MOSS community will continue to contribute high quality information and will eventually expand to cover more topics related to FAST ESP. As of now, I don't see the same level of knowledge sharing occurring with FAST as I have seen with MOSS. I only hope that in response to Microsoft's acquisition of FAST as well as their reasonable product licensing model, that FAST will become more widely adopted and that a FAST Search community will flourish on the Web.
Prior to becoming proficient in MOSS Search, and prior to doing numerous Search Proof of Concepts on behalf of Microsoft, I spent quite a bit of time locked inside of a small office in the North End of Boston, researching, building and testing MOSS Search on a Microsoft VM. My primary sources of information included TechNet webcasts, blogs, Codeplex, MSDN articles, and the Microsoft Partner Support contacts. I've come to really appreciate the abundance of free flowing ideas and information that exists on the Web related to MOSS. The community is fantastic.
As I embark on new and exciting adventures working with FAST ESP, I am certain that the MOSS community will continue to contribute high quality information and will eventually expand to cover more topics related to FAST ESP. As of now, I don't see the same level of knowledge sharing occurring with FAST as I have seen with MOSS. I only hope that in response to Microsoft's acquisition of FAST as well as their reasonable product licensing model, that FAST will become more widely adopted and that a FAST Search community will flourish on the Web.
Tuesday, March 24, 2009
Firefox Automatic Logon
Description:
Configuring automatic logon for Firefox, for Microft Office SharePoint Server (MOSS) URLs
Solution:
1.
Open Firefox
2.
Address Bar: Type about:config
When prompted for a warning, click "I'll be careful I promise"
3.
About:config > Preference Name > network.automatic-ntlm-auth.trusted-uris
Right-click and "Modify"
4.
Entering String Value Dialog Box
Type the URL addresses of the SharePoint web applications (use comma to separate multiple addresses)
E.g. https://portal.domain.com, https://search.domain.com
Click "OK"
For information about more advanced Firefox/MOSS integration, read Mauro's recent blog post:
SharePoint/Office Integration with Firefox
Configuring automatic logon for Firefox, for Microft Office SharePoint Server (MOSS) URLs
Solution:
1.
Open Firefox
2.
Address Bar: Type about:config
When prompted for a warning, click "I'll be careful I promise"
3.
About:config > Preference Name > network.automatic-ntlm-auth.trusted-uris
Right-click and "Modify"
4.
Entering String Value Dialog Box
Type the URL addresses of the SharePoint web applications (use comma to separate multiple addresses)
E.g. https://portal.domain.com, https://search.domain.com
Click "OK"
For information about more advanced Firefox/MOSS integration, read Mauro's recent blog post:
SharePoint/Office Integration with Firefox
Tuesday, March 17, 2009
SQL Server: How to Change the Default Database Location
Description:
Instructions for changing the default Database locations.
Solution:
1. Open SQL Server Management Studio
2. Right Click on the SQL Server Instance node > Properties
3. Navigate to the "Database Settings" menu
4. Modify the "Database default locations"
5. Restart the following Windows Service:
SQL Server (MSSQLSERVER)
6. Create a new test database to verify that it is being created in the new, default location
Instructions for changing the default Database locations.
Solution:
1. Open SQL Server Management Studio
2. Right Click on the SQL Server Instance node > Properties
3. Navigate to the "Database Settings" menu
4. Modify the "Database default locations"
5. Restart the following Windows Service:
SQL Server (MSSQLSERVER)
6. Create a new test database to verify that it is being created in the new, default location
SharePoint 3.0: How to Move SQL Database Files, Transaction Log Files to Different Disk Location
Description:
Instructions for moving database files (mdf) and transaction log files (ldf) to a different disk drive on the database server, in a MOSS 2007 server farm.
Solution:
1. Perform the necessary capacity planning analyses and tasks to ensure that the future configuration will perform and scale for growth.
2. Schedule a maintenance window to allow for enough time to perform the configuration changes and test the SharePoint portal after the changes are complete. Communicate the maintenance window appropriately to the business users.
3. Create folders on the destination disk drive for storing the files. If the servers are physical, consider storing the transaction log files on a separate physical disk from the database files, to maximize performance. If the servers are virtual, understand the disk configuration of the underlying servers to ensure considerations including disk performance, contention, scalability, and snapshots.
In this example, D:\MSSQL_Data is the destination of data files, and D:\MSSQL_TLogs is the destination of transaction log files.
4. On the MOSS web front end servers and the Index server, stop the following Windows Services:
WWW Publishing Service
Windows SharePoint Administration
Windows SharePoint Search
Windows SharePoint Timer
Windows SharePoint Tracing
Windows SharePoint VSS Writer
Office SharePoint Search
5. For each database that is being moved, run the SQL Commands below to take the database offline
SQL Server Management Studio > New Query
--------------------
ALTER DATABASE MOSS_ContentDatabase SET OFFLINE;
GO
--------------------
6. Using Windows Explorer, physically copy the mdf and ldf files of the databases to their new location.
7. Run the SQL Commands below to update the physical location of the database files
SQL Server Management Studio > New Query
--------------------
USE master;
GO
ALTER DATABASE MOSS_ContentDatabaseMODIFY FILE (NAME = MOSS_ContentDatabase, FILENAME = 'D:\MSSQL_Data\MOSS_ContentDatabase.mdf');
GO
ALTER DATABASE MOSS_ContentDatabaseMODIFY FILE (NAME = MOSS_ContentDatabase_log, FILENAME = 'D:\MSSQL_TLogs\MOSS_ContentDatabase_log.ldf');
GO
ALTER DATABASE MOSS_ContentDatabase
SET ONLINE
GO
--------------------
8. Verify that the updated location has been properly set for each database by running the command below:
SQL Server Management Studio > New Query
--------------------
USE master;
GO
SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('MOSS_ContentDatabase');
GO
--------------------
Instructions for moving database files (mdf) and transaction log files (ldf) to a different disk drive on the database server, in a MOSS 2007 server farm.
Solution:
1. Perform the necessary capacity planning analyses and tasks to ensure that the future configuration will perform and scale for growth.
2. Schedule a maintenance window to allow for enough time to perform the configuration changes and test the SharePoint portal after the changes are complete. Communicate the maintenance window appropriately to the business users.
3. Create folders on the destination disk drive for storing the files. If the servers are physical, consider storing the transaction log files on a separate physical disk from the database files, to maximize performance. If the servers are virtual, understand the disk configuration of the underlying servers to ensure considerations including disk performance, contention, scalability, and snapshots.
In this example, D:\MSSQL_Data is the destination of data files, and D:\MSSQL_TLogs is the destination of transaction log files.
4. On the MOSS web front end servers and the Index server, stop the following Windows Services:
WWW Publishing Service
Windows SharePoint Administration
Windows SharePoint Search
Windows SharePoint Timer
Windows SharePoint Tracing
Windows SharePoint VSS Writer
Office SharePoint Search
5. For each database that is being moved, run the SQL Commands below to take the database offline
SQL Server Management Studio > New Query
--------------------
ALTER DATABASE MOSS_ContentDatabase SET OFFLINE;
GO
--------------------
6. Using Windows Explorer, physically copy the mdf and ldf files of the databases to their new location.
7. Run the SQL Commands below to update the physical location of the database files
SQL Server Management Studio > New Query
--------------------
USE master;
GO
ALTER DATABASE MOSS_ContentDatabaseMODIFY FILE (NAME = MOSS_ContentDatabase, FILENAME = 'D:\MSSQL_Data\MOSS_ContentDatabase.mdf');
GO
ALTER DATABASE MOSS_ContentDatabaseMODIFY FILE (NAME = MOSS_ContentDatabase_log, FILENAME = 'D:\MSSQL_TLogs\MOSS_ContentDatabase_log.ldf');
GO
ALTER DATABASE MOSS_ContentDatabase
SET ONLINE
GO
--------------------
8. Verify that the updated location has been properly set for each database by running the command below:
SQL Server Management Studio > New Query
--------------------
USE master;
GO
SELECT name, physical_name
FROM sys.master_files
WHERE database_id = DB_ID('MOSS_ContentDatabase');
GO
--------------------