Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 5

BXS Generation

There are two ways we can do this

#1 We get the log files instead of the DB itself.

(a) The RawDataReader utility will run and go into the DB and start the process of inserting records.
(b) Afterwhich BXS will get generated.

#2 We have DB backups from TAKION, SOFI we can generate BXS files are restoring the DB’s.

(a) DB restoration will need to be done which is a pre-requisite for GenerateReportRecord utility to
run successfully.
BXS GENERATION STEPS

1. Connect to AWS Server (IP: 54.184.14.162)


2. Go to partition D and follow the below steps
D:\File Execution Automation MultiArgument Updated\File Execution Automation
MultiArgument Updated
Here we select the utility “BXSFileAutomation.exe”

3. This will open the utility that will process DB’s and generate the BXS files we need.
4. Next, we need to move to selecting the DB’s which is a separate process.

SELECTING DB’s:

1. Now we select the DB so the utility can process it and provide the relevant files.
2. We can select the DB’s from the below location:
D Drive >> Archives >> DB_Archives
3. Now for whichever IMID we need to generate BXS we will pick those DB’s.
For example if we want to work on QNTX then we will follow the below path: D Drive >>
Archives >> DB_Archives

BSX Utility:

1. Once we select the DB or DB’s it will do a 2-step process, restore the DB and run the EOD
process after which the BXS files are generated.
2. When the utility runs it shows consolidated logs, the EOD logs don’t get shown separately.
3. When the utility starts it will restore the DB and start the EOD process then the utility will go in a
hold state till the EOD process completes or fails.
4. In case the EOD process for a particular DB breaks the EOD process will stop and close, after
which the utility will go from hold state as previously mentioned and start working on the next
DB backup and start the processes for that.
5. Manual monitoring is required by the user to ensure the utility is carrying out the required
operations successfully incase it doesn’t there are ways to troubleshoot which will be discussed
later in this document.

Working on the BXS Utility:

1. The BXS Utility has certain parameters that need data for it to work.

2. Some information needed can be acquired from the CONFIG file, which is located on the below
path
Disk Drive ‘D’ >> EOD Processes 3.0.0.0 >> EOD Process.exe.config

(A) Database Name: It is the name of the DB which would be restored.

*Restoration of DB will be done but it will be the name that been set in the EOD process.

* In the CONFIG file head to the sub section “ConfigurationDatabase” here you can check the relevant
DB name

(B) Server Name: The name of the server can be picked from the sub section “Data Source” of the
CONFIG file.
(C) User ID: Since AWS SQL Server is locally run so we can leave this as blank.

(D) Password: We don’t need to input a password as the AWS SQL Server is locally run so we can leave
this as blank.

(E) EOD Argument: It is the value we need to input for the utility to know for which IMID BXS files are
needed, example: BSX(IMID) where IMID can be VCVT, VCVU, QANT, QNTX, etc.

(F) Next step is to press “Select Exe” it will open a file explorer window where we need to select the
executable “EODProcess.exe”
s

You might also like