Problem setting up separate runtime environment on OWB 11g

Question

We're trying to set up an environment similar to this: [Split Repositories Implementation|http://download.oracle.com/docs/cd/B28359_01/owb.111/b31280/reqs01.htm#BGBIHAHE]
The server OS is Windows Server 2003 x64 ed, database version is 11.1.0.7
The database/warehouse server was installed with a single database where the default design repository is installed. There is a "control center service" running on the default instance.
We're running OWB clients on separate XP workstations and are able to access the minimal default design repository.
We've set up another database on the same server, this one is to be used for the runtime environment, as described in the references Oracle diagram referenced above.
However we're not able to find much useful documentation on how to set up the second database with the runtime environment and control center service.
Whenever we try to dig deeper into the Oracle documentation, we always end up with hints on how to set up a "remote runtime" on a server without database. This is not what we want to achieve.
A simple step-by-step guide on how to set up a runtime control center repository with audit tables & packages in a database separate from the design repository database is very difficult to find.
Is there anyone who've succeded in doing this that could give us any information on how to implement it?
Regards,
-Haakon-

Answer 1

Thanks again Oleg.
I've now managed to configure up a separate runtime target environment in addition to our design environment.
For others who might struggle with this; here's what I did:
- log on to the Windows server console
- open a command window
- set ORACLE_SID to the newly created runtime target database
- set ORACLE_HOME
to same home as previous OWB default home installation (initial design database)
- run >sqlplus "/as sysdba"
- run %OWB_HOME%/owb/UnifiedRepos/clean_owbsys.sql
to remove all previous OWBSYS setup
- edit %OWB_HOME%/owb/UnifiedRepos/cat_owb.sql
and comment out the 'LOCK USER OWBSYS' statement at the end, then run the script
- run %OWB_HOME%/owb/UnifiedRepos/reset_owbcc_home.sql : this will prompt for "the full path of the Oracle home for the OWB Control Center install:"
. Enter your '<drive>:\Oracle\product\11.1.0\db_1\owb'
- after running reset_owbcc_home.sql one needs to set a known password on the OWBSYS user:
ALTER USER owbsys IDENTIFIED BY password
- finally run the Repository Assistant locally on your server and set up a new repository workspace in the new database. This time (after running the above sql-scripts, the Assistant did not crash halfway through).
We're now able to create a new Control Center from the OWB client installation and deploy tables & mappings and execute mappings on the runtime target system.