Axapta3 Installation(SP4)

Axapta3 Installation(SP4)

原贴地址：http://fyhbs.com/Library/Axapta30/Configuration/Library_AX30Config.html#EX001
MBS Axapta Version 3.0 Installation and Configuration Library

1) Axapta 3.0 Client Installation
2) Axapta 3.0 Service Pack 4 Client Installation (Upgrade Version)
3) Axapta 3.0 Client Configuration
4) Axapta 3.0 ODBC data source Configuration (SQL Server)
5) Axapta 3.0 Application Installation
6) Axapta 3.0 Service Pack 4 Application Installation (Upgrade Version)
7) Axapta 3.0 Object Server (AOS) Installation
8) Axapta 3.0 Service Pack 4 Object Server (AOS) Installation (Upgrade Version)
9) Axapta 3.0 Service Pack 5 Object Server (AOS) Installation (Upgrade Version)
10) Axapta 3.0 Master AOC File
11) Axapta 3.0 Command Line

Axapta 3.0 Client Installation

1. Insert Axapta 3.0 CD, and Select Individual Install, and then click "Client"
2. Click "NEXT" on Welcom page
3. Check on Accept the terms in the License agreement option, select the country,
   and then click "NEXT"
4. Key in customer information, Select any one who use this computer option,
   and then click "NEXT"
5. On Setup Type page, chose "Costomer", and then click "NEXT"
6. On Custom Setup page, click "Change" button, and then change the Axapta clinet
   folder name. For example : "C:\AX30CLIENT".
7. On Client Type Page, select 2-tier or 3 tier.
   For 2-tier configuration, it need type in Axapta application's path.
   For 3-tier configuration, it need type in Axapta Server name or IP address and Axapta Object Server (AOS) name, default is "axapta".
8. Click "NEXT", and "Install" button to start Client Installation.
9. Click "Finish"

Click Here To see Axapta 3.0 Client Installation Steps in GUI mode.

Axapta 3.0 Service Pack 4 Client Installation (Upgrade Version)

1. Insert Axapta 3.0 Service Pack 4 CD, Click Installation, and then click Client
2. Click "NEXT" on Welcom page
3. Check on Accept the terms in the License agreement option, select the country, and then click "NEXT"
4. On the Destional Folder page, click "NEXT"
5. Click "Install" Button to start installation
6. Click "Finish"

Click Here To see Axapta 3.0 Service Pack 4 Client Installation Steps in GUI mode.

Axapta 3.0 Client Configuration

1. Start Client Configuration Utility
   Path: Start --> Programs --> Axapta Configuration Utility
2. For setup a new configuration, click Manage Button, and then New Configuration
3. On the New Configuration window, type the name of configuration.
   For example: AX30CLI (Axapta 3.0 Client) Based on situation, you can select copy from active configuration or from original configuration, and then click OK
4. On the General Tab, put the start company, for example : dat
5. On the Client Tab, you can select thin client or Fat client.
6. Click Setting to setup connection
7. On the Connect Settings, you need to setup AOS server name and AOS host server name It will be able to use host server's IP address, instead of using host server's name.
8. Click OK, and then OK to finish setup

You can have multi client configuration for login to different system and layer

Click Here to view Client configuration steps in GUI mode.

Axapta 3.0 ODBC data source Configuration (SQL Server)

Use windows data source administor to setup client ODBC parameters.

1. Start data source administrator
   PATH: Start -> Control panel -> Administrative Tools -> data Source (ODBC)
2. On System DSN tab click Add Button
3. High light the data source, in this case, it is SQL Server, and then click Finish
4. Type data source name, description and then select SQL server from drop down menu
5. Chose SQL server authentication, and then put login ID and password
6. Click Client Configuration, and select TCP/IP network libraries, then click OK
7. Click NEXT, and then change default database to Axapta database.
8. Click NEXT, you can change SQL server message language here, and then click next
9. Before finish the setup, click Test Data Source button to verify if the setup is ok.
10. Click OK, and OK again to finish ODBC setup

ODBC setup only necessary if you use 2 tier or Fat Client configuration.

Click Here to view ODBC configuration steps in GUI mode.

Axapta 3.0 Install Application

1. Insert Axapta 3.0 CD, and Select Individual Install, and then click "Application"
2. Click "NEXT" on Welcom page
3. Check on Accept the terms in the License agreement option, select the country, and then click "NEXT"
4. Type in customer information, and then click "NEXT"
5. On Setup Type page, chose Costomer, and then click "NEXT" (Suggest always chose CUSTOMER)
6. On Custom Setup page, click "Change" button, and then change the Axapta clinet folder name. For example : "C:\AX30".
7. Click NEXT when finish change the folder.
8. Click "NEXT", and "Install" button to start Client Installation.
9. Click "Finish"

Click Here to view Install Application steps in GUI mode.

Axapta 3.0 Service Pack 4 Application Installation (Upgrade Version)

1. Insert Axapta 3.0 Service Pack 4 CD, Click Installation, and then click Application
2. Click "NEXT" on Welcom page
3. Check on Accept the terms in the License agreement option, select the country, and then click NEXT
4. On the Destional Folder page, click NEXT
5. On the Select upgrade type page, Select Upgrade from Axapta 3.0 and then click NEXT
6. Click "Install" Button to start installation
7. To start installation, you have to stop AOS, If AOS is still running, it will pop up a page to ask you stop AOS. Click OK after you stopped AOS.
8. Click "Finish"

Click Here To see Axapta 3.0 Service Pack 4 Application Installation Steps in GUI mode.

Axapta 3.0 Object Server (AOS) Installation

1. Insert Axapta 3.0 CD, and Select Individual Install, and then click Server
2. Click NEXT on Welcom page
3. Check on Accept the terms in the License agreement option, select the country, and then click NEXT
4. On the Customer Information page, Type in User Name and Organization name,and then click NEXT
5. On Setup Type page, chose Costomer, and then click NEXT
6. On Custom Setup page, click "Change" button, and then change the Axapta clinet folder name.
   For example : C:\AX30\AOS.
7. On the Axapta Application Page, chose the Axapta Application folder here.
   Forexample: C:\AX30
8. On the Active Directory Integration Page, setup if you want AOS to integrate with active directory or not.
9. On the database setup page, type in database parameters:
   For example: data source, Server, database, user ID and Password
   Click NEXT when you fill in all these information
10. Click Install button to start Client Installation.
11. Click Finish

Click Here To see Axapta 3.0 Object Server Installation Steps in GUI mode.

Axapta 3.0 Service Pack 4 Object Server (AOS) Installation (Upgrade Version)

1. Insert Axapta 3.0 Service Pack 4 CD, Click Installation, and then click Axapta Object Server
2. Click "NEXT" on Welcom page
3. Check on Accept the terms in the License agreement option, select the country, and then click "NEXT"
4. On the Destional Folder page, click "NEXT"
5. Click "Install" Button to start installation
6. Click "Finish"

Click Here To see Axapta 3.0 Service Pack 4 Object Server Installation Steps in GUI mode.

Axapta 3.0 Master.AOC File

To speed up opening of form you could create a master.aoc file and place it were the Ax32.exe resides. The master.aoc file can be created by changing one of personal aoc files. This cache file is created in your profile when you logoff from Axapta. Just rename it to master.aoc. The trick is to enter all nessasary forms of which will perform badly, and then use the created cache file. Everytime the kernel is loaded it will look for this file. Remember to create a new master.aoc file everytime you make changes to your cached object. for example if you change a form.

user AOC file can be find under:
C:\Documents and Setting\user\Local Setting folder.

Axapta Command Line


Following are Axapta Command line parameters and its description

-allowunauth
When using Windows Authentication, this option enables users that do not pass the authentication process to be allowed logging in using user name and password (traditional Axapta logon sequence). If not enabled, users will be rejected if not authenticated.

-aol="s"
aol is an acronym for Application Object Layer. Valid layers are:
sys, syp, gls, glp, dis, dip, los, lop, bus, bup, var, vap, cus, cup, usr and usp.

-aolcode="s" Access code for aol.

-aos=host:port
Connect to the AOS running at given port number on specified host. Host is either a DNS hostname (for example server1.damgaard.com) or an IP address (192.88.253.41). The port number is the number specified for the AOS instance that should be connected to. No instance name needs to be specified because only one instance can be running at a given port on a given machine. Using this option will connect the client directly to the AOS using TCP traffic only and bypass the initial search for the AOS and thereby eliminates the need for networking that supports UDP traffic. This eases firewall configuration and NAT appliances

-aos=instance@host
Connect to the specified AOS instance running at the specified host machine. Instance is the name (for example 'Axapta'), and host is DNS name or IP address of the machine running the AOS. Specifying -aos=MyAOS@MyHost equals setting -servermask=MyAOS and -internet=MyHost (or specifying these in corresponding fields on the server tab in the Configuration Utility).

-aos=ad("adsn")
Use Active Directory integration. "adsn" is the "Active Directory Server Name to search the Active Directory for. Same as "By name - find a specific AOS" in the Axapta Configuration Utility

-aos=adbrowse
Use Active Directory integration. Search the Active Directory for "Active Directory Server Names" in User objects and Organizations Units. Same as "By organization - browse for per-user or per-organizational specific AOS" in the Axapta Configuration Utility.

-aos=ad
Use Active Directory integration - search the Active Directory for any AOS. Same as "Simple - find any AOS" in the Axapta Configuration Utility

-applexclusive
The application files are opened in exclusive mode. Note applexclusive" and applshare cannot both be given. If you do give both, the one given last on the command line will take effect. You will not get any error messages.

-application=s
Specify the name of the Axapta application. Default: Standard

-applshare
The application files are opened in shared mode. This is default. Note applexclusive" and applshare cannot both be given. If you do give both, the one given last on the command line will take effect. You will not get any error messages.

-broadcast= xx.xx.xx.xx
Specify a broadcast address to be used in CLIENT mode. A request is sent to all the broadcast addresses to obtain identification of the available application servers. The address consists of four decimal values between zero and 255 separated by dots.

-bwsim=speed:latency
where speed states the bandwidth simulated (in bytes per second). The latency is specified as a number designating number of ms spent for communication round trip (the fixed overhead (time used) the network applies to sending a package to the server and receive one back). To verify....

-client
Connect to an AOS and run as a three-tier thin client. Use -aos= to specify which AOS.
client = thin : Connect to an AOS and run as a three-tier thin client.
Use -aos= to specify which AOS.
client = fat : Connect to an AOS and run as a three-tier fat client.
Use aos= to specify which AOS.

-company=s Select initial company s. Default: dat

-connectionidletimeout=seconds
Set the time in seconds to leave an idle database connection open before closing it. Shorter idle time will decrease database server and Axapta memory usage, but will potentially cause time-consuming re-logins on the fly. Default: 60 seconds is the default for Microsoft SQL Server, 30 minutes the default for Oracle.

-createdsn=microsoftsqlserver or-createdsn=oracle
Have the data source created automatically in the ODBC manager.

-createdsn_tcpipport=integer
TCP/IP port number required for Oracle. This parameter is relevant only when
-createdsn=oracle is given. The parameter is ignored if given with
-createdsn=microsoftsqlserver.

-database=s
Use database s when connecting to the database server. Default: The default option is to use the database set in the ODBC driver.

-dbcli= [ODBC]|[OCI]
Runs Axapta in either ODBC or OCI mode. -DBCLI=ODBC is the default.

-dbserver=s
Use server s during login. Default: The default option is to use the server set in the ODBC driver.

-dbunicodeenabled=0 | 1 Initialize database for Unicode

-directory=s Specify the Axapta root-directory.

-doclanguage=s
Use this option if you would like to have the documentation in a different language than the one used in menus and dialogs.
Example:
-doclanguage=da : will give you the documentation in Danish.
Default: The default is that the documentation language is identical to the language used in the system. This is set by the -language option.

-dsn=s
Use ODBC driver data source s. Default: BMSDSN

-featurekeysystem
The 3.0 security system is ON by default.Use this parameter to enable the old featurekey system.
-fetchahead=n A maximum of records retrieved from the database at a time. Default: 100

-hint=n
Apply database dependent SQL hint(s). Default: Empty for default settings.

-internal=relaxedsyntax The 3.0 kernel defaults to strict X++ syntax checking.
For relaxed syntax checking, use this parameter to ease restrictions.

-internet=s
Specify an Internet address to be used in ?client mode. A request is sent to all the Internet addresses to obtain identification of the available Object servers.

-job=s
Run external job s prior to any other database-related action during startup.
Default: The default is not to run a job.

-language=s
Select language s for the user interface. Default: Language must be selected during setup.

-log=s
Name the SQL error log file (may include a full drive and path specification).
Default: trcAxaptaError.log in the standard Axapta log-directory.

-logdir=s
Use an alternative directory for the log files generated when you compile, import or export in Axapta. Default: The default is that the log files are generated in the Log folder.

-noauto
Use this parameter to bypass system related application calls made by the Axapta kernel. This includes the ability to bypass startup code, and some timer based calls. This parameter will allow you to startup Axapta in order to fix problems that were introduced in the application code. Normally these problems would prevent you from starting Axapta. For example, if code is introduced in the startup method that causes Axapta to go into infinite loop, and therefore, never finishes the startup procedure, . To change this, start with the ?NOAUTO switch, correct the code and restart without the ?NOAUTO to have the startup code included again.

-opencursors=n
A maximum of n database cursors are kept open per connection for cursor reuse.
Default: 90 cursors

-port=integer : TCP port for the AOS

-preloadthresholdmsec=milliseconds Time used for preloading.
For example, -preloadthresholdmsec=3000 results in the issue of a warning whenever preloading exceeds 3000 milliseconds. This value can not be specified per user in Tools, Options, SQL, Warnings. This threshold is only activated when warnings are enabled.
-preloadthresholdrecords=records Number of records preloaded.
For example, -preloadthresholdrecords=300 results in the issue of a warning whenever preloading exceeds 300 records. This value can not be specified per user in Tools, Options, SQL, Warnings. This threshold is only activated when warnings are enabled.

-querytimelimit =[table:][milliseconds]
Save queries running longer than a given number of milliseconds to file. If the value of QuerytimeLimit is zero (0), which is the default, no queries are logged. This parameter supports directing output to a table, i.e. SysTraceTable (default is disk-file). Use -QuerytimeLimit=ms for tracing all SQL statements exceeding the ms milliseconds threshold and -QuerytimeLimit=table:ms to do the same to table.

-regconfig=name Use a Registry configuration called name.
A configuration can be created using the Axapta Configuration Utility.

-regimport=file name Import a configuration to the Registry.
The import is performed prior to the evaluation of any other options. This means that you can import a configuration using ?regimport and then select it using ?regconfig.

-repair
Any non-zero value will force a re-synchronization of SQL system tables during startup. The use of this command-line parameter is logged in the Event log. Use this option to handle situations when problems in SQL system tables prevent Axapta from starting, for example missing indexes.

-retry=n
Delay in seconds before re-executing after a deadlock. Default: 5 seconds

-securityprovider=s
Selects the security provider to use with Windows Authentication and is only relevant for Object Server configuration. For AOS running on Windows NT the only valid option is "NTLM" which provides authentication based on the NTLM security provider. For Windows 2000 systems 'Kerberos' is also a valid security provider. For Windows 2000 networks with solely Windows 2000 servers and clients 'Negotiate' is also an option. This will elect the best suitable security provider automatically.

-serveridletimeout=seconds
Specifies how long (in seconds) the AOS instance should be allowed to be running without servicing clients. When this timeout expires without having clients connected, the instance will be shut down automatically. This option is well suited to be combined with setting instance startup mode to OnDemand making the server auto-start upon request from client and shutdown when no clients need service for at given amount of time.

-servermask=s
Specify the mask s for selecting a subset of object servers when running in CLIENT mode. if this option is not specified, and multiple object servers are found, all available object servers will be presented in a selection box.

-share
Share label and identifier files between several applications. if not specified, the files will not be shared.

-singleuser
Run the program in single user mode.

-sqlbuffer=n Set the upper limit in Kbytes of the fixed internal data retrieval buffer. Default: 24 Kbytes

-sqlcomplexliterals=n
About literals and placeholders. Setting sqlcomplexliterals to the value 1 enables this feature, the value 0 disables this feature.

-sqlformliterals=n About literals and placeholders.
Setting sqlformliterals to the value 1 enables this feature, the value 0 disables this feature.

-sqloraclefirstrowsfix=n
Oracle Versions 8.05, 8.06 and 8.15 occasionally selects a poor query plan for queries using the Axapta keyword firstFast row. The symptom is that an index matching the order by specification is preferred, even though another index much better serves the where part and the number of rows returned is small. Axapta includes a workaround for this problem, which you should only enable if you have verified that the above problem is the cause for poor performance. The Axapta Query Analyzer can be used for detecting this. A value of 1 enables this work around, a value of 0 disables this feature.

-sqlparm=s
Add additional parameters s upon database login. The format follows the ODBC standard: key1=value1;key2=value2. An example: DIR=c:\db;ID=9. Default: The default is no additional parameters.

-sqlpwd=s
Use password s upon login to the SQL database. Default: bmssa_pwd

-sqltrace[=Table]
Invoke SQL statement tracing to log file or table. Use -sqltrace for tracing all generated SQL statements to file and -sqltrace=table to do the same to table. Default: No tracing.

-sqluser=s
Use user name s during login to the SQL database. Default: bmssa

-startupmsg=s
Text to be displayed during Axapta startup.

-startupcmd=MyCommand
A string that is passed to Axapta and can be used to have your own startup commands executed. The string is passed in the calls appl.startup(MyCommand) info.startup(MyCommand) appl and info are instantiated objects of the application classes Application and Info respectively. The application classes are inherited from the system classes xApplication and xInfo. Learn more in the Developer's Guide. You can access the guide from Axapta's Help menu.

-useis Use integrated security during SQL database login
and thus disabling values set by using parameters sqluser and sqlpwd.

-user=s Log on as user s.

-useserverprinters
Have the client direct all printing to the printer connected to the server.

-warnings[=table]
Enable various run-time warnings which are logged to a file, or table. Use -warnings to trace all developer warnings to file and -warnings=table to trace all warnings to a table. Default: No warnings.

-windowsauth={0|1}
This option disables/enables Windows Authentication which, when enabled, is providing Single Sign-On and Authentication of client machine account and the user logging in.

posted on 2007-12-03 17:07 Jacky Xu 阅读( ...) 评论( ...)   编辑 收藏

转载于:https://www.cnblogs.com/JackyXu1981/articles/981276.html