" /> Why project Genesys Multimedia and related Business Components have to be create - Genesys CTI User Forum

Author Topic: Why project Genesys Multimedia and related Business Components have to be create  (Read 3254 times)

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
Advertisement
Hi, Guys,

I’m experiencing Siebel Gplus adapter 8;0 deployment, when I configure multimedia component, there are some steps about creating project ‘Genesys Multimedia’ and some related Business components mannually, ( these steps are on page 350, 351 of document Gplus Adapter 8.0 for Siebel CRM
Deployment Guide (80gp_dep_slcrm.pdf).

But for Voice component deployment, based on same document, we don’t have to create project ‘Genesys Voice’ and related business components manually, which will be created accordingly when all related SIFs are imported.


why is there such difference between voice and multimedia?

THanks.

Kevin

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Voice is natural configuration, MCR as always needs specific configurations as their universe is much bigger and many possibilities (mail, chat, sms, video, facebook, etc) and you need to specify what you need for your environment. It is normal procedure.

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
but even for these Multimedia sif, related projects and Business components will be created automatically, when they are imported directly.

why we bother to mannaully create them?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Eh? Automatically? Never as far as I have seen...GPlus is just a connector, so the manual will always go for the full steps, not the Wizard ones. I personally don't use Wizards as you can't see why they are doing and then troubleshooting those installations can take more time than needed.

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
from page 160 in document  80gp_dep_slcrm.pdf

Start of procedure
1. Start Siebel Tools against the local database.
2. Lock the projects common for all features and the projects for selected
optional features. Projects are described in Table 10.
3. Import the GenSymbolicStrings.sif file.
4. Lock the Genesys Symbolic Strings project.
5.Import the mandatory GenComm.sif file.
6. Lock the Genesys Voice Project.
7. Import the GenesysTools.sif file.
8. Lock the Genesys Tools Project.

from page 162:

Note: The project named Genesys Voice is created when you import the
GenComm.sif file, as explained in the instructions below. When you
first open the Projects list, the Genesys Voice project does not yet
exist and so is not available to be locked.
The project named Genesys Tools is created when you import the
GenesysTools.sif file. Lock the project after import of
GenesysTools.sif.
The project named Genesys Symbolic Strings is created when you
import the GenSymbolicStrings.sif file. Lock the project after import
of GenSymbolicStrings.sif

but in the Deploying the Multimedia Component section:  page 350
we need to create project mannually before we import sif.

Start of procedure
1. Start Siebel Tools.
2. If not done previously for the Voice Component, import the
GenSymbolicStrings.sif (for Siebel 7.8 and higher), GenComm.sif, and
GenesysTools.sif archives from:
<Installation Directory>/<Siebel Version>, where <Siebel Version> =
7.7, 8.0 or 8.1.
3. Create the Genesys Multimedia project, if it does not exist.
4. Lock the project.
5. Choose one of the Action-related Siebel Business Components (BC) that
you use and that corresponds with the following conditions.
The BC must have the following fields:

Offline Daimonas

  • Full Member
  • ***
  • Posts: 106
  • Karma: 2
  • There's a fish in every bowl.
I have read both documents you refer to. Like anything in Genesys, there are many ways to do things. Some manual, some by wizard. There is not really a right or wrong way to do it, if it results the same outcome, using a spesfic function within Genesys.

The setup instructions you point out are specific to Siebel, not Genesys. Therefore, Genesys is just documenting what they have used with Siebel to make it work based on previous questions or problems, setting up the connector in Siebel to work with Genesys.  So it is likely, either way would work, but will still require some customizations or configuration, if something doesn’t work  ;D