Operate > WebSphere Commerce Accelerator > Business relationship management > Create reseller relationships: an overview

Create service agreements for a store

Before you create a service agreement for a store, ensure that the following steps are complete:

Before you begin

1. Obtain a copy of the template service agreement XML file to use on your local client. The service agreement XML template can be found in the following location on the machine where WebSphere Commerce is installed: WC_EAR/xml/trading/xml/TemplateHostingContract.xml

2. Ensure you have the following information:

   • Full DN of the reseller organization.

   • E-mail address for the owner of the store.

   • Directory name where the store assets will be saved.

   • Full DN of the service provider organization.

   • Full DN of the profile stores organization.

   • Unique name of the catalog profile store you want the store to use.

   • Unique name of the store profile store you want the store to use.

   • Unique name of the shared fulfillment center you want the reseller store to use.

Note that if you import a contract by using XML, and want to have that contract appear in the WebSphere Commerce Accelerator, then have a contract description.

Procedure

1. Copy the template service agreement XML file to a new file name.

2. Open the copy of the template service agreement XML file in either a text editor or an XML editor.

3. Replace all the instances of the following strings with values appropriate for the distributor...

   1. Replace HOSTED_STORE_ORG_DISTINGUISHED_NAME with the full distinguished name of the store organization. This can be found in the DN column of the ORGENTITY table An example is o=Example Organization,o=Reseller Organization,o=Root Organization.

   2. Replace HOSTED_STORE_SUB_ORG_NAME with the name of the store sub-organization. The sub-organization will be created during the deployment of the contract. An example is Example RHS Organization.

   3. Replace HOSTED_STORE_SUB_ORG_DISTINGUISHED_NAME with the full DN of the store sub-organization. The sub-organization will be created during the deployment of the contract. An example is o=Example RHS Organization,o=Reseller Organization,o=Root Organization.

   4. Replace HOSTED_STORE_OWNER_DISTINGUISHED_NAME with the full distinguished name of the owner of the store. This can be found in the DN column of the USERS table. An example is uid=Me,o=Example Organization,o=Reseller Organization,o=Root Organization.

   5. Replace HOSTED_STORE_OWNER_EMAIL_ADDRESS with the e-mail address of the owner of the store. An example is me@Example.com.

   6. Replace HOSTED_STORE_DISPLAY_NAME with the name of the store. An example is Example.

   7. Replace HOSTED_STORE_DESCRIPTION with the description of the hosting store An example is This is the Example store.

   8. Replace HOSTED_STORE_DIRECTORY_NAME with the name of folder to keep store file assets. An example is Example.

   9. Replace HOSTED_STORE_DEFAULT_LOCALE with the store's default locale. An example is en_US.

   10. Replace HOSTED_STORE_DEFAULT_CURRENCY with the store's default currency. An example is USD.

   11. Replace SERVICE_PROVIDER_ORG_DISTINGUISHED_NAME with the full distinguished name of the service provider organization. This can be found in the DN column of the ORGENTITY table. An example is ou=Service Provider Organization,o=Manufacturer Organization,o=Root Organization.

   12. Replace PROFILE_ORG_DISTINGUISHED_NAME with the full DN of the profile stores organization. This can be found in the DN column of the ORGENTITY table. An example is ou=Profile Organization,o=Manufacturer Organization,o=Root Organization.

   13. Replace CATALOG_PROFILE_STORE with the unique name of the catalog profile store This can be found in the IDENTIFIER column of the STOREENT table. An example is Catalog Profile Store.

   14. Replace HOSTED_STORE_PROFILE_STORE with the unique name of the store profile store. This can be found in the IDENTIFIER column of the STOREENT table. An example is Reseller Profile Store.

   15. Replace SERVICE_PROVIDER_SHARED_FULFILLMENT_CENTER_NAME with the name of shared fulfillment center of service provider. This can be found in the NAME column of the FFMCENTER table. An example is Shared fulfillment center.

   16. Replace SERVICE_PROVIDER_LOCALE with the locale of the WebSphere Commerce Accelerator in which you are loading the contract. An example is en_US.

   17. Replace POLICY_GROUP_B2B_OR_B2C_NAME with the policy group name of the B2B direct or B2B indirect business to consumer policy group. Use either B2BPolicyGroup or B2CPolicyGroup.

   18. Replace POLICY_GROUP_NAME_FOP_PROFILE_STORE with the policy group name for the profile store. This can be found in the NAME field of the ACPOLGRP table. An example is Reseller Profile Store ProfileGroup.

   19. Replace the entire PaymentAccount element with the appropriate PaymentAccount element for the credit cards you accept. An example is

       <PaymentAccount currency="USD">        
       <Brand type="MasterCard"/>        
       <Brand type="VISA"/>        
       <Brand type="American Express"/>
       </PaymentAccount>
       

   20. Replace PAYMENT_METHOD with the payment method string to be used with Custom Offline Cassette. This information determines the account to be used in each payment transaction that is processed by the Custom Offline Cassette.

   21. Add any additional ShippingMode elements that should be set up for each store.

4. Save the file.

5. Import the service agreement XML file into WebSphere Commerce.

+

Search Tips   |   Advanced Search