• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 866
  • Last Modified:

Application Database with Vignette

Hello, I´m a new developer using Vignette v6. I am spanish and my english is not pretty good. I am doing my first web application with Vignette. I have a database for this application but I don´t know if this database is the Content database or not. I know the Content database is an internal Vignette database but I don´t know if my application database has to be the same.

I need help. Thanks a lot.
0
oarnaiz
Asked:
oarnaiz
  • 3
  • 2
1 Solution
 
hooker042299Commented:
Basically, you need a place where Vignette can create all it's own tables that store all the internal information it needs and a place where your application will store its data.

This can be the same schema/database.
But it is good practice to store the internal Vignette tables and the content (the tables that you will insert/select from) in different schemas.

There are two ways to configure this. Firstly, you can use the configuration script to use <schema a> for the Vignette system tables and <schema b> for the content tables.
Or, you can configure the installation to use the <schema a> for both. Then in your application you can overwrite the variables ::USERNAME and ::PASSWORD to connect to a different schema. Why this way? If you were going to have multiple different applications, then you might want them to store their data in different logical places - different schemas. So each application could connect to their own schema.

What database are you using? And is there a database person assisting you in this?

Yo no conozco las palabras tecnicas para responder en espanol a su pregunta (ni las teclas para escribirlo)...
Espero que entiendas lo que digo..
0
 
oarnaizAuthor Commented:
First of all, thanks for your answer. The problem is that I still having the same question I tried to explain before. Do I need to transfer my application´s Oracle 8.1.7. schema/database to the CMS database or not? I´ve one schema (Vignette´s default) in CMS database.
0
 
hooker042299Commented:
Ok - I don't fully understand your question / situation.
I need more information
Can we try and walk through it?

What is the situation with your Vignette installation?
Vignette is installed and configured?
Configured is use <schema a> for both system and content?
Configured to use <schema a> for system tables and <schema b> for content?
It sounds like you're going to create a new application in Vignette. Is that right? Or are you transfering an existing application to Vignette?
When you say that you "have a database for this application", do you mean that someone has created a schema in a different database for use in this new application? There is a table structure? There is data?
Is this currently a different schema or a different database (e.g. is the Vignette schema connect string something like <user1>/<password>@<DB1> but the application database is <user2>/<passsword>@<DB2> OR is the it <user1>/<password>@<DB1> and <user2>/<password>@<DB1>)?


Whatever your answers, there is probably more than one option. Within a template, you can override the internally set connect string to connect to a different schema or a different database.
I would have thought that your ideal aim should be to have one database with two schemas - one with the system tables, one with the tables & data used in your application.


0
 
hooker042299Commented:
Addition: Just to explain further, Vignette uses ODBC so you should be able to configure the templates to connect and query any database that you would normally be able to connect to. So although I mention what I think is the "ideal" situation - that's just my opinion. But if you already have schema a in database 1 for Vignette system and schema b in database 2 for the application then there's no problem - it's just a case of overriding the ::USERNAME, ::PASSWORD and ::SERVER variables to get the template to connect to where you want it to connect to (I know I'm repeating myself).
0
 
oarnaizAuthor Commented:
Thanks a lot.
0

Featured Post

KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now