AX7: Install a deployable package
Table of Contents
Introduction
This tutorial walks you through the steps for applying a deployable package on a system. This package can be either a binary hotfix for Application Object Server (AOS) or a deployable package that was created in your development environment.
This article describes the process using the command line and requires remote access to the environments. On the other hand, and in most cases, you can apply a deployable package to an environment directly from Dynamics Lifecycle Services (LCS) as described in Apply a deployable package on a system, without the need to understand the process described on this page.
Key concepts
- Deployable package – A deployable package is a unit of deployment that can be applied in any environment. It can consist of a binary hotfix to the AOS runtime components, an updated application package, or a new application package.
- AXUpdateInstaller – A deployable package has the installer executable bundled in it. When the package is downloaded to a computer, the installer is available.
- Runbook – The deployment runbook is a series of steps that is generated for applying the deployable package to the target environment. Some of the steps are automated, and some are manual. AXUpdateInstaller provides the capability to run these steps one by one and in the correct sequence.
Collect topology configuration data
- In Microsoft Dynamics Lifecycle Services (LCS), open the Environment page.
- Click the name of a virtual machine (VM), and establish a Remote Desktop connection to the VM by using the user name and password that are provided on the Environment page.
- On the VM, download the zip file for the deployable package from LCS. Note: After you download the zip file, right-click it, and then select Properties. Then, in the Properties dialog box, on the General tab, click Unblock to unlock the files. Finally, extract the files, and continue with the next step.
- In the folder where the deployable package was extracted, find and open the file that is named DefaultTopologyData.xml. You must populate this file with the VM name and installed components.
- To populate the VM name, follow these steps:
- Open Windows Explorer, right-click This PC, and then select Properties.
- In the system properties, find and make a note of the machine name (for example, AOS-950ed2c3e7b).
- In the DefaultTopologyData.xml file, replace the machine name with the name that you found in the previous step.
- To populate the installed components, follow these steps:
- Open a Command Prompt window as an administrator.
- Navigate to the extracted folder, and run the following command to see a list of all the installed components on the computer.
AXUpdateInstaller.exe list
- Update the DefaultTopologyData.xml with the list of components.
When you’ve finished populating the VM name and installed components, the DefaultTopologyData.xml file should resemble the following illustration.
- To populate the VM name, follow these steps:
- Repeat steps 2 through 4 for each VM that is listed on the Environment page.
Generate a runbook from the topology
Based on the topology information in the DefaultTopologyData.xml file, you must generate the runbook file that will provide step-by-step instructions for updating each VM.
- On any VM, run the following command to generate the runbook.
AXUpdateInstaller.exe generate –runbookid=[runbookID] –topologyfile=[topologyFile] –servicemodelfile=[serviceModelFile] –runbookfile=[runbookFile]
Here is an explanation of the parameters that are used in this command:
- [runbookID] – A parameter that is specified by the developer who applies the deployable package
- [topologyFile] – The path of the DefaultTopologyData.xml file
- [serviceModelFile] – The path of the DefaultServiceModelData.xml file
- [runbookFile] – The name of the runbook file to generate (for example, AOSRunbook.xml)
Example
AXUpdateInstaller.exe generate -runbookid="VAL200AA2BMEDIU-runbook" -topologyfile="DefaultTopologyData.xml" -servicemodelfile="DefaultServiceModelData.xml" -runbookfile="VAL200AA2BMEDIU-runbook.xml"
The runbook provides the sequence of steps that must be run to update the environment. The following illustration shows an example of a runbook file. Each step in a runbook is associated with an ID, a machine name, and step execution details.
Install a deployable package
- Based on the sequence of steps that is specified in the runbook, start with the first machine that is listed.
- Follow these steps on each VM:
- Import the runbook by running the following command.
AXUpdateInstaller.exe import -runbookfile=[runbookFile]
Example
AXUpdateInstaller.exe import -runbookfile="VAL200AA2BMEDIU-runbook.xml"
- Verify the runbook.
AXUpdateInstaller.exe list
- Execute the runbook.
AXUpdateInstaller.exe execute -runbookid=[runbookID]
Example
AXUpdateInstaller.exe execute -runbookid="VAL200AA2BMEDIU-runbook"
- Export the runbook.
AXUpdateInstaller.exe export -runbookid=[runbookID] -runbookfile=[runbookFile]
Example
AXUpdateInstaller.exe export -runbookid="VAL200AA2BMEDIU-runbook" -runbookfile="VAL200AA2BMEDIU-runbook.xml"
- Import the runbook by running the following command.
- AXUpdateInstaller updates the runbook file after each step is run on a VM.
- The runbook also logs information about each step.
- For manual steps, follow the instructions, and then mark the step as completed in the runbook by using the AXUpdateInstaller.
AXUpdateInstaller.exe execute -runbookID=[runbookID] -setstepcomplete=[stepID]
Example
AXUpdateInstaller.exe execute -runbookid="VAL200AA2BMEDIU-runbook" -setstepcomplete=2
- After all the steps are completed on one machine, export the runbook results.
AXUpdateInstaller.exe export -runbookID=[runbookID] -runbookfile=[runbookFile]
Example
AXUpdateInstaller.exe export -runbookid="VAL200AA2BMEDIU-runbook" -runbookfile="VAL200AA2BMEDIU-runbook.xml"
- Log on to the second machine that is listed, and repeat steps 1 through 6 until all machines have been updated.
- If errors occur during any step, debug the script/instruction in the step, and update accordingly.
Back up the database and computer instance
- After all the services are stopped, make a backup of the database and VM snapshot manually (optional). Then run the following command to mark the backup step as completed. Supply the correct backup step ID.
AXUpdateInstaller.exe execute -runbookid=[runbookID] -setstepcomplete=[stepID]
Example
AXUpdateInstaller.exe execute -runbookid="VAL200AA2BMEDIU-runbook" -setstepcomplete=3
Update files
- After you’ve marked the backup step as completed, the next step is triggered. In the sample step, AOS packages are updated from the deployable package.
- Run the following command to verify that the new version is installed.
AXUpdateInstaller.exe list
- View the runbook to see the completed steps.
Run database synchronization
- At one point, you will see a database synchronization (DBSync) step.
Start all services
- After the database synchronization step is completed, follow the same instructions to complete the remaining steps. All the services will be started.
Troubleshooting
- After all the steps are completed, export the runbook, and save it outside the computer for future reference. For example, you might have to use the runbook file in these situations:
- You must analyze the downtime requirements for production, and so on.
- You must send the file to Microsoft in the event of failure to install a deployable package.
- If any step fails, you can rerun it by running the following command.
AXUpdateInstaller.exe execute -runbookid=[runbookID] -rerunstep=[stepID]
- To prevent version mismatch or downgrade, or installation of the same deployable package, run the following command.
AXUpdateInstaller.exe execute -runbookid=[runbook ID] -versioncheck=true
- To verify database synchronization, navigate to the aosservce\scripts\ folder and find the dbsync.error.txt file. Find the file, and look for any errors.
AX7: Install a deployable package的更多相关文章
- 在绘图的时候import matplotlib.pyplot as plt报错:ImportError: No module named '_tkinter', please install the python-tk package
在绘图的时候import matplotlib.pyplot as plt报错:ImportError: No module named '_tkinter', please install the ...
- ImportError: No module named '_tkinter', please install the python3-tk package
ImportError: No module named '_tkinter', please install the python3-tk package 先更新包,命令:sudo apt-get ...
- Centos6版本使用yum报错 Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfi Setting up Install Process No package gcc available. Error: Nothing to do
在使用Centos6版本yum时报错 Loaded plugins: fastestmirror, refresh-packagekit, securityLoading mirror speeds ...
- ubuntu下使用python3的有些库时,解决"raise ImportError(str(msg) + ', please install the python3-tk package') ImportError: No module named '_tkinter', please install the python3-tk package"的错误
问题: 在Ubuntu下使用matplotlib这个库时,运行时出现如下错误: raise ImportError(str(msg) + ', please install the python3-t ...
- sudo apt install libreadline-dev Reading package lists... Error!
luo@luo-ThinkPad-W540:~$ luo@luo-ThinkPad-W540:~$ luo@luo-ThinkPad-W540:~$ luo@luo-ThinkPad-W540:~$ ...
- You need to install the perl-doc package to use this program
You need to install the perl-doc package to use this program 解决方案:apt-get install perl-doc
- yum -y install pip No package pip available. Error: Nothing to do
centos下安装pip时失败: [root@wfm ~]# yum -y install pipLoaded plugins: fastestmirror, refresh-packagekit, ...
- Python ImportError: No module named '_tkinter', please install the python3-tk package
ImportError: No module named '_tkinter', please install the python3-tk package 这个问题的原因是使用的python3环境内 ...
- maven install与maven package 的区别
mvn install 是将你打好的jar包安装到你的本地库中,一般没有设置过是在 用户目录下的 .m2\下面.mvn package 只是将你的代码打包到输出目录,一般的是 target下面.
随机推荐
- springMVC 返回json 忽略类中属性的注解
该注解使用在 类名,接口头上 @JsonIgnoreProperties(value={"comid"}) //希望动态过滤掉的属性 该注解使用在get方法头上 @JsonIgno ...
- Python 批量修改文件名
最近下载了几部美剧(越狱.迷失.权利的游戏......),每集文件名都好长好长..想改短一些,但一个一个改太累了,于是写了个脚本来实现批量修改: 修改前文件名: 修改后文件名: 代码实现: #enco ...
- Torch 网络层 参数的初始化问题
Torch 网络层 参数的初始化问题 参考链接: https://github.com/Kaixhin/nninit 从 Torch 中自带的包,可以看到:https://github.com/tor ...
- 0.AutoMapper核心
AutoMapper是基于约定的对象 - 对象映射器.AutoMapper使用流畅的配置API来定义对象 - 对象映射策略.AutoMapper使用基于约定的匹配算法来匹配源到目标值.AutoMapp ...
- React组件生命周期过程说明
来自kiinlam github94 实例化 首次实例化 getDefaultProps getInitialState componentWillMount render componentDidM ...
- GDB详解
1 简介 2 生成调试信息 3 启动GDB 的方法 4 程序运行上下文 4.1 程序运行参数 4.2 工作目录 4.3 程序的输入输出 5 设置断点 5.1 简单断点 5.2 多文件设置断点 5.3 ...
- [PHP] - Laravel 5 的 Hello Wold
吐槽一段 整了半天,Laravel下载麻烦得可以去死.先要安装composer,而composer又被共墙了,之后又要安装git,安装完git还要注册git,等等.... 最终放弃这种玩法,太恶心了. ...
- Python不完全入门指南
适用范围: 有一定编程基础,想快速入门python的人群 说明: 使用jupyter notebook编写,可以使用nbviewer网站进行查看. Python不完全入门指南 项目放在github上, ...
- WCF服务客户端首页调用慢的问题处理
场景: WCF服务架设于IIS服务中,走TCP协议.客户端首次调用特别慢,第一次加载完后,都正常. 解决: 把服务中需要序列化的模型所在的工程 > 属性 > 生成 > 生成序列化程序 ...
- oracle ||,
|| oracle数据库中的 ||称为 "字符串连接符" 用于连接查询结果,如下: select trade_id,accept_date from A; ------------ ...