SharePoint Study Notes-exercise series-70-exercise analysis-(Q141-Q143)

Question 141
You are planning an upgrade to a Sharepoint 2010 application. You have the following requirements:
. Modify an existing workflow to include a new code activity.
. Ensure running instances of the workflow continue to work.
. Ensure new instances of the workflow include the modifications.
You need to plan the upgrade the application to meet these requirements. After the workflow code is modified, what shoshould your plan specify?
A. Deploying the code to the Global Assembly Cache (GAC) and deactivating the workflow feature.
B. incrementing the version of the workflow assembly, deploying to the GAC, and activating the workflow feature.
C. incrementing the version of the workflow assembly, deploying to the GAC, deactivating the workflow feature, and then activating the workflow feature.
D. incrementing the version of the workflow assembly, deploying to the GAC, and modifying the appropriate workflow. xml file to reference the new version.

Resolution:
You plan to upgrade a Sharepoint application to meet the following requirements:
Requirement 1. Add a new code activity for an existing workflow
Requirement 2. Ensure that the used workflow instance continues to run normally
Requirement 3. Ensure that the new workflow instance contains the modifications in requirement 1
What should you do to ensure that the upgrade meets the above requirements?
Because this question requires "ensure that the used workflow instance continues to run normally", you must deploy the new workflow assembly. That is, "incrementing the version of the workflow assembly, deploying to the GAC", which is described in the section before option B .C. D. Option A is excluded because the Assembly (compiled code) instead of the Code is deployed in the GAC.
We know that each workflow has a workflow definition (workflow. XML) file. This XML definition specifies the identity of the actual workflow assembly, the classes in the Assembly, and the location of any workflow form that the workflow must run. Option B .C does not define the workflow of the original job (workflow. XML) file, so that it does not meet requirement 1, that is, you must add a new code activity for an existing workflow. Only option D is available. By modifying the workflow. xml file, you can point the ID of the workflow assembly on which the existing workflow depends to the newly created workflow Assembly to meet the requirements of this question.
Therefore, select D as the answer to this question.

Reference
Http://msdn.microsoft.com/zh-cn/library/ms434426 (V = office.14). aspx
Http://msdn.microsoft.com/en-us/library/ms414556 (V = office.14). aspx
Http://social.msdn.microsoft.com/Forums/en-US/6034c5d5-86b2-45dc-a9cc-4ebf4930668e/how-to-increment-the-version-of-my-workflow

 

Question 142
You have a Sharepoint 2010 application deployed in production. the application has a list with a single longrunning workflow named version. you design a new version of the workflow named versionb. you have the following requirements:
. Existing instances of version must continue to run until completed.
. Versionb must always be instantiated in the future.
. Version A must no longer be instantiated.
You need to design the solution to meet the requirements. Which approach shocould you recommend?
A. Disable the start this workflow when a new item is created property in the Start options of Version.
B. Disable the start this workflow when a new item is created property in the Start options of versionb.
C. Set the no new instances property in the remove workflows settings of Version.
D. Set the optionally limit the number of versions to retain property in the versioning settings of the list.

Resolution:
You have developed and deployed a sharepoint2010 application in the production environment. This application contains a workflow that runs a list for a long time. The current version of this workflow is a. You are going to develop a new version of B, and meet the following requirements:
Requirement 1. The running version A must continue until the execution is completed.
Requirement 2. After the upgrade, the new workflow instance must be created based on Version B.
Requirement 3. After Version B takes effect, no new workflow instance is created based on version.
How do you meet the above requirements?
We know that you can add workflows by associating workflows with lists, document libraries, content types, or websites. You can remove a workflow by unassociating a workflow with a list, document library, content type, or website. Alternatively, you can stop a new workflow instance from starting, but still allow all running workflow instances to complete. This is exactly what needs to be done in this question.
The following describes how to remove a workflow association from the list or Document Library:
Remove workflow Association from list or document library
1. Verify that you have the following management creden:
O you must be a member of the site owners group on the configured SharePoint site.
2. Find the list or library from which you want to remove the workflow.
3. Perform one of the following operations:
O For the list, click "list" on the "List Tools" tab ".
O in the "Settings" group, click "list Settings ".
O For the database, click "Database" on the "database tools" tab ".
O in the "Settings" group, click "database Settings ".
4. On the "List Settings" or "database Settings" page, click "workflow Settings" in the "permissions and management" section ".
5. On the "workflow Settings" page, click "delete Workflow ".
6. On the "delete Workflow" Page, locate the workflow to be removed and select from the following options:
O select "no new instances" to prevent new instances of this workflow from running, but still allow running instances to complete. [This is the result required by this question. Only option C uses this attribute settings. Therefore, option C is the answer to this question]
After all running workflows are completed, you can return to this page to completely remove workflow associations.
O select "Remove" to prevent new instances of the workflow from running and remove all instances of the workflow. This option removes running instances.
7. Click OK ".
Option A. B Closes the automatic workflow. It does not have much to do with the requirements of this question.
Option D applies to version saving restrictions for list items (mainly document versions in the Document Library), and has nothing to do with the workflow of this question. Therefore, it should be excluded.
Therefore, C is the answer to this question.

