Export (0) Print
Expand All

Set up an Oracle database

Dynamics AX 4.0

To set Microsoft Dynamics AX up to work with an Oracle database, you must work with an Oracle database administrator (DBA), to follow this process:

  1. Microsoft Dynamics AX administrator and System Administrator. Determine which account you want the Application Object Server (AOS) service to run as.

  2. Oracle DBA: On the computer that will host the Oracle database:

    • Set up Oracle Database 10g with appropriate tablespaces and indexspaces.

    • Create a user account with rights in the database for the Microsoft Dynamics AX administrator to use when installing anApplication Object Server (AOS) instance,

    • Optional. Add the AOS account of each computer as a user in the database.

    • Optional. Create a schema for each database instance.

    • Optional. Compile Setup stored procedures on the Oracle database.

  3. Oracle DBA: Install an administrator version of an Oracle Database 10g client on the computer that will host the Application Object Server (AOS) instance.

  4. Microsoft Dynamics AX administrator: On the computer that will host the AOS instance, log in with the installing user account, and use the Setup wizard to set up the AOS and connect it to the Oracle database.

  5. Microsoft Dynamics AX administrator: Start Microsoft Dynamics AX, and as part of the installation checklist, configure the placement of tables in tablespaces. For more information, see Configure Oracle tablespaces.

You can set up multiple Microsoft Dynamics AX databases on an Oracle system by following the process below and creating each database under a different schema.

  1. Work with a System Administrator to determine which account you want the AOS service to run as.

    By default, an AOS instance runs as the Network Service account of the computer that you install it on. You can also set the AOS instance to run as a domain account.

    NoteNote

    If you are installing an AOS and an Oracle database on the same computer, you must use a domain account for the AOS account.


  2. Optional. If you choose to use a domain account, work with a System Administrator to have a new account created solely for use by the AOS instance. We recommend that the account be set up as follows:

    • Log on as a service

    • No interactive logon rights

The following steps must be performed by an Oracle DBA.

  1. Set up Oracle Database 10g with the following characteristics:

    Option

    Value

    Database name

    Any valid Oracle database name

    Tablespace

    Create tablespaces for Microsoft Dynamics AX to use, for example:

    • AXTAB, for tables

    • AXIDX, for indexes

    • AXTMP, for temporary tables

    The Microsoft Dynamics AX administrator can configure the tablespaces after Microsoft Dynamics AX has been fully installed. For more information, see Configure Oracle tablespaces.

    NoteNote
    If you are upgrading, you must use the same tablespace names in the Microsoft Axapta 3.0 system and the Microsoft Dynamics AX new system.
    NoteNote

    Microsoft Dynamics AX supports Unicode collations. If you are setting up a new Microsoft Dynamics AX installation, we recommend that you choose a Windows collation for your location. For more information about choosing a collation for an Oracle database, see your Oracle documentation.


  2. Setup uses the Windows account of the installing user to allow the AOS account (the domain account or Network Service account that is associated with an AOS instance) to connect to the Oracle database, and to write stored procedures to the Oracle database. To enable this, set the following rights:

    • Add the network account of the person who will install the AOS to the database administrators group in Oracle.

    • Set Oracle to use Windows authentication.

  3. Optional. Add the AOS account of each computer that runs an AOS instance in your system as a user in the database. Grant the user accounts the following rights in the database:

    GRANT CREATE USER TO "<AOSaccount_name>";
    GRANT SELECT ANY CATALOG TO "<AOSaccount_name>";
    GRANT CREATE PROCEDURE TO "<AOSaccount_name>";
    

    If you do not perform this step, Setup grants the following rights to the current AOS instance:

    • ALL PRIVILEGES

    • SELECT ANY DICTIONARY

  4. Optional. Create a schema (user account) for each database instance and grant the following rights:

    CREATE USERS <schema name> IDENTIFIED BY "<schema password>";
    GRANT ALTER ANY CLUSTER TO "<schema name>";
    GRANT ALTER ANY DIMENSION TO "<schema name>";
    GRANT ALTER ANY INDEX TO "<schema name>";
    GRANT ALTER ANY INDEXTYPE TO "<schema name>";
    GRANT ALTER ANY MATERIALIZED VIEW TO "<schema name>";
    GRANT ALTER ANY PROCEDURE TO "<schema name>";
    GRANT ALTER ANY TABLE TO "<schema name>";
    GRANT ALTER TABLESPACE TO "<schema name>";
    GRANT ALTER USER TO "<schema name>";
    GRANT ANALYZE ANY DICTIONARY TO "<schema name>";
    GRANT CREATE ANY CLUSTER TO "<schema name>";
    GRANT CREATE ANY DIMENSION TO "<schema name>";
    GRANT CREATE ANY INDEX TO "<schema name>";
    GRANT CREATE ANY INDEXTYPE TO "<schema name>";
    GRANT CREATE ANY MATERIALIZED VIEW TO "<schema name>";
    GRANT CREATE ANY PROCEDURE TO "<schema name>";
    GRANT CREATE ANY TABLE TO "<schema name>";
    GRANT CREATE ANY VIEW TO "<schema name>";
    GRANT CREATE CLUSTER TO "<schema name>";
    GRANT CREATE DATABASE LINK TO "<schema name>";
    GRANT CREATE DIMENSION TO "<schema name>";
    GRANT CREATE INDEXTYPE TO "<schema name>";
    GRANT CREATE MATERIALIZED VIEW TO "<schema name>";
    GRANT CREATE PROCEDURE TO "<schema name>";
    GRANT CREATE PUBLIC DATABASE LINK TO "<schema name>";
    GRANT CREATE TABLE TO "<schema name>";
    GRANT CREATE TABLESPACE TO "<schema name>";
    GRANT CREATE USER TO "<schema name>";
    GRANT CREATE VIEW TO "<schema name>";
    GRANT DELETE ANY TABLE TO "<schema name>";
    GRANT DROP ANY CLUSTER TO "<schema name>";
    GRANT DROP ANY DIMENSION TO "<schema name>";
    GRANT DROP ANY INDEX TO "<schema name>";
    GRANT DROP ANY INDEXTYPE TO "<schema name>";
    GRANT DROP ANY MATERIALIZED VIEW TO "<schema name>";
    GRANT DROP ANY PROCEDURE TO "<schema name>";
    GRANT DROP ANY TABLE TO "<schema name>";
    GRANT DROP ANY VIEW TO "<schema name>";
    GRANT DROP PUBLIC DATABASE LINK TO "<schema name>";
    GRANT DROP TABLESPACE TO "<schema name>";
    GRANT DROP USER TO "<schema name>";
    GRANT EXECUTE ANY INDEXTYPE TO "<schema name>";
    GRANT EXECUTE ANY PROCEDURE TO "<schema name>";
    GRANT EXPORT FULL DATABASE TO "<schema name>";
    GRANT GLOBAL QUERY REWRITE TO "<schema name>";
    GRANT GRANT ANY OBJECT PRIVILEGE TO "<schema name>";
    GRANT GRANT ANY PRIVILEGE TO "<schema name>";
    GRANT IMPORT FULL DATABASE TO "<schema name>";
    GRANT INSERT ANY TABLE TO "<schema name>";
    GRANT LOCK ANY TABLE TO "<schema name>";
    GRANT MANAGE SCHEDULER TO "<schema name>";
    GRANT MANAGE TABLESPACE TO "<schema name>";
    GRANT QUERY REWRITE TO "<schema name>";
    GRANT SELECT ANY DICTIONARY TO "<schema name>";
    GRANT SELECT ANY TABLE TO "<schema name>";
    GRANT SELECT ANY TRANSACTION TO "<schema name>";
    GRANT SYSDBA TO "<schema name>";
    GRANT UPDATE ANY TABLE TO "<schema name>";
    

    If you do not perform this step, Setup grants to the following rights to the schema.

    • ALL PRIVILEGES

    • SELECT ANY DICTIONARY

    • SELECT_CATALOG_ROLE

  5. Optional. (If you do not perform this step, it will be performed by Microsoft Dynamics AX Setup.) Import the Setup stored procedures. You can find the Setup stored procedures on the Microsoft Dynamics AX DVD, in the Support folder, OracleCreateServerSessions and OracleCreateUserSessions. The stored procedures have been wrapped.

Configure rights outside of Oracle

On the computer that runs Oracle, the Oracle DBA must:

  1. Enable Windows remote authentication. Add the following entry to the SQLNET.ORA file.

    SQLNET.AUTHENTICATION_SERVICES = (NTS)

  2. If some users that log in from clients are not on the same domain as the database, you must also set REMOTE_OS_AUTHENT to true, and restart the Oracle service.

Install the Oracle client

On the computer that will host the AOS instance, the Oracle DBA must:

  1. Install an Oracle Database Client (10g release), Administrator version.

  2. If your system uses a TNSNames connection, open the TNSNames.ora file, add the following statements to it, and then save the file:

    
                        DatabaseName =
        (DESCRIPTION =
            (ADDRESS = (PROTOCOL = TCP)(HOST = serverhostname)(PORT = portnumber)
        )
        (CONNECT_DATA =
            (SERVER = DEDICATED)
            (SERVICE_NAME = databasename)
        )
    )
    

The following steps are performed by a Microsoft Dynamics AX administrator.

Run Setup to connect the AOS to the Oracle database

  1. Log on with the installing user account that the Oracle DBA provides.

  2. If you have not done so already, insert the Microsoft Dynamics AX DVD into your drive. If the Microsoft Dynamics AX Setup Wizard does not launch automatically, double-click the Autorun.hta file in the root directory of the DVD.

    If you are installing from a network location, share the installation files and connect to the location from the computer on which you want to install the program.

  3. To begin the installation process, click Microsoft Dynamics AX.

    On the Prerequisites check page, Setup validates that the software required to install Microsoft Dynamics AX is present. If it is not, click Install. To continue after the update completes, click Next.

  4. On the Welcome page of the Setup Wizard, click Next to continue.

  5. On the License agreement page, read the license agreement and then click I accept the terms in the license agreement to accept the licensing terms and conditions. Accepting the license agreement activates the Next button. To continue, click Next.

  6. On the Select installation type page, click Custom installation, and then click Next.

  7. On the Create an instance of Application Object Server page, in the Application Object Server name box, enter a name for this AOS instance.

  8. Optional: To send information about any fatal error in an AOS instance to Microsoft, select the Automatically send information about fatal errors in any Application Object Server service instance to Microsoft check box.

    If you enable error reporting, information is sent over a secure (https) connection to Microsoft, where it is stored with limited access. Microsoft uses the reports only to improve Microsoft Dynamics AX, and treats all information as confidential.

  9. On the Select account for the Application Object Server page, choose whether to use the Network Service account of the local computer or a domain account for the AOS account, and then click Next.

    If you choose to use a domain account, before you install, work with a System Administrator to have a new account created solely for use by the AOS instance. We recommend that the account be set up as follows:

    • Log on as a service

    • No interactive logon rights

    Depending on the other roles that you have selected, Setup grants the following permissions for the AOS account:

    Role

    Permissions granted

    AOS (database must exist)

    Adds the AOS account to the database as a user, and makes it a member of the db_ddladmin, db_datareader, and db_datawriter database roles.

    Grants the user execute rights on the OracleCreateServerSessions and OracleCreateUserSessions stored procedures.

    AOS (application files must exist)

    Grants the AOS account Full Control permissions on the application files directory.

    Application integration (AIF) Web services,

    Grants the AOS account Full Control permissions on the AifWebService share, if the AOS is installed at the same time as the AIF Web services.

  10. On the Select database type page, select Oracle database server, and then click Next.

  11. On the Connect to Oracle database server page, select the connection type you plan to use.

    • If you select Connect using a net service (TNS), type in the service name.

    • If you select Connect using custom settings, type in the host name, database service name, and TCP/IP port to connect to.

  12. Enter a schema (user) name and password to use to connect to the database. If you enter a schema name that does not already exist, Setup creates it for you.

  13. On the Ready to install page, review the summary of roles for your computer. To proceed, click Next.

  14. On the Installing page, you can monitor installation progress as Setup proceeds. At this point, Setup performs these actions on the computer that runs Oracle:

    • Grants the AOS account Full Control on the Oracle installation directory.

    • Runs a script that creates a schema, if it does not already exist.

    • Creates session persistence stored procedures.

  15. On the Completing Microsoft Dynamics AX Setup page, you can review the summary of roles and components for your computer. To exit the Setup wizard, click Finish.

  1. Verify that the AOS instance has started:

    • Open the Windows Event viewer on the AOS computer (Start > Administrative Tools > Event viewer).

    • To determine when the AOS has started, wait for the message "Object Server AOSname: Ready for operation."

  2. After the AOS instance has connected, start a Microsoft Dynamics AX client.

  3. Complete the installation checklist. For more information, see Installation checklist.

You can install multiple Microsoft Dynamics AX databases on an Oracle system by creating each database under a different schema.

Show:
© 2014 Microsoft