Topic
  • 3 replies
  • Latest Post - ‏2013-01-10T15:39:06Z by SystemAdmin
SystemAdmin
SystemAdmin
300 Posts

Pinned topic database instances vs database schemas

‏2013-01-08T08:44:27Z |
Hi,
we need to install a WL 5.0.5 Server that is going to use Oracle as target DB and Websphere as runtime AS.

The DBA created the required databases (WRKLGHT, WLREPORT, APPCNTR) before WL installation.
Actually, he did not create three separate Oracle instances.
He used instead a single Oracle instance and created the required structures as separate schemas (ie: worklight, worklightReport, worklightAppCntr).

When we run the GUI Installation Manager, we hit a "Database properties" panel that needs to be filled up with connectivity settings for the target Oracle.

Unfortunately in this panel I can only specify a single username as "Access settings".
Which one of the above different schemas shall we use ?

If this panel is not completely (and correctly) set, then we can't proceed with the GUI installation.

Is there any way to workaround this ? Maybe a silent installation allow to specify all different schemas ?

Please let us know how we can move on.
Thanks in advance for any help.
Ciao, Stefano.
  • SystemAdmin
    SystemAdmin
    300 Posts

    Re: database instances vs database schemas

    ‏2013-01-08T09:25:07Z  
    Hi.
    I can add one further notice about the subject.

    The customer already has a running WL 5.0.0.3 installation.

    The target Oracle has been configured as desired, with the two WRKLGHT and WLREPORT database structures defined as different schemas on a single DB instance (the APPCNTR database was not yet required).

    For this 5.0.0.3 installation, the IM "Database properties" panel is empty ("No settings" required).
    This allowed the customer to successfully complete the installation.

    Is it possible to skip the "Database properties" panel also for the new v5.0.5 installation ?
    Ciao, Stefano.
  • slowhand
    slowhand
    35 Posts

    Re: database instances vs database schemas

    ‏2013-01-08T12:49:10Z  
    > The DBA ... did not create three separate Oracle instances.
    > He used instead a single Oracle instance and created the required structures as separate schemas (ie: worklight, worklightReport, worklightAppCntr).

    > When we run the GUI Installation Manager, we hit a "Database properties" panel that needs to be filled up with connectivity settings for the target Oracle.
    > Unfortunately in this panel I can only specify a single username as "Access settings".

    The installer is meant to provide a simple-to-use setup that matches most customer situations.

    In this situation, which does not match the set of situations for which the installer was made for, a reasonable workaround is to
    1. specify a "Derby" database or a dummy "MySQL" database that you have set up,
    2. let the installer proceed,
    3. after the installer is done, modify the definition of the datasources in the app server's configuration.
    The latter is under "Resources > JDBC > JDBC providers" and "Resources > JDBC > Data sources" for WAS (to be modified through the WebSphere administrative console).
    You also have to modify the wl.db.type and wl.reports.db.type properties in worklight.properties in the worklight.war file.
    4. create and initialize the databases as described in the appendix of the Worklight 5.0.0.3 Admin Guide.

    > Maybe a silent installation allow to specify all different schemas ?

    No, the silent installation offers the same choices as the GUI installation.

    > For this 5.0.0.3 installation, the IM "Database properties" panel is empty ("No settings" required). This allowed the customer to successfully complete the installation.
    > Is it possible to skip the "Database properties" panel also for the new v5.0.5 installation ?

    No, the "Other database (requires manual setup)" choice from the 5.0.0.3 installer is gone in 5.0.5.

    I hope the workaround mentioned above works for you.

    --slowhand
  • SystemAdmin
    SystemAdmin
    300 Posts

    Re: database instances vs database schemas

    ‏2013-01-10T15:39:06Z  
    • slowhand
    • ‏2013-01-08T12:49:10Z
    > The DBA ... did not create three separate Oracle instances.
    > He used instead a single Oracle instance and created the required structures as separate schemas (ie: worklight, worklightReport, worklightAppCntr).

    > When we run the GUI Installation Manager, we hit a "Database properties" panel that needs to be filled up with connectivity settings for the target Oracle.
    > Unfortunately in this panel I can only specify a single username as "Access settings".

    The installer is meant to provide a simple-to-use setup that matches most customer situations.

    In this situation, which does not match the set of situations for which the installer was made for, a reasonable workaround is to
    1. specify a "Derby" database or a dummy "MySQL" database that you have set up,
    2. let the installer proceed,
    3. after the installer is done, modify the definition of the datasources in the app server's configuration.
    The latter is under "Resources > JDBC > JDBC providers" and "Resources > JDBC > Data sources" for WAS (to be modified through the WebSphere administrative console).
    You also have to modify the wl.db.type and wl.reports.db.type properties in worklight.properties in the worklight.war file.
    4. create and initialize the databases as described in the appendix of the Worklight 5.0.0.3 Admin Guide.

    > Maybe a silent installation allow to specify all different schemas ?

    No, the silent installation offers the same choices as the GUI installation.

    > For this 5.0.0.3 installation, the IM "Database properties" panel is empty ("No settings" required). This allowed the customer to successfully complete the installation.
    > Is it possible to skip the "Database properties" panel also for the new v5.0.5 installation ?

    No, the "Other database (requires manual setup)" choice from the 5.0.0.3 installer is gone in 5.0.5.

    I hope the workaround mentioned above works for you.

    --slowhand
    Hi Bruno,
    I didn't have the chance to try your suggested workaround.
    The customer decided to make a new v5.0.5 fresh install setting up all the required 3 databases (sticking by the rule).
    Thanks anyway for your help.
    Ciao, Stefano.