Creating Enterprise and Prepopulating Data

Pre-requisites: Ensure that the Application Server is running.

Procedure

  1. Create four or more enterprises.
    Enterprise Type
    BrandOwner Supplier
    VeloselMarketplace Marketplace
    Bottler1 Supplier
    Bottler2 Supplier
  2. Create BrandOwner Enterprise:
    • Create a BrandOwner Enterprise of type Supplier with Internal Name as bowner
      Attribute Value
      Enterprise BrandOwner
      Enterprise Type Supplier
      Internal Name bowner
    • Create a user admin with first name admin and last name admin. Assign the Work Supervisor and Admin roles to this user.
      Attribute Value
      User Name admin
      First/Middle/Last admin//admin
      Roles Work Supervisor/Admin
    • Import XML Pack for BrandOwner Enterprise, you can import an XML pack to prepopulate the enterprise with some data.
      • Log in to the BrandOwner enterprise.
      • Select System Operations > Import Meta Data.


      • Provide the path to the following xml file:
$MQ_COMMON_DIR/common/standard/samples/cim2cimmetadata/Brandowner/BrandOwner-MetaData.jar.
      • Refer to Step 6 to view the data generated through XML pack import.
  3. Create VeloselMarketplace Enterprise (This is just for subscription purposes. The real Velosel Marketplace Enterprise resides on Instance 2):
    • Create an Enterprise VeloselMarketplace of type Marketplace with Internal Name as Veloselm.
      Attribute Value
      Enterprise VeloselMarketplace
      Enterprise Type Marketplace
      Internal Name Veloselm
    • Create a user admin with first name admin and last name user. 
Assign the Work Supervisor and Admin roles to this user.
      Attribute Value
      User Name admin
      First/Middle/Last admin//admin
      Roles Work Supervisor/Admin
    • Import XML Pack for VeloselMarketplace Enterprise, you can import an XML pack to prepopulate the enterprise with some data.
      • Log in to the VeloselMarketplace enterprise.
      • Select System Operations > Import Meta Data.
      • Provide the path to the following xml file:
$MQ_COMMON_DIR/standard/samples/cim2cimmetadata/VeloselMarketplace/VeloselMarketplace-MetaData.jar
      • Refer to Step 6 to view the data generated through XML pack import.
  4. Create Bottler1 Enterprise:
    • Create an Enterprise Bottler1 of type Supplier with Internal Name as Bottler1.
      Attribute Value
      Enterprise Bottler1
      Enterprise Type Supplier
      Internal Name Bottler1
    • Create a user admin with first name admin and last name user. Assign the Work Supervisor and Admin roles to this user.
      Attribute Value
      User Name admin
      First/Middle/Last admin//admin
      Roles Work Supervisor/Admin
    • Import XML Pack for Bottler1 Enterprise, you can import an XML pack to prepopulate the enterprise with some data.
      • Log in to the Bottler1 enterprise.
      • Select System Operations > Import Meta Data.
      • Provide the path to the following xml file:
$MQ_COMMON_DIR/standard/samples/cim2cimmetadata/Bottler1/Bottler1-MetaData.jar.
      • Refer to Step 6 to view the data generated through XML pack import.
  5. Create Bottler2 Enterprise:
    • Create an Enterprise Bottler2 of type Supplier with Internal Name as Bottler2
      Attribute Value
      Enterprise Bottler2
      Enterprise Name Supplier
      Internal Name Bottler2
    • Create a user admin with first name admin and last name user. Assign the Work Supervisor and Admin roles to this user.
      Attribute Value
      User Name admin
      First/Middle/Last admin//admin
      Roles Work Supervisor/Admin
    • Import XML Pack for Bottler2 Enterprise, you can import an XML pack to prepopulate the enterprise with some data.
      • Log in to the Bottler2 enterprise.
      • Select System Operations > Import Meta Data.
      • Provide the path to the following XML file:
$MQ_COMMON_DIR/standard/samples/cim2cimmetadata/Bottler2/Bottler2-MetaData.ja
      • Refer to Step 6 to view the data generated through XML pack import.
  6. Data generated through XML Pack Import: By importing the various XML packs, the respective enterprises are populated with the following:
    • Repository: For example, MC_V2VITEMMASTER

    • Attributes: some custom attributes in repository MC_V2VITEMMASTER

    • Output Maps: an output map OM_V2VOUTPUT based on the EANUCCExt Output format created in repository MC_V2VITEMMASTER

    • Synchronization Format: EANUCCEXT synchronization format with some custom attributes

    • The following Business Process rules are created:
      • Brandowner enterprise: Custom Protocol Selection and Rulebase Selection
      • VeloselMarketplace enterprise: Custom Protocol Selection, Rulebase Selection, and Repository Selection for Received Records
      • Bottler1 and Bottler2 enterprises: Custom Protocol Selection and Repository Selection for Received Records