Customer Connect vs Customer Portal

Yahoo Archive
1
>
> So using the portal I could deploy custom queries to each customer?
>

Good question. I know that the Connect Products (Customer and Sales)
respect the business logic where a customer only sees her own orders
and sales reps only see their orders. I assume that the Portal follows
the same logic.

The connect products have a method to add usernames and to link them
to customers but I'm not sure how Portal does the same thing. It could
be the same process, I just don't know.

Mark W.
2
What is the difference between the 2 of these?
We have had customer connect for some time but have never used it yet.

Also is anyone connecting directly to the DB using ASP.net & ODBC for
a customer portal?
3
> What is the difference between the 2 of these?
> We have had customer connect for some time but have never used it yet.
>
> Also is anyone connecting directly to the DB using ASP.net & ODBC for
> a customer portal?

This is my understanding:

The Connect Products have a separate database that are sync'd through
a Sonic process . This means that the web server is hitting the copy
of the database and the webserver stays up when you shut down your
production database. When the database comes back up, the changes
resync. The Product Configurator is available within the Connect
framework.

Portal exposes BAQs as web parts and can start Service Connect
processes to update the database. If the server is down, the portal is
down and there's no resyncing. You cannot run Product Configurations
in the Portal ordering screens.

Mark W.
4
So using the portal I could deploy custom queries to each customer?

--- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@...> wrote:
>
> > What is the difference between the 2 of these?
> > We have had customer connect for some time but have never used it yet.
> >
> > Also is anyone connecting directly to the DB using ASP.net & ODBC for
> > a customer portal?
>
> This is my understanding:
>
> The Connect Products have a separate database that are sync'd through
> a Sonic process . This means that the web server is hitting the copy
> of the database and the webserver stays up when you shut down your
> production database. When the database comes back up, the changes
> resync. The Product Configurator is available within the Connect
> framework.
>
> Portal exposes BAQs as web parts and can start Service Connect
> processes to update the database. If the server is down, the portal is
> down and there's no resyncing. You cannot run Product Configurations
> in the Portal ordering screens.
>
> Mark W.
>