|
Home > Archive > WebSphere Commerce suite > January 2004 > Team Development
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Google 2004-01-19, 2:48 pm |
| We're working on porting a 4.1 implementation to 5.5. When we first
installed Commerce Studio on our machines, we didn't have a shared database
to use so we installed DB2 on each developer's workstation. Now we have
ported all the old data to a database instance that we want to share. We
want to share it so that we don't have to maintain an instance on each
developer's machine.
How do we switch our installs of Commerce Studio to work with the shared
database instance instead of local instances? We have tried creating new
server instances in the configuration panel and having them use the remote
database, but this only seems to work for one developer machine. When we set
up a second machine the same way, there seem to be some conflicts because of
duplicate primary keys. Should each developer use a different admin login
for WebSphere?
| |
| Senthil Anand 2004-01-19, 2:48 pm |
| Update your $instance$.xml to point to remote database.
"Google" <bgoggin@amentra.com> wrote in message
news:bj7hq5$52ao$1@news.boulder.ibm.com...quote:
> We're working on porting a 4.1 implementation to 5.5. When we first
> installed Commerce Studio on our machines, we didn't have a shared
databasequote:
> to use so we installed DB2 on each developer's workstation. Now we have
> ported all the old data to a database instance that we want to share. We
> want to share it so that we don't have to maintain an instance on each
> developer's machine.
>
> How do we switch our installs of Commerce Studio to work with the shared
> database instance instead of local instances? We have tried creating new
> server instances in the configuration panel and having them use the remote
> database, but this only seems to work for one developer machine. When we
setquote:
> up a second machine the same way, there seem to be some conflicts because
ofquote:
> duplicate primary keys. Should each developer use a different admin login
> for WebSphere?
>
>
|
|
|
|
|