Dear All,
I am interested to apply the DPBuddy to our Auto Deploy process. I can import this follow the step in document. I have some questions hope to get your suggestion.
I want to import the package that have got from exporting from GUI like this captured image below.
And I have save it to package/DP_All_Domainl.zip
In this zip package contains 2 domains (default , TimeSereis). My question are:1. How can I export all entire system by using tag? Can I use the following command?
<target name="backup" description="Backup one or multiple domains">
<dp:backup file="backup.zip" domainPatterns="TimeSeries.*, default" appendTimestamp="true" />
</target>
2. How can I import them by using the tag target?
<target name="importall" description="Import configuration and apply deployment policy to it">
<property name="ws.port" value="5550" />
<dp:import domain=”default” file="package/DP_All_Domainl.zip" overwriteFiles="true" overwriteObjects="true" />
</target>
PS: I can only import per each domain by using 2 tags of target (e.g. <target name=”import_default> .. and <target name=”import_TimeSeries”>) but what I would like to do is to import all.
3. If deploying is failed e.g. the management interface has been replaced with the incorrect IP. So we will cannot access the management interface , right?
The question is How we rollback this?
Regards,
Noppon K.
This email was sent to you by Thomson Reuters, the global news and information company. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Thomson Reuters.
Hi Alexander,
Thanks for your quick reply. I am interested for the #3. In the past I have some problem in GUI access. While I was importing by replacing the incorrect IP on eth4 (management interface). Then the result is I could not do the next step. This means that it automatic apply what I had done, right?
I just concern that it will impact to DPBuddy cause it is using XML management interface as well. If I am wrong please correct.
I am appreciated for your help and hope to get helping in the future question JMany Thanks
Noppon K.
Hi Alexander,
Thanks for this answer. I still have more question.
In case I want to import the configuration to non-existing domain. I have tried but it returned error “Authentication error” something like this. I need to create domain myself on GUI.
Is there any way to import the configuration to non-existing or is there any command to check and creating domain before importing?
Dear All,
Error! Filename not specified.
And I have save it to package/DP_All_Domainl.zip
In this zip package contains 2 domains (default , TimeSereis). My question are:
1. How can I export all entire system by using tag? Can I use the following command?
<target name="backup" description="Backup one or multiple domains">
<dp:backup file="backup.zip" domainPatterns="TimeSeries.*, default" appendTimestamp="true" />
</target>
2. How can I import them by using the tag target?
<target name="importall" description="Import configuration and apply deployment policy to it">
<property name="ws.port" value="5550" />
<dp:import domain=”default” file="package/DP_All_Domainl.zip" overwriteFiles="true" overwriteObjects="true" />
</target>
PS: I can only import per each domain by using 2 tags of target (e.g.
<target name=”import_default> .. and <target
name=”import_TimeSeries”>) but what I would like to do is to
import all.
3. If deploying is failed e.g. the management interface has been replaced with the incorrect IP. So we will cannot access the management interface , right?
The question is How we rollback this?
Regards,
Noppon K.
This email was sent to you by Thomson Reuters, the global news and information
company. Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be the views of
Thomson Reuters.
This email was sent to you by Thomson Reuters, the global news and information
company. Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be the views of
Thomson Reuters.