Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When installing SAS Email Marketing (SEM) 2.2 against SAS Marketing
Automation, you need to perform the following in order to get the
integration pieces to function. If not, you may receive Remote Exception
errors when trying to add or modify an export definition in the SAS
Management Console Marketing Automation plug-in.

The instructions below are for systems where IBM WebSphere is used as
the container for the MA Application Server. For instructions specific
to BEA WebLogic, please refer to SAS Note:  #017382 .

From the SEM directory:

...\SASEmailMarketing\2.2\lib

copy "sas.email.core.jar" to the export adatpter installation directory:

...\SASMarketingAutomation\MAExportAdapters\4.3

together with the new sas.email.broadcast.jar taken from the SEM
directory

...\SASEmailMarketing\2.2\doc\lib

This is required due to the missing class of

com/sas/email/rmi/asp/AspProviderManager

in the new sas.email.broadcast.jar

Instructions for Installation and Configuration of the Marketing Automation SEM Adapter Using Websphere are fully described in the Integration of the SAS E-mail Marketing Server in Marketing Automation 4.4 document.

Please take time to read this document before following the additional
steps presented here.

For WebSphere, a folder containing these jars should also be created to
establish a shared library. For example: "D:\SASBES". Copy the new jars
to this location also.

Add the "sas.email.core.jar" to the shared library. This is performed
from the WebSphere Administration Console via Environment->Shared
Libraries. Use the following steps:

From the WebSphere Administrative Console, set up the shared library as
follows:

(Note: These steps assume you are starting from scratch, you may need to
remove and delete the existing shared library first, or alternatively
you can edit the existing shared library)

- Select Environment->Shared Libraries
- Select the correct scope radio button; e.g. "Server" and select the
  'Apply' button
- Click the "New" button
- Enter the library name: SASBES (or any other meaningful name)
- Enter the classpath settings: (using the example directory above)

D:/SASBES/sas.analytics.crm.adapter.bes.jar
D:/SASBES/sas.analytics.crm.ma.adapter.jar
D:/SASBES/sas.email.broadcast.jar
D:/SASBES/sas.email.core.jar

- Click the ‘Apply’ button
- Click the ‘Save’ button

The next step is to add the shared library to the MA libraries. This is
performed in the Administrative Console as follows:

- Select Applications->Enterprise Applications
- Select Marketing Automation 4.3
- Select Libraries
- Click the ‘Add’ button
- Select ‘SASBES’ Adapter Shared Library (using the example name above)
- Click the ‘Apply’ button
- Click the ‘Save’ button

The next step is to add WebSphere policy permissions for the shared
library jar files. This is achieved using the policy tool editor and is
documented on page 9 of the installation and configuration document
mentioned above. Please include additional permissions for the
"sas.email.core.jar" as follows:

- Navigate to the directory tree in the Open window to pick up the
policy file that you need to update. After selecting the policy file,
click Open. The code base entries are listed in the window. Use the
following steps to add entries into the policy file:

- Click the ‘Add Policy Entry’ button

- In the CodeBase field, type the path to one of each of the jar files
in the following format (using the example folder ‘D:\SASBES’ notice
that forward-slash ‘/’ is used):

file:/d:/SASBES/sas.email.core.jar

- Enter the above and click the ‘Add Permission’ button and then select
‘AllPermission’ from the drop down menu.

- Click the ‘OK’ button.

This completes the additional installation steps for deployment of the
SEM export adapter for WebSphere. Please ensure all other steps included
in the installation and configuration guide are also followed. Once the

Operating System and Release Information