Microsoft Solution for Internet Business
Operations Guide
On This Page
AbstractThis guide provides solution operations for Microsoft® Solution for Internet Business (MSIB) version 2.0. It focuses on ongoing operational activities relating to your MSIB deployment. It also discusses data lifecycles and best practices in managing MSIB databases and data files. IntroductionMicrosoft® Solution for Internet Business (MSIB) is an integrated solution that is built using high quality Microsoft® .NET-based Windows Server System products to provide end-to-end processes and features for sophisticated Internet sites. MSIB integrates a number of different Microsoft products into a solution that enables the development and management of enterprise Web sites for Internet presence and electronic commerce. These products include:
MCMS and Commerce Server are the primary, front-line server products involved in the solution. SQL Server provides the underlying database services for both MCMS and Commerce Server. When deploying MSIB, ISA Server can be used to achieve the required management, security functionality, and caching for your site. The Adventure Works sample site included with MSIB provides a common starting point for corporate Web sites. Exact Web site requirements and design preferences vary from company to company, and so experienced consultants can begin with the MSIB Web site to create a customized solution for their client. This document describes the Microsoft Operational Framework (MOF) and the best practices involved with the operation activities and troubleshooting of database problems. It also discusses managing the databases that are a part of MSIB, including security, backup, and restore. Reader GuidanceSystem administrators, IT professionals, and developers should read this document. Anyone reading this document should also read the product documentation for Commerce Server 2002 and MCMS 2002. Each product documentation set contains specific and detailed information about the corresponding products. Microsoft Operations Framework Reference ModelThe operational reference model for MSIB uses the MOF and the related process model, both of which are reviewed in this section. This section also describes the operations infrastructure, reporting, change management, and people skills required for operating an MSIB site. Microsoft Operations FrameworkMOF is a collection of best practices, principles, and models. It provides comprehensive technical guidance for achieving mission-critical production system reliability, availability, supportability, and manageability for solutions and services built on Microsoft products and technologies. Thus, MOF is the reference model for this guide. From a documentation standpoint, the guide fits within the MSIB Solutions Operations Guide level of the documentation as defined by MOF. MOF provides the fundamentals of operations methodology and framework for IT operations. Product operations guides provide detailed operations information specific to the server products. This guide provides operations management guidance specific to the solution platform made up of the base server products. These three types of documents should then be customized based on the specific deployment and operating environment to create an Operations Guide specific to the customer. For a comprehensive introduction to the MOF, see the document Microsoft Operations Framework Executive Overview on the Microsoft Business Web site at http://go.microsoft.com/fwlink/?LinkId=10428. Product Operations GuidesMSIB integrates multiple Microsoft Enterprise Servers. The product operations guides (POGs) for each of these Enterprise Servers provide guidance on how to operate these servers. MSIB customers should reference these POGs for details of granular operations specific to these servers. The following discusses the POGs currently available: Windows 2000 Operations Guide The Windows 2000 Operations Guide series draws from best practice guidelines documented in the Information Technology Infrastructure Library (ITIL) from the Central Computer and Telecommunications Agency (CCTA) and from years of IT operations experience by Accenture, Avanade, HP Services, Hewlett-Packard Company, Lucent Technologies/NetworkCare Professional Services, Compuware Corporation, Unisys Corporation, Microsoft Consulting Services (MCS), and the Microsoft Information Technology Group (ITG). The Windows 2000 Operations Guide series contains a comprehensive selection of operations guides covering such topics as capacity management, configuration management, storage management, and system administration. The series is located on the Microsoft Technet Web site at http://go.microsoft.com/fwlink/?LinkId=10448. Windows 2000 Security Operations Guide The Security Operations Guide for Windows 2000 Server is in a different location than the above series. It is located on the Microsoft Technet Web site at http://go.microsoft.com/fwlink/?LinkId=10449. SQL Server 2000 Operations Guide To manage a SQL Server in a day-to-day environment, you need to perform a wide variety of procedures, including server monitoring, backup, verification of scheduled events, capacity planning, and developer and end-user support. This guide includes instructions for these procedures along with steps for dealing with unresolved issues in a timely manner. The SQL Server 2000 Operations Guide is located on the Microsoft TechNet Web site at http://go.microsoft.com/fwlink/?LinkId=10447. Microsoft Operations Manager Operations Guide The Microsoft Operations Manager 2000 (MOM) Operations Guide includes guidance and recommended best practices for maintaining and running MOM in an existing IT infrastructure. This guidance is based on the three supported MOM deployment architectures:
The guide contains instructions for deploying agents across multiple domains, across firewalls, across slow links, and in workgroups. Detailed instructions are provided for maintaining each of the MOM components: MOM database, Database Access Server/Consolidator-Agent Manager (DCAM), agents, and reporting. This guide also includes an overview of the security architecture that is implemented by MOM, and it includes component-based security guidance. Finally, the information in this guide is organized according to the MOF process model. The MOM 2000 Operations Guide is located at Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=10436. Operations Infrastructure Organizations that deploy an e-commerce solution must keep the deployment functioning 24 hours a day, seven days a week. It has become increasingly common for enterprise application integration to have a similar availability requirement. This document outlines the administrative tasks a system administrator must perform to keep a Web site based on MSIB running on a continual basis. Also discussed in this document are important concepts and common administrative issues about which system administrators must be aware. The major areas of administration and management related to MSIB and the tools used to administer those areas are:
People Skills Required Different business disciplines are tasked with undertaking various roles in managing an MSIB deployment. Each of these disciplines is discussed in the following topics. Business managers Business managers add, change, and delete site content using Commerce Server Business Desk in the development environment. These users also define business rules for processing orders and for other business processes. Business managers work with the following types of content:
Site developers Site developers add, change, or delete site content using Microsoft® Visual Studio® .NET and other tools in the development environment. These users also develop XML documents. Site developers work with the following types of content:
Template designers Site designers and developers build the site structure and templates. Template designers, using page templates, determine where to place personalized content information on a page, the number of links to provide, and how to display those links. They create navigation server controls that can be reused for site navigation in multiple templates without copy and pasting code directly in the template. One designer can create the server controls and another can use them. Testers Testers test newly developed content in the test/staging environment, prior to deployment, in an effort to identify any potential problems that arise from the incorporation of the new content and new functionalities. System administrators System administrators administer change requests from both business managers and site developers by using Commerce Server Manager resources or Business Desk modules. System administrators are responsible for the following:
Change Management Model Change management for this solution should be done through a well-defined change management process such as the following:
The following table lists the activities usually carried out in this process.
MOM and MOM Management PacksMSIB uses MOM 2000 and various management packs for monitoring and operations management. MOM 2000 delivers enterprise-class operations management by providing comprehensive event management, proactive monitoring and alerting, reporting, and trend analysis. The Application Management Pack — the extensive product support knowledge base included in MOM — is the key to helping reduce the day-to-day support costs associated with running applications and services in a Windows–based IT infrastructure. As a key part of any successful Windows 2000 Server or Windows Server System deployment, MOM 2000 management packs provide the operational knowledge necessary to keep mission-critical applications and systems running smoothly. MOM database sizing MOM collects and stores data in a SQL Server database. The default database installed with MOM is named OnePoint. After you have installed MOM, you should grow your OnePoint database to 5 GB in database size and 1 GB in transaction log size. This will prevent the OnePoint database from filling up. MOM performs database grooming, so in a typical scenario, the database size will peak at a certain size as data is collected and groomed continuously. For details about MOM database sizing information, see Microsoft Operations Manager: Performance and Sizing at http://go.microsoft.com/fwlink/?LinkId=10606. The MOM sizing document located at this URL contains calculators for predicting the database size required to support your MOM database collection. MOM report generation Producing reports and managing nodes at the same time on the same computer consumes a large amount of CPU and disk resources. There is an estimated 30 percent CPU overhead for report generation, with a disk utilization of 100 percent, and average disk queue lengths of 12 or more during this function. Therefore, you should not attempt to generate reports while managing nodes from the central computer. As a best practice, use a separate reporting system and a duplicate database if possible, from which to generate reports. Alternatively, if you do not have a separate reporting system, you can schedule reports to run at an appropriate time. Bear in mind that generating more than two reports at once will overtax most systems. MOM Base Management Pack and MOM Application Management Pack The MOM Base Management Pack contains the rules and knowledge base for the following:
The Application Management Pack contains the rules and knowledge base for the following:
It is recommended that you use the above-listed management packs to monitor your servers. However, your deployment will function correctly without any of the management packs. You should only install specific management packs that match the servers you deploy. For example, installing Exchange Server management pack does not make your deployment any more manageable if you do not have an Exchange Server deployment. The performance monitoring network overhead for MOM is small, so performance and network overhead should not be a key concern in your decision to deploy application management packs. Available Third-Party Management Packs MOM is extensible by using management packs provided by third-party software and hardware vendors. Some of the management packs that you may want to consider deploying are listed below. Dell computer Dell OpenManage Connections enables system administrators to easily manage Dell servers from MOM. The following is a list of links to more information about these management packs:
HP/Compaq
NetIQ
MSIB Management Pack The MSIB MOM Management Pack is available on the MSIB CD at Tools\Management Pack\ MSIB20.akm. To install the MSIB MOM Management Pack
The MSIB MOM Management Pack is now installed. Setting up alert e-mail notification In order for the MISB Management Pack e-mail alert to function, you must do the following setup steps, in the order shown:
To set up e-mail configuration
To set up your e-mail notification groups
To associate your notification group with your alert processing rules
MSIB MOM Management Pack features Following is a list of what you can do with the MSIB MOM Management Pack:
To perform an HTTP Ping operation on the MSIB site URL
Reacting to server failure MOM can send out notification when a service fails. When this occurs, you must remove the defective server from your deployment using the wlbs command. To remove a defective Web server or ISA Server from an NLB cluster
To add the server back into the cluster
The server is added back into the cluster. Monitoring your MSIB site externally MOM monitors your deployment from the internal network. To monitor your deployment from an external network, you can subscribe to monitoring services from service providers of your choice. These services can also monitor and track response characteristics for your deployment from different Internet access points from different countries. External monitoring services compliment MOM monitoring and should be considered as an integral part of your monitoring infrastructure. Monitoring the System You can use MOM and MOM application management packs to help monitor your MSIB application. MOM identifies key performance counters and Windows NT event logs vital to your deployment, and automates the collection of these Windows NT performance counters. This section explains the counters that pertain to the MSIB solution, and how they indicate correct or degrading system behavior. Service monitoring enables the operations staff to observe the health of a service in real time. Accurate monitoring of a system is a complex process within a distributed process environment. With this in mind, the following list is an example of system components that are typically monitored to ensure that the service remains available:
Knowing the current health of a service or determining that a service outage may occur is of little benefit unless the operations staff is able to take pre-emptive action, or at the very least, to notify the appropriate group that a specific type of proactive or corrective action needs to occur. When combined and implemented properly, this service management function provides the critical capability to ensure that service levels are always in a state of compliance. Event Log The Event Log is the main error message repository for the Windows Server System products used in MSIB. The following table shows the events that you should monitor when running an MSIB site.
Performance Monitor counters Use the Performance Monitor to measure the performance of your own computer or other computers on a network. The Performance Monitor uses a series of counters that track data, such as the number of processes waiting for disk time, the number of network packets transmitted per second, and the percentage of processor utilization. With this data, you can create charts, set alerts, and format reports that enable you to gauge and tune system performance. Data can be displayed as it is collected, stored in log files for later use and comparison, or both. For a full discussion about the use of performance monitor counters, see the document Overview of Performance Monitoring on the Microsoft TechNet Web site at http://go.microsoft.com/fwlink/?LinkId=10566. The following are options for running the Performance Monitor:
Relevant performance counters can be categorized into the following groups:
Active Server Pages The following table shows the Active Server Pages (ASP) performance counters that are of interest in the context of MSIB, and observations related to each counter.
Network segment The following table shows the network segment performance counters that are of interest in the context of MSIB, and observations related to each counter.
Process, Inetinfo instance The following table shows the process performance counters that are of interest in the context of MSIB, and observations related to each counter. The number of bytes, and especially changes to this number of bytes, associated with the Inetinfo process are of particular interest.
Memory The following table shows the memory performance counters that are of interest in the context of MSIB, and observations related to each counter.
Physical disk The following table shows the physical disk performance counters that are of interest in the context of MSIB, and observations related to each counter.
SQL Server The following table shows the SQL Server segment performance counters that are of interest in the context of MSIB, and observations related to each counter.
Commerce Server The following table shows Commerce Server performance counters that are of interest in the context of MSIB, and observations related to each counter.
The Catalog Queries per Second counter is the rate of queries per second through the CS2002: Marketing and Catalog object on a server. These queries include all category and product related queries, as well as free-text search. You can reduce queries made to the Product Catalog System by using a product cache or search cache to improve performance. Free-text search can also be tracked with the Microsoft Search queries/second counter. The catalog query rate is the uncached rate. If this rate is high, then the application code should be changed to take advantage of a local caching mechanism, such as the LRUCache counter. Note: For an extensive list of performance counters available in Commerce Server, see Commerce Server 2002 Help. Message Queuing The following table shows Message Queuing (also known as MSMQ) performance counters that are of interest in the context of MSIB, and observations related to each counter.
System The following table shows system performance counters that are of interest in the context of MSIB, and observations related to each counter.
Web service The following table shows the Web service performance counters that are of interest in the context of MSIB, and observations related to each counter.
Operational ActivitiesThis section describes the various operational activities associated with running an MSIB site. These activities are divided into the following categories:
MSIB Startup ProcedureThis section describes the procedures you perform to get your MSIB site running. In order to get all of the servers running for the MSIB site, the servers must be started in the following sequence:
To start and check the Domain Controllers
To start the primary and secondary servers running SQL Server and SQL Server cluster check
For more information about installing SQL Server 2000, see the "Installing SQL Server" section in the .NET Enterprise Servers documentation on the Microsoft MSDN Web site located at http://go.microsoft.com/fwlink/?LinkId=10567. To run the Windows Clustering check
To run database connectivity check
To start and check the Tier 2 ISA Servers
To start and check the Web servers
To start and check the Search servers
To start and check the SMTP Relay servers
To start and check MOM/Application Center server
For more information, see MOM and Application Center 2000 Help. To start and check the Business Desk server
To start and check the Tier 1 ISA server
This functionality check should include browsing catalogs, performing searches, and testing all of the major feature areas of the site. MCMS Content Creation and WorkflowEvery MCMS Web page has a template associated with it. These templates are created by template designers. In MCMS 2002, this is done using Visual Studio .NET. After the template designer finalizes the template design, the content publishing process begins when an author — any content creator in your organization — uses one of the following tools to create a page:
After an editor approves the page, a moderator for the channel to which the page will be posted, reviews and approves the publishing schedule before publication. Moderators ensure that the channels contain relevant content. After approval, the page content is published on the site according to the scheduled start and expiration dates for the posting. Each page contains its own publishing schedule that includes start and expiration dates, and identifies the channels on which the page will be published. When a subscriber navigates to a page in a channel, MCMS dynamically generates the page. Channels are used to store, organize, and manage access to content. The following summarizes the steps to publish MCMS content to a production site:
For more information about the MCMS workflow, see "Publishing Workflow" in MCMS 2002 Help. Catalog creation and modification By default, MSIB uses the Commerce Server Product Catalog System as the primary tool for storing and maintaining product data. Business managers use the associated catalog modules in Commerce Server Business Desk to create and modify product data. These modules can also be used to import catalog data from other data sources and to export catalog data for use in other applications. Business managers can update product information, such as the product price, and then publish the changes to the Web site. The catalog modules in Business Desk enable business managers to easily find products by performing a property search or a free-text search. For more information, see "Business Desk Catalogs" in Commerce Server 2002 Help. Developers can also access the Commerce Server Product Catalog System programmatically, using the following Commerce Server objects: CatalogManager, CatalogSets, CatalogToVendorAssociation, Category, Product, and ProductCatalog. For more information about programming with these objects, see "Product Catalog Programming Concepts" and "COM Object Reference" in Commerce Server 2002 Help. Report analysis Business reporting is an important aspect of analyzing and altering business practices to optimize profitability. Business managers use the Reports module in Commerce Server Business Desk to run both dynamic and static reports. The system administrator must perform several tasks before a business manager can run and view reports. For example, system administrators must import data into the Data Warehouse and run the report preparation process on a regular basis. This ensures that the reports run by business managers are using the most up-to-date data. Business managers can run Commerce Server reports to identify the top-selling products by units sold and by total sales, and to identify the top-selling categories by units sold and by total sales. The results of this analysis can be used, for example, to discount products that are not selling well, or to promote accessories for products that are selling well. In addition, developers can use this information to customize the Web site to suggest up-sells and intelligent cross-sells to prospective buyers. In order to run report analysis, Web log files must be copied from the Web tier to the offline Data Warehouse tier to be imported. This operation should be carried out daily. For more information about data warehousing, see "Data Warehouse" in Commerce Server 2002 Help. Change Configuration SettingsThis section describes aspects of MSIB that are likely to evolve over time, changing periodically during the life cycle of an MSIB site. Detailed information about changing, maintaining, and backing up configuration settings is provided for Web data, Windows accounts, and Commerce Server SQL connection strings. Web data Use Commerce Server Site Packager to initially deploy the MSIB Web site. To update the content of the MSIB Web site, use a method that is appropriate for the type of component underlying the content that you are updating. The following table shows the tool(s) appropriate for updating the various types of components that contribute to the content of the MSIB Web site.
Windows accounts Commerce Server installed Windows Services uses local and Domain User accounts. It is important to ensure that each of the following Commerce Server Windows Services is running under a valid local or Domain User account:
Commerce Server Connection StringsMSIB uses several Commerce Server connection strings. These connection strings are managed by the underlying .NET Enterprise Servers and accessed through their APIs. The connection strings are managed using Commerce Server Manager. These connection strings are global to the site; if you make any changes to them, you will need to stop and restart the service in order for those changes to take effect. Best practice requires that you do not use sa (the sa sysadmin user) in any of the connection strings used to connect to the following databases:
The following table shows the connection strings for each Commerce Server site resource.
Regular Database MaintenanceThe dbcc checkdb SQL query should be run on all databases each night to reduce the chances of running with corrupted databases. It is recommend that you run the dbcc checkdb query once a week on all databases. To run dbcc checkdb
The dbcc checkdb query runs. The following is a list of the databases against which this query should be run:
DBCC checkdb recommendations In Microsoft SQL Server 2000, you can run the dbcc checkdb query while the database is in use. However, dbcc checkdb places a schema lock on the table that it is currently checking, to prevent metadata changes while the table is being checked, thus allowing data management language (DML) statements but not any data definition language (DDL) statements on the tables being checked. This change provides greater flexibility as to when you can run dbcc checkdb because dbcc checkdb does not completely deny system usage to the users. The dbcc checkdb query is a CPU-intensive and disk-intensive operation. Each data page that requires checking must first be read from disk into memory. In addition, dbcc checkdb uses tempdb for sorting operations. If transactions are being performed while dbcc checkdb is running, the transaction log file continues to grow because the DBCC command blocks log truncation until it has finished reading the log file. It is recommended that you run dbcc checkdb during hours when the load is light on the server. If the utility is run during heavy peak usage time, expect a performance hit on the transaction throughput as well as dbcc checkdb completion time. Recommendations for good DBCC performance
Service Packs and Hotfixes MSIB, together with the service packs, hotfixes, and component software applications listed in the MSIB Deployment Overview is a tested, supported solution. To see if new service packs, hotfixes, or updated releases of component software applications are available and have been tested with MSIB, go to http://go.microsoft.com/fwlink/?LinkId=10601 and search for Microsoft Knowledge Base article 329331. Microsoft and third-party software vendors provide different tools for checking software updates and security fixes. One example is the Microsoft Base Security Analyzer. You should weigh the benefits of applying software updates recommended by these tools against the risk of instability that a particular hotfix might introduce. Never automatically accept and install all updates the tools recommend, as the update might have an unexpected effect on your servers. Review each software update carefully and apply updates only on servers that require a particular update. Once the software updates have been applied, thoroughly check all features of your site and stress test the updated platform to ensure that the software updates do not create problems or unwanted side effects. Important: It is recommended that you test on your test platform and not on your production platform. Your test platform should be architecturally the same as your production platform. This ensures that your test cases cover your intended production deployment scenario. Tuning the SystemWhen considering performance, it is important to first determine where performance is needed most. Because tuning techniques vary for the different .NET Enterprise Servers used in MSIB, they are each discussed separately in this section:
Microsoft Commerce Server When using an MSIB site, users generally have the most direct contact with Commerce Server. In the Commerce Server portion of MSIB, performance tuning should focus on the front line Web servers that provide cataloging and dynamic content generation. Another tuning possibility involves moving resource-intensive processing onto the Business Desk computer. This enables the front line Web servers to remain free, providing quick responses and better support to a higher number of concurrent users. The Microsoft Application Center Test (ACT) tool is a simulation tool designed to stress test Web servers and analyze performance and scalability problems with Web applications, including ASP pages and the components they use. The ACT tool simulates a large group of users by opening multiple connections to the server and rapidly sending HTTP requests. The ACT tool supports several different authentication schemes, and it supports the Secure Sockets Layer (SSL) protocol, making it ideal for testing personalized and secure sites. Although long-duration and high-load stress testing is the main purpose of the ACT tool, the ACT programmable Dynamic Tests are also useful for functional testing. The ACT tool is compatible with all Web servers and Web applications that adhere to the HTTP protocol. For information about the ACT tool, For information about the ACT tool, go to the Microsoft Application Center Web site at http://go.microsoft.com/fwlink/?LinkId=10570. Microsoft Content Management Server In MCMS, throughput is a key measurement of performance, measuring items such as pages per second, ASPs per second, and gets per second. A further measurement is the number of concurrent users on the site. Some of the areas to fine-tune performance on a Web site include:
Running the Cleanup UtilityYou should run the cleanup utility periodically to delete orphan profiles and postings. To run this utility, make sure that the permissions are set to full rights for Everyone. The log file for the cleanup utility is located at <drive:>\Inetpub\WWWroot\MSIB20\WBCExtensions\CleanupUtilLog.htm. To run the cleanup utility
The utility runs and removes the orphaned profiles. Security Scan ToolsIt is recommended that you do routine security audits and security scans. Auditing and scanning can happen internally — inside the firewall boundary, or externally — outside the firewall. Internal security audits and scans ensure that security settings are correctly set and stay intact over time, and that security patches are correctly propagated to the right servers. For example, file access permissions on files such as the machine.config file that contain security data is secured and kept secured, and strong passwords are enforced for all accounts. External security audits and scans ensure that exposed services are protected and not vulnerable to brute force attacks. This also ensures that no unnecessary ports are opened. Use these tools with care to avoid misuse and unnecessary load on your servers. Commercial and public domain security scanning tools are readily available to help you detect common security vulnerabilities. Some of these tools enable you to retrieve an updated list of vulnerabilities to protect your servers from the latest breaches. Security scan tools include, but are not limited to, NetIQs Security Analyzer, Security Auditing Tool for Analyzing Networks (SATAN), and various port scanners. Security in OperationsThere are a number of different aspects involved in the security of an MSIB site. They can be categorized as follows:
Certificates It is important that you keep track of the expiration dates of your certificates; best practice requires renewing certificates in advance. For more information about certificates, see the MSDN® Online Library at the Microsoft MSDN Web site at http://go.microsoft.com/fwlink/?LinkId=10624 and search for the topic "Certificate Services and Components." MSIB passwords If you change passwords for Windows NT domain user accounts, you are required to change the corresponding passwords on all the related servers. The following table lists the accounts that are associated with your MSIB deployment.
After changing passwords for your service accounts on the Microsoft® Active Directory® server, you must propagate the new passwords to the services running on the individual servers. The following table shows you where and how to update these passwords:
In addition to setting strong passwords for each of these accounts, you should define your corporate policies for maintaining these passwords. For example, how often you want to change these passwords, when, and during what event do you want to change them. For information about creating accounts, see the "Creating the Necessary Accounts on the First Domain Controller/DNS Server" in MSIB Installing Domain Controllers Guide. For information about how to set up and enable strong passwords, go to "Implementing Guidelines for Strong Passwords" on the Microsoft Windows NT Server Web site at http://go.microsoft.com/fwlink/?LinkId=10572. For information about enabling strong password functionality in Windows 2000, go to the Microsoft Product Support Services Web site at http://go.microsoft.com/fwlink/?LinkId=10573. For information about setting up password policies, password management and creating security guidelines for your company, go to the Microsoft TechNet Web site at http://go.microsoft.com/fwlink/?LinkId=10628. For comprehensive coverage of Microsoft security recommendations, best practices, and security design, go to the Microsoft Technet Web site at http://go.microsoft.com/fwlink/?LinkId=10625. MCMS security In order to ensure security on an MCMS site, you should do the following:
Some organizations may have more stringent security guidelines, so you should make sure to consult your IT staff prior to deploying a site. Providing access to Commerce Server resources In order for Commerce Server Business Desk users and administrators to access resources, such as the product catalog, they must have permissions to access the SQL Server database that corresponds to the resource. A user should have a SQL Server login name that is linked to a SQL Server user that has the db_owner database role. Alternatively, to provide greater detail, you can assign the user to the db_ddladmin, db_datareader, and db_datawriter roles. To check the SQL Server roles assigned to a login name for a resource
If the login name you specified does not appear in the list of database users, you can add a new SQL Server user. To add a new SQL Server user for a resource database
Securing database archive
|