Reference
Http://technet.microsoft.com/zh-cn/library/ee662537 (V = office.14). aspx
Http://technet.microsoft.com/zh-cn/library/ee662537 (V = office.14). aspx
Http://technet.microsoft.com/zh-cn/library/ee662540 (V = office.14). aspx
Http://office.microsoft.com/en-au/sharepoint-server-help/enable-and-configure-versioning-for-a-library-HA101853103.aspx

 

Question 143
In your development environment, you designed new versions of a number of features currently working in a Sharepoint 2010 farm. the features are being used throughout the farm at all scope levels. you need to meet the following requirements:
. All the features on the farm must be upgraded to the newest version.
. All existing feature instances must be upgraded to the latest version.
. The sites using the features must experience as little downtime as possible.
Which approach shocould you recommend?
A. deploy all of the features as one solution package to the farm. specify the new version number for each feature in the current feature. XML file for the feature. activate all of the new features at the farm level.
B. deploy each of the features in its own solution package to the farm. specify the new version number for each feature in the current feature. XML file for the feature. activate the new features only in the locations where they are currently activated.
C. Specify the new version number and any upgrade actions required in each of the feature. xml files. Run feature upgrade as a solution package on the farm.
D. retract the existing versions of the features. specify the new version number for each feature in a new feature. XML file for each feature. deploy the features as a new solution package. activate the new features only in the locations where they are currently activated.

Resolution:
You have developed several new features in the development environment. The old version instances of these features have been applied in the production environment, their application layers are any layer of the entire field (web application, site collection, web, list ....), You need to do the following:
Requirement 1. All functions must be upgraded to the latest version.
Requirement 2. Existing features at all levels must be upgraded to the latest version
Requirement 3. Minimize function downtime
This question involves the upgrade of SharePoint functions. Let's take a look at the relevant description:
In Microsoft SharePoint Foundation, each feature has a version number specified in its corresponding feature. xml file. When a function is activated within a specific range, a function instance associated with the version of the function is created. With feature version control in SharePoint foundation, you can easily track features and their associated instances. Later, when you deploy the new feature, Sharepoint Foundation also needs to upgrade the associated feature, because the version number of the feature instance is smaller than the new version number specified in the current feature. xml file.
During feature upgrade, the feature instance to be upgraded is also upgraded Based on the upgrade operation specified in the new feature. xml file. SharePoint Foundation uses the new queryfeatures method (which can be applied to top-level objects such as spwebapplication and spsite) to determine the feature instance to be upgraded based on the version number of the feature instance. The new feature. xml file contains a part that can be used to specify the upgrade operations required to upgrade a specific feature instance from an earlier version to the latest version. To upgrade the infrastructure, You can query the set of feature instances to be upgraded, and then upgrade each feature instance. This activity involves declarative upgrade operations and custom Upgrade Code. In SharePoint Foundation, the version numbers of each feature instance are tracked.
Update the functions in the following order: Server field level, web application level, website set, and specific website. At the website level, the upgrade sequence of the function instance is: Starting from the root website, and then upgrading down according to the sub-website hierarchy. The dependency-based functions are upgraded in sequence, that is, the functions that these functions depend on are upgraded before the functions are upgraded.
When an error occurs during the upgrade, the upgrade stops at the specified feature instance and records the error in the ULS log and upgrade. log files. (Generally, the ULS log contains detailed information about the error ). In addition, you can continue to upgrade other feature instances. After the initial upgrade is completed and the process is restarted, the Administrator has the opportunity to discover and solve the problem that causes the function to fail to be upgraded. Later, when you restart the upgrade process, Sharepoint Foundation repeat all the upgrade operations on the features that failed the first upgrade to complete the upgrade process for all features and feature instances.
The <upgradeactions> section added in the feature. xml file specifies the upgrade operation that can be applied to the specified function.
You can place the <upgradeactions> section at the beginning or end of the feature. xml file so that it is in the content of the <feature> element. In this section, you can specify upgrade operations for different upgrade ranges and include a list of upgrade operations applied to a specified range. The upgrade definition always upgrades the feature to the version declared in the <feature> element.
Next we will analyze the backup options.
Option A. Package all the functions into a solution, redeploy the on-site level, and activate them at the on-site level. This obviously does not conform to the description of this question: "instances of the old version have already been applied in the production environment, and their application layers are at any level throughout the field ". In addition, this method does not meet the requirement of Group 2. Therefore, this option is excluded.
Option B. re-develop a solution for the new features of each function and deploy it on site. In this way, the old version is not upgraded, but the new version is developed and deployed. In addition, this method of constantly developing and deploying new solutions will frequently interrupt the SharePoint production environment. Therefore, option B should also be excluded.
Option C. Upgrade the solution package by developing features instead of re-developing the new feature solution package, which is clearly in line with the requirements of this question. The feature upgrade solution package is used to complete all the operations for Sharepoint feature upgrade.
Option D. Remove the features of the earlier version. This obviously does not meet requirement 2, that is, they cannot be withdrawn, but upgraded. Therefore, option D is excluded.

Therefore, C is the answer to this question.
Reference
Http://msdn.microsoft.com/zh-cn/library/ee535723 (V = office.14). aspx
Http://msdn.microsoft.com/zh-cn/library/ee535708 (V = office.14). aspx
Http://msdn.microsoft.com/zh-cn/library/ee537575 (V = office.14). aspx

SharePoint Study Notes-exercise series-70-exercise analysis-(Q141-Q143)