Administering the SAS Add-In for Microsoft Office |
Overview |
Custom add-in tasks are .NET assemblies (DLL files) that you create, deploy, register, and execute from the SAS ribbon in Microsoft Office applications.
To provide access to custom tasks based on the job responsibilities in your organization, you first register custom tasks as capabilities. You then assign the capabilities to roles, and assign users to roles.
The process of creating, deploying, registering, and executing custom tasks as capabilities in the SAS Add-In for Microsoft Office is similar to the process that is used in SAS Enterprise Guide.
Create Custom Tasks |
To create custom tasks, you develop Windows executables and package
them as .NET assemblies. It is convenient to assemble multiple tasks in a
single .NET assembly so that you can share code and implementation among the
tasks. For additional information, see Administering SAS Enterprise
Guide, at
http://support.sas.com/documentation/onlinedoc/guide/.
Deploy Custom Tasks |
You can deploy custom tasks to computers that run the SAS Add-In for Microsoft Office in two ways, using drop-in deployment or add-in deployment. Drop-in deployment copies .NET assemblies into specific local directories that are recognized by the SAS Add-In for Microsoft Office. Custom tasks in drop-in directories are automatically registered (made available for execution) the next time the user starts a Microsoft Office application.
Add-in deployment copies .NET assemblies into any local directory. You then identify those directories for use in the SAS Add-In for Microsoft Office using the Add-In Manager in SAS Enterprise Guide. Deployment registration makes the custom tasks available for execution from the SAS ribbon in Microsoft Office applications.
When you deploy your custom tasks, make sure that you include any dependent assemblies that are referenced by those tasks. At the same time, make sure that you do not include any dependent assemblies that are provided by the SAS Add-In for Microsoft Office or by SAS Enterprise Guide.
Follow these steps to use the Add-In Manager:
Copy the .NET assembly into one of the following directories:
C:\ProgramFiles\SAS\Add-InForMicrosoftOffice\release-number\Custom
%appdata%\SAS\Add-InForMicrosoftOffice\release-number\Custom
where
%appdata% is the Microsoft Window environment variable that maps to a user account.
Repeat the copy in other user accounts if multiple users run the SAS Add-In
for Microsoft Office on the same
host.
%appdata%\SAS\SharedSettings\release-number\Custom
Use this location
to deploy custom tasks to specified user accounts, using a shared
directory that is accessed by the SAS Add-In for Microsoft Office and SAS
Enterprise Guide.
Start or restart a Microsoft Office application to register the custom tasks and make them available for testing.
Follow these steps to use add-in deployment:
Copy the .NET assembly into any local directory.
Start SAS Enterprise Guide and open the Add-In Manager. Select Tools Add-In Add-In Manager.
In the Add-In Manager dialog box, select Browse .
Navigate to the directory where you stored your .NET assembly.
Click Open to display the names of the custom tasks in the assembly.
Click OK to accept the custom tasks and register them in SAS Enterprise Guide.
Test the new custom tasks in a Microsoft Office application.
Register Custom Tasks As Capabilities |
After you deploy custom tasks, follow these steps to register custom tasks as capabilities:
In SAS Enterprise Guide, start SAS Enterprise Guide Explorer. Select Tools SAS Enterprise Guide Explorer.
In Explorer, select Tools Task Import Wizard.
In the first page of the Task Import Wizard, you see your current metadata profile connection. If you need to connect with a different profile, click Cancel to close the wizard and select File Manage Profiles. After you change your profile, click Close, then start the Task Import Wizard.
In the second page of the Task Import Wizard, specify the location from which you want to import task definitions. You can choose to have the wizard search standard locations for task definitions or you can specify a task-definition XML file.
Select tasks to receive metadata, and then click Finish in the sixth wizard page to create metadata.
If you are unable to create metadata, then you might need to install the package named SAS Add-In for Microsoft Office Server Data on the host that contains your current metadata repository.
Apply Custom-Task Capabilities to Roles |
Follow these steps to apply custom-task capabilities to roles:
In SAS Management Console, open the User Manager.
To create a new role for your custom-task capabilities, right-click in the User Manager and select New Role.
To add a custom-task capability to an existing role, double-click an Add-In for Microsoft Office role.
In the role properties window, click the Capabilities tab.
In the Capabilities tab, expand the Plug-Ins branch in the tree view.
Click the custom-task capabilities that you want to add to that role.
Click OK.
The custom-task capabilities will be applied to the role the next time affected users initialize a Microsoft Office application.
Note: To access unregistered custom tasks, you need the capability Access Unregistered Custom Tasks, which is available in the Tools and Help category, as described in Default Roles and Capabilities for the SAS Add-In for Microsoft Office.
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.