HeroEngine Publish
From HEWIKI
(Difference between revisions)
(removed reference to Bflat) |
(→Verification) |
||
| Line 126: | Line 126: | ||
| Login to clean test using [[HeroBlade]] || | | Login to clean test using [[HeroBlade]] || | ||
|- valign="top" | |- valign="top" | ||
| − | | Select the Client GOM <br>''Open the | + | | Select the Client GOM <br>''Open the Console Window'' to access the [[CLI]]|| |
|- valign="top" | |- valign="top" | ||
| Enter "<tt><nowiki>|recompileallscriptsbytecode </nowiki></tt>" as a [[CLI]] command<br>''This may take a few minutes'' || | | Enter "<tt><nowiki>|recompileallscriptsbytecode </nowiki></tt>" as a [[CLI]] command<br>''This may take a few minutes'' || | ||
Revision as of 19:16, 9 November 2012
HeroEngine Publish (also called HE Publish) is the set of tools (HEPublishBuilder and HEPublishApply) that provide the ability to build and deploy publish packages. These tools are used by the HeroEngine team to assemble updates to the DOM/GOM that are components of a new release, they are not intended for use by licensees.
To follow the steps on this page, you need access to certain tools, which can be downloaded from the MMO Platform downloads page:
- Master Control Console
- HE Publish Builder
- HeroBlade
- Oracle tools, such as 10.2G These are not available via HeroEngine, you must already have them on your side.
Information needed from your Development Director:
- Local hard-drive path for storing the publish packages
- Package version number
- Package hotfix number
- Package type (MAJOR, MINOR, or HOTFIX)
- Source fsService world name (for this example, we use HJ_DEV)
- Source fsService database Schema names (for this example, we use DEV_SERVER_GOM, DEV_CLIENT_GOM, and DEV_REPOSITORY)
- Destination fsService world name (for this example, we use CLEAN_TEST)
- Destination fsService database Schema names (for this example, we use CLEAN_SERVER_GOM, CLEAN_CLIENT_GOM, and CLEAN_REPOSITORY)
- fsService login account name and password
- fsService Schema name and password
- fsService database name
HeroEngine Publish also uses a GNU LGPL licensed compression program called 7-zip to compress its publish packages. 7-Zip binaries and source code may be found at http://www.7zip.org.
| Shutdown Clean_Test in Master Control |  
|
| Open HE Publish Builder It is a separate application, which can be accessed via your Start Menu. If you do not have it installed yet, you can download it. |
|
| Select New... from Package | 
|
| Define the New Package: a. Enter a directory on your local harddrive to store the files or accept default; b. Enter current version and hotfix numbers; c. Select package type; d. Click OK. |
|
| Verify the Distribution Packages, and that the numbers are correct. Also review the messages in the Build Process Output window, to ensure that there are no errors. |
 
|
| Select the Source Configuration Strings from the Master Control | 
|
Enter Service Database connection information
|
|
The World Schema Selection Dialog is opened
|
|
| If the DEV_SERVER_GOM, DEV_CLIENT_GOM and DEV_REPOSITORY Schemas do not exist, they must be added. For information on how to do this, see Adding schemas during HeroEngine Publish | 
|
| If the HJ_DEV World does not exist, it must be added. See Adding worlds during HeroEngine Publish | 
|
| Select the HJ_DEV world by double-clicking it, or single-clicking it then pressing OK | 
|
| Review HJ_DEV's information to ensure that you have selected the correct schemas and names. Any wrong information must be corrected by re-entering the Master Control Connection, deleting incorrect entries and re-entering correct information. | 
|
| Select DOM Tab | 
|
| Generate Server DOM Database This may take a couple minutes, wait until it no longer says Busy at the bottom of the HE Publish Builder window |
|
| Validate Server DOM Database | 
|
| Generate Client DOM Database This may take a couple minutes, wait until it no longer says Busy at the bottom of the HE Publish Builder window |
|
| Validate Client DOM Database | 
|
| Select Repository Tab | 
|
| Generate Repository Database This may take a couple minutes, wait until it no longer says Busy at the bottom of the HE Publish Builder window |
|
| Validate Repository Database | 
|
| Finalize the package. This bundles all necessary files into a single self extracting archive named the same as your package file. This may take a couple minutes, wait until it no longer says Busy at the bottom of the HE Publish Builder window |
 
|
| Launch the self extracting package executable | 
|
| Confirm that you wish to install the HeroEngine package | 
|
| After the package is extracted HEPublishApply automatically launches and detects the Hero Engine package file. | 
|
| Press the "Update World" button | 
|
Enter Service Database connection information
|
|
| The World Schema Selection Dialog is opened |
|
| If the CLEAN_SERVER_GOM, CLEAN_CLIENT_GOM and CLEAN_REPOSITORY Schemas do not exist, they must be added. See Adding Clean Schemas |
|
| If the CLEAN_TEST World does not exist, it must be added. See Adding worlds during HeroEngine Publish |
|
| Select the CLEAN_TEST world by double-clicking it, or single-clicking it then pressing OK. World alteration preparations now begin. This may take a couple minutes, wait until it no longer says Busy at the bottom of the HE Publish Builder window |
|
| You will now be queried as to which parts of the package to apply. Check with your Dev Director as to which parts need to be applied, or simply select ALL which will automatically check all boxes. | |
| When preparations are complete, select OK to apply alterations to the CLEAN_TEST server. | 
|
| When Ready (no longer busy), Close HE Publish Apply |
Verification
If you want to verify the publish:
- Note: The CLEAN_TEST world name is being used here only for example purposes, and will probably be different to what you will be using for your own system
| Recursively Watch GAME under CLEAN_TEST in Master Control In the Master Control Console, right-click on the CLEAN_TEST world, and select Watch/Recursive |
|
| Clear the logging window Right-click on the logging window in the Master Control Console, and select CLEAR |
|
| Fireup CLEAN_TEST | |
| Login to clean test using HeroBlade | |
| Select the Client GOM Open the Console Window to access the CLI |
|
| Enter "|recompileallscriptsbytecode " as a CLI command This may take a few minutes |
|
| When done (Master Control Console will say Finished Recompiling in the Logging Window), enter "HSCS recompileallscriptsbytecode" as a CLI command | |
| When done (Master Control Console will say Finished Recompiling), copy the Logging window in Master Control Console to a text editor | |
| Search for "Request 0" to identify extraction and compile errors | |
| If there are any errors, the identified HSL script needs to be repaired, probably by your local GameMasters. After the fix, this entire publish package needs to be restarted from step #1 Lather, rinse, repeat, until there no further errors. |
Next steps
Once you have received the new version of HeroEngine, you must upgrade the executables running on your world. For a full licensee, this means running the Deploy. For a source licensee, this means compiling the new source code, and deploying it.
See: Upgrading worlds
