System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean withFailover) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject, Boolean withFailover) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) at ftp_controls.Common_.Utility_.GetCustomRegPropertiesByUrl(String url) FTPOnline - SOA Offers Competitive Advantages
Welcome Guest!
Create Account | Login
Locator+ Code:

Search:
FTPOnline Channels Conferences Resources Hot Topics Partner Sites Magazines About FTP RSS 2.0 Feed

email article
printer friendly

SOA Offers Competitive Advantages
Using design patterns brings together programmer/analysts and enterprise architects to enhance your core services.
by Peter Varhol

Posted March 30, 2004

Enterprises from financial institutions to manufacturers are continuing to adopt technology with the same goals in mind—to make operations more efficient, take advantage of opportunities quickly, and make better decisions than their competitors. But while all of them can purchase the same systems and software, the real advantage comes from being able to apply these tools in innovative and productive ways. Creating an application infrastructure that pays dramatic dividends for the enterprise requires skills in determining how to architect applications that make effective use of core services.

The latest in a line of application infrastructures produced by industry analysts and strategic consultants is the service-oriented architecture(SOA). To many, it sounds like a collection of randomly assembled industry buzzwords. But the concept itself is straightforward. An SOA, at its heart, is a collection of services. A service is a software component that is well-defined, both from the standpoint of software and business function, and doesn't depend on the context or state of any application that calls it.

These services are typically implemented as Web services, accessible by applications through the Simple Object Access Protocol (SOAP), an XML form transmitted over HTTP. The advantage of using Web standards in an SOA is that the services can more easily adapt to different applications. Nothing in particular has to be done programmatically to the service, except to enable it to receive requests and transfer results using SOAP. So, in many cases, Web services are straightforward for an enterprise to build, and existing software can even be adapted to create new Web services.

How does an SOA give an enterprise a competitive advantage, and enable it to respond rapidly to business opportunities? Simply, it enables an enterprise to define the essential services it requires to serve its core business needs efficiently, and to adapt rapidly to changing business conditions. Once these core services are implemented, any application can call upon them to access and analyze data, build new business models, or provide data or features that make that application immediately pay back its investment.

This means that SOA is both a technical and a business strategy. It's a business strategy in that services deliver core value to the business. The services that comprise the SOA must be designed with an intimate understanding of the business, in order to determine what capabilities can be used across multiple applications. And they must be general enough to support multiple applications with different purposes, yet specific enough to provide real value to individual applications.

From a technology point of view, the challenge is in the architecture of the enterprise Web services. Because an SOA is fundamentally a flow and a relationship of service interfaces, designing the interfaces and their relationships requires an exceptional knowledge of Web technologies, business processes, and the technology platform underlying the services and the applications that employ them. The architect must understand not only how Web services are constructed, but how they are used by both existing applications and applications planned for the future.

Back to top










Java Pro | Visual Studio Magazine | Windows Server System Magazine
.NET Magazine | Enterprise Architect | XML & Web Services Magazine
VSLive! | Thunder Lizard Events | Discussions | Newsletters | FTPOnline Home