|
Вот более конкрентно про master.aoc
Create a master@.aoc file.
Fix your network problems regarding latency
When running in a 3-Tier environment we need the best performance possible. This is why we have made it possible to create a preconfigured cache file.
When running a 3-Tier Damgaard Axapta 2.5 client, we will cache different object as we use the application. All objects are cached in the memory on the client machine. When the client is shutdown, the cache objects are written to disk, in a file with the extension .aoc (Axapta Object Cache). The next time a user starts the client, the executable ax32.exe checks for the .aoc file and if one exists it is loaded into memory. This gives us a performance gain, as we do not have to cache these objects again.
How do we create the preconfigured cache file? This is very simple, we configure a 3-tier client and go through the parts of the application the all client will use e.g. General Ledger, Sales Order and Accounts Receivable. Doing this will create an .aoc file, with the following naming convention.
- ax_AOS Instancename@Hostname_username.aoc
Using an example of the environment that we have configures in the workshop, you can locate an .aoc file on your hard drive called.
- ax_Cust01@aos-course_Admin.aoc
You should be aware that the naming convention of the .aoc file is different if you have configured an Object Server Cluster e.g.
- ax(clustername)username.aoc
Any of the above files, if used as the preconfigured cache file, must be renamed to master.aoc.
When installing the Damgaard Axapta 2.5 Client software, the setup.exe program will look for the master.aoc file in the directory where setup.exe is located. After completing the installation of the client, the setup.exe program will, if a master.aoc file exists, copy this file to the \Log directory, located in the default directory structure of the installed client.
What is the functionality? When a user starts the client software for the first time, the executable ax32.exe, will look for a cache file that belongs to the user, which is currently logging in. If one exists then this cache file is loaded into memory. If none exists, then the ax32.exe will look in the \Log directory fore the master.aoc file, if one exists, the objects in this cache file are loaded into memory.
We will now create a master.aoc file and use this file with the Damgaard Axapta WebDeploy Utility. We will verify that the master.aoc file is in fact located in the \Log directory and we will test that this .aoc file is actually used as described above.
The following steps will cover all that is necessary to complete the above-described test.
1. Locate and delete all .aoc files on your server.
2. Configure a 3-tier client to connect to the Cust01_live_ax25sp0 Object Server instance.
3. Start Damgaard Axapta and access different parts of the application. This will cache objects in the memory of your workstation.
4. Shutdown the client and locate the .aoc file created. Copy this file to a directory named D:\Damgaard\Cust01_Live_master_aoc and rename the file to master.aoc
5. Copy the master.aoc file to the AxSetup folder created for the Web Deployment Utility.
6. Remove all installed clients from your Server, do this via. the Add/Remove programs icon under Control Panel.
7. Web deploy a client to your server. When the installation program has ended, verify that you do have a master.aoc file located in the \Log folder.
8. Start Damgaard Axapta and notice the performance gain.
9. Exit Damgaard Axapta and locate all .aoc files on your Server. As you can see, you now have 2 .aoc files, one is the master.aoc and the other belongs to the user that has just been logged into the application.
Creating the master.aoc file should be considered a very important task. It is necessary to know what types of users we have on a given system, to create the master.aoc file best suited for the work that our users will perform.
|