data import and export

infodart INDIA TECHNOLOGY LIMITED (ITIL)

Data Import and Export Guide for Hypercity

Pratima Gupta

1/7/2011


Contents1 Introduction.................................................................................................................................3

2 Data Import from MMS into CO...................................................................................................3

2.1 Configuring data import on CO machine.................................................................................3

2.1.1 Configure ‘dataimport’ folder supplied by Infodart.........................................................3

2.1.2 Configure Back Office profile on Websphere...................................................................7

2.1.3 Configuring ‘dataimport’ to connect to stage1, stage2, BO and CO databases on Remote machine.................................................................................................................................7

2.1.4 Configure Central Office Profile on Websphere...............................................................9

2.2 Create Stores in Central Office and Back Office.......................................................................9

2.3 Running Interfaces...................................................................................................................9

2.3.1 Pre-requisites...................................................................................................................9

2.3.2 Build Jars on CO using POLL files from MMS..................................................................10

3 Exporting Data from CO to MMS...............................................................................................14

3.1 Executing StoresSales.bat to create T* files...........................................................................14

4 Export data from Central Office to Back Office..........................................................................15

4.1 Export Promotions from CO to BO.........................................................................................15

4.2 Export GV from CO to BO.......................................................................................................16

4.3 Export Parameters from CO to BO.........................................................................................16

5 Export data from Back Office to POS.........................................................................................21

5.1 Export Parameters from BO to POS.......................................................................................21

5.1.1 Configuring POS Client...................................................................................................21

5.1.2 Configuring POS Server..................................................................................................22

6 Export data from POS to CO and BO..........................................................................................26

6.1 Export Sales Transactions from POS to BO & CO...................................................................26

6.1.1 Check POS Log Queue on BO Server..............................................................................26

6.1.2 Check POS Log Queue on CO Server..............................................................................26



6.2 Export Journal from POS to CO..............................................................................................31

6.2.1 Check EJournalImport and EJournal Queue on BO Server.............................................31

6.2.2 Check EJournalImport Queue on CO Server...................................................................31


Infodart Confidential

db_config.xml

<property name="password" value="db2admin@1"/><property name="username" value="db2admin"/><property name="url" value="jdbc:db2://127.0.0.1:51000/bodb"/>



7 TroubleShooting Interfaces........................................................................................................38

7.1 Jar Not Created - SQL0668N Operation not allowed for reason code "3" on table...............38

7.2 Jar Not Created - SQL0289N Unable to allocate new pages in table space "USERSPACE1".. .38

8 Revision History.........................................................................................................................39

1 IntroductionThis guide covers various configurations required for

Importing data from MMS to Central Office Exporting Data from Central Office to MMS Exporting Data from Central Office to Back Office Exporting Data from Back Office to POS Exporting data from POS to Back Office and Central Office

2 Data Import from MMS into CO

2.1 Configuring data import on CO machine

2.1.1 Configure ‘dataimport’ folder supplied by Infodart

dataimport refers to the folder provided by Infodart.

1. Edit dataimport\build.xml Edit the value of property <property name="java.home.dir" value="……." /> to point to

‘jdk1.5.0_15’ folder. Edit the value of property <property name="config.dir" value="….." /> to point to

‘dataimport\config’ folder. Supply the complete path to the config folder.2. Edit dataimport\db_config.xml

Edit the, URL, username, password of BODB in ‘storeDataSource’ bean.

Edit the, URL, username, password of stage1db ‘stage1DataSource’ bean.


db_config.xml

<property name="password" value="db2admin@1"/><property name="username" value="db2admin"/><property name="url" value="jdbc:db2://127.0.0.1:51000/stage1db"/>

db_config.xml

<property name="password" value="db2admin@1"/><property name="username" value="db2admin"/><property name="url" value="jdbc:db2://127.0.0.1:51000/stage2db"/>

db_config.xml

<property name="password" value="db2admin@1"/><property name="username" value="db2admin"/><property name="url" value="jdbc:db2://127.0.0.1:51000/codb"/>

hc-import.properties

db.url=jdbc:db2://127.0.0.1:51000/stage1dbdb.username=db2admindb.password=db2admin@1

stage2db.url=jdbc:db2://localhost:51000/stage2dbstage2db.username=db2adminstage2db.password=db2admin@1

bodb.url=jdbc:db2://localhost:51000/bodbbodb.username=db2adminbodb.password=db2admin@1

codb.url=jdbc:db2://localhost:51000/codbcodb.username=db2admin


Edit the, URL, username, password of stage2 in ‘stage2DataSource’ bean.

Edit the, URL, username, password of CODB in ‘CODataSource’ bean.

3. Edit dataimport\hc-import.properties Edit the URL, username and password of stage1db, stage2db, bodb and codb.

Edit the path to ’loadscripts’ folder


hc_import.properties

runscriptpath=D:\\dataimport\\loadScripts

setenv.bat

set ANT_HOME=D:\hypercity_bo\thirdparty\apache-ant-1.6.2

setenv.bat

set JAVA_HOME=C:\Program Files\Java\jdk1.5.0_15

run-scripts.bat

set ANT_HOME=D: \hypercity_bo\thirdparty\apache-ant-1.6.2

run-scripts.bat


run-scripts.bat

set DB2PATH=D:\Program Files\IBM\SIF\DB2


4. Edit dataimport\setenv.bat Edit path to ANT_home to point to Ant 1.6

Edit path to JAVA_HOME to point to JDK 1.5

Note: On the SIT server I had to add the following line to setenv.batset CLASSPATH=%CLASSPATH%;E:\ dataimport;otherwise the the application was unable to load ‘hc-import.properties’.

5. Edit dataimport\loadScripts\run-scripts.bat Edit path to ANT_home to point to Ant 1.6


Edit path to DB2

Edit username and password to stage1db


run-scripts.bat

set DB_STG1=stage1dbset DB_STG1_USR=db2adminset DB_STG1_USRPASS=db2admin@1rem db2 connect to stage1db user db2admin using db2admin@1

run-scripts2.bat

set ANT_HOME=D:\hypercity_bo\thirdparty\apache-ant-1.6.2

run-scripts2.bat


run-scripts2.bat

set DB2PATH=D:\Program Files\IBM\SIF\DB2

run-scripts2.bat

set DB_STG1=stage2dbset DB_STG1_USR=db2adminset DB_STG1_USRPASS=db2admin@1rem db2 connect to stage1db user db2admin using db2admin@1

Stage1CleanUp.db2

connect to stage1db user db2admin using db2admin@1;

Stage2CleanUp.db2

connect to stage2db user db2admin using db2admin@1;


6. Edit dataimport\loadScripts\run-scripts2.bat Edit path to ANT_home to point to Ant 1.6


Edit path to DB2

Edit username and password to stage2db

7. Edit dataimport\Stage1CleanUp.db2 - Edit username and password for stage1db

8. Edit dataimport\Stage2CleanUp.db2 - Edit username and password for stage2db


Stage1CleanUp.db2

Create stage1db schema by running script stage1_create_1.0.sql

Stage2CleanUp.db2

Create stage2db schema by running script stage2_create_1.0.sql

spring.properties

importdata.file.path=D:/dataimport/BO/jars

spring.properties

importdata.archive.path=D:/dataimport/BO/archive

db2 "catalog tcpip node remoteco remote o360-prd-dbs server 50000"db2 "terminate"


9. Edit dataimport\stage1_create_1.0.sql

10. Edit dataimport\Stage2_create_1.0.sql

2.1.2 Configure Back Office profile on Websphere

1. Open IBM\SIF\WebSphere\AppServer\profiles\BOSrv01\properties\ spring.properties2. Edit path to the directory from which data import bundles should be picked

3. Edit path to the directory to which dimp bundles will be archived after processing

2.1.3 Configuring ‘dataimport’ to connect to stage1, stage2, BO and CO databases on Remote machine

Stage 1 , Stage 2, Stage 3 will usually lie on the same DB (say o360-prd-dbs). While BO DB will lie on another DB.

1. Install DB2 on the machine that has ‘dataimport’ folder.2. Log in as db2admin on DB2 on ‘dataimport’ machine.3. Create an instance alias named remoteco referring to db2admin instance on remotehost (o360-

prd-dbs)

4. Create a database alias named stage1db referring to stage1db, follow this procedure.


db2 "catalog database stage1db as stage1db at node remoteco authentication server"db2 "terminate

db2 => connect to stage1db user db2admin using db2admin@1

db2 "catalog database stage2db as stage2db at node remoteco authentication server"db2 "terminate

db2 "catalog database codb as codb at node remoteco authentication server"db2 "terminate

db2 "catalog tcpip node remotebo remote o360-prd-dbs2 server 50000"db2 "terminate"

db2 "catalog database bodb as bodb at node remotebo authentication server"db2 "terminate

run-scripts2.bat

set DB_STG1=stage1db


5. Now that the alias has been created, you can connect to the database alias using the CONNECT command. For example:

6. Create another database alias named stage2db referring to stage2db, follow this procedure.

7. Create database alias named codb referring to codb, follow this procedure.

8. Create an instance alias named remotebo referring to db2admin instance on remotehost (o360-prd-dbs2)

9. Create database alias named bodb referring to bodb, follow this procedure.

10. Point DB_STG1 in run-scripts.bat to alias named stage1db

11. Point DB_STG1 in run-scripts2.bat to alias named stage2db


run-scripts2.bat

set DB_STG1=stage2db

load client from "c:dataimport\\workingDir\POLLC0.DWN" ……..

spring.properties

importdata.file.path=D:/dataimport/CO/jars

spring.properties

importdata.archive.path=D:/dataimport/CO/archive


12. Edit all “.db2” scripts in the directory dataimport/loadscripts as follows Replace load by load client Supply the complete path to the .DWN file

2.1.4 Configure Central Office Profile on Websphere

1. Open IBM\SIF\WebSphere\AppServer\profiles\COSrv01\properties\ spring.properties2. Edit path to the directory from which data import bundles should be picked

3. Edit path to the directory to which dimp bundles will be archived after processing

2.2 Create Stores in Central Office and Back Office

1. Put MOM-00001-20080417-1.jar in D:/dataimport/ CO/jars and D:/dataimport/ BO/jars. These will be consumed by Central Office and Back Office respectively.

2.3 Running Interfaces

2.3.1 Pre-requisites

2.3.1.1 Processes on Central Office machine

Using DOS command prompt start the following process

1. FTP server. Correct JAVA_HOME in D:\dataimport\apache-ftpserver-1.0.0\bin\startserver.bat Change folder to D:\dataimport\ Run setenv.bat Change folder to D:\dataimport\apache-ftpserver-1.0.0\bin\ Run startserver.bat

Note: Start the server using startserver.bat instead of ftp.bat.


dataimport\config\FTPClientConfig.properties on BO machine

(CO machine) of the FTP server>ftp.server.port=2121 <only jars will be downloaded (Options: xml,jar>

#actual folder from which the poll files will be processed. need complete path like D:\\final\\

<Store ID of BO>

ftp.server.unprocessed.folder=Uftp.server.current.folder=


2. FTP Client. Change to D:\dataimport\ Run runFTP.bat

3. Pricing bat Change folder to D:\dataimport\ Run setenv.bat Run loadCOPRC.bat

4. CO GV interface Change folder to D:\dataimport\ Run runCOGV.bat

2.3.1.2 Processes on Back Office machine

Using DOS command prompt start the following process

1. FTP Client. Change to D:\dataimport\ Run runFTP.bat

Before starting the FTP Client, check FTPClientConfig.properties.

2. Jar bat Change to D:\dataimport\ Run runJar.bat

2.3.2 Build Jars on CO using POLL files from MMS

2.3.2.1 Merchandise Hierarchy Import

On CO machine copy POLL54 in dataimport\dest\<store id> folder. On CO machine, run loadMH.bat file to load data into stage1DB.

Running loadMH.bat does the following: Creates jar in dataimport\jars folder.


dataimport\hc-import.properties on CO machine

jars.directory=jarsbo.jars.directory=apache-ftpserver-1.0.0\\res\\home

spring.properties of CO profile - IBM\SIF\WebSphere\AppServer\profiles\COSrv01\properties\

# directory in which incoming data import bundles arriveimportdata.file.path=D:/dataimport/jars

# directory in which dimp bundles will be archived after processingimportdata.archive.path=D:/dataimport/archive


(CO machine) of the FTP server>ftp.server.port=2121 <only jars will be downloaded>




Creates folders dataimport\apache-ftpserver-1.0.0\res\home\jars and dataimport\apache-ftpserver-1.0.0\res\home\<store id> on the FTP server.

Copies the jar to dataimport\apache-ftpserver-1.0.0\res\home\<store id> and dataimport\apache-ftpserver-1.0.0\res\home\jars folder.

CO Application will consume the jar from dataimport\jars.

The FTP client running on BO machine will pick up the jar from apache-ftpserver-1.0.0\res\home. The FTP scheduler pings the FTP server at regular intervals for any JARs to be imported into BO.

The FTP scheduler checks for store folders for stores defined in ftp.stores.list at location apache-ftpserver-1.0.0\res\home on the FTP server. If jars found then these are downloaded to ftp.client.destinationFolder, from where these are picked by the BO application server.


spring.properties for BO profile - IBM\SIF\WebSphere\AppServer\profiles\BOSrv01\properties\

# directory in which incoming data import bundles arriveimportdata.file.path=D:/dataimport/jars

# directory in which dimp bundles will be archived after processingimportdata.archive.path=D:/dataimport/archive




2.3.2.2 Item Master Import

1. On CO machine copy POLL51 in dataimport\dest\<store id> folder.2. On CO machine, run loadIM.bat file to load data into stage1DB.

2.3.2.3 Item UPC Import

1. On CO machine copy POLL56 in dataimport\dest\<store id> folder.2. On CO machine, run loadID.bat file to load data into stage1DB.

2.3.2.4 Item MRP Import

1. On CO machine copy POLLMP in dataimport\dest\<store id> folder.2. On CO machine, run loadID.bat file to load data into stage1DB.

2.3.2.5 Item Delta Import

1. On CO machine copy POLL53 and POLL55 in dataimport\dest\<store id> folder.2. On CO machine, run loadID.bat file to load data into stage1DB.

2.3.2.6 Pricing Import

1. On CO machine copy POLL64 & POLL79 in dataimport\dest\<store id> folder.2. On CO machine, run loadPRC.bat file to load data into stage1DB.

2.3.2.7 Reason Code Import

1. On CO machine copy POLLRC in dataimport\dest\<store id> folder.2. On CO machine, run loadRC.bat file to load data into stage1DB.

2.3.2.8 Employee Import

1. On CO machine copy POLLHR in dataimport \dest\<store id> folder.2. On CO machine, run loadEMP.bat file to load data into stage1DB.

2.3.2.9 Customer Import

1. On CO machine copy POLLC0, POLLC1, POLLC2, POLLC4, POLLC6, POLLC7, POLLC8, POLLCA & POLLCM in dataimport\dest\<store id> folder.

2. On CO machine, run loadCUST.bat file to load data into stage1DB.

2.3.2.10 Gift Voucher Import

1. On CO machine copy POLL26 in dataimport\dest\<store id> folder.2. On CO machine, run loadGV.bat file to load data into stage1DB.

2.3.2.11 Tax Import

3. On CO machine copy POLLT* in dataimport\dest\<store id> folder.4. On CO machine, run loadTax.bat file to load data into stage1DB.

2.3.2.12 Delete Style Import

1. On CO machine copy POLL41 in dataimport \dest\<store id> folder.2. On CO machine, run loadDeleteDelta.bat file to delete styles.


dataimport\build.xml

<target name="StoresSales">………..<arg value = '04241' /> …….</target>


When the jar is consumed by CO and BO, styles are removed from the CO_STYL table in CODB and BODB. Please note that only styles are deleted, the items with related styles are not deleted. The items will have to be deleted using POLL files.

3 Exporting Data from CO to MMS

3.1 Executing StoresSales.bat to create T* files

1. On CO machine, in build.xml, supply storeid in ‘StoresSales’ target.

2. Create store folder (04241) under dataimport\target folder. The store folder must exist. Otherwise the T* files will not be generated.

3. Run StoresSales.bat


co-pricing-import.properties

PricingImportBaseDir=apache-ftpserver-1.0.0/res/home/PricingImportItemGroupImportBaseDir=apache-ftpserver-1.0.0/res/home/ItemGroupImport

TargetDir=apache-ftpserver-1.0.0/res/home/

stores.list=04241,01290


of the FTP server>ftp.server.port=2121 <only jars will be downloaded>




4 Export data from Central Office to Back Office

4.1 Export Promotions from CO to BO

1. Ensure FTP server is running on the CO machine. Refer to Section 2.3.1.2 - Processes on Central Office machine to start the server.

2. Ensure loadCOPRC.bat is running on the CO machine. Refer to Section 2.3.1.2 - Processes on Central Office machine to start Pricing bat. This calls a Scheduler that checks CO database at regular intervals and creates JAR at location apache-ftpserver-1.0.0\res\home (TargetDir) as defined in co-pricing-import.properties file.

Note: Ensure apache-ftpserver-1.0.0/res/home/PricingImport and apache-ftpserver-1.0.0/res/home/ItemGroupImport path exists on the CO FTP server.

3. Ensure that runFTP.bat is running on the BO machine. Refer to Section 2.3.1.3 - Processes on Back Office machine for starting the FTP client. The FTP client pings the FTP server at regular intervals for any JARs to be imported into BO.



of the FTP server>ftp.server.port=2121 <only jars will be downloaded>




4.2 Export GV from CO to BO

1. Ensure FTP server is running on the CO machine. Refer to Section 2.3.1.2 - Processes on Central Office machine to start the server.

2. Ensure runCOGV.bat is running on the CO machine. Refer to Section 2.3.1.2 - Processes on Central Office machine to start COGV bat.

3. Ensure that runFTP.bat is running on the BO machine. Refer to Section 2.3.1.3 - Processes on Back Office machine for starting the FTP client. The FTP client pings the FTP server at regular intervals for any JARs to be imported into BO.

4.3 Export Parameters from CO to BO

Oracle application (at the CO) sends a JMS message to a store-specific queue (say STORE_01001, STORE_01002, etc) created at a queue manager (co.queue.manager) running on the CO system. A Message-Driven Bean (running under WAS, at the BO) consumes this message and puts it in a Topic, which is subscribed to by various POS applications

Parameters are exported from CO to BO using queues. When a store is added to the enterprise store hierarchy the queue for each store must be defined on the CO.

1. To create the store queue:

a. Add the following commands to CO_Queue_Scripts\create.dat on the CO server.

DEFINE QLOCAL (STORE_<StoreId>.ERROR) USAGE (NORMAL) DEFPSIST(YES)DEFINE QLOCAL (STORE_<StoreId>) USAGE (NORMAL) DEFPSIST(YES) BOQNAME(STORE_04241.ERROR) BOTHRESH(1)

ExampleDEFINE QLOCAL (STORE_04241.ERROR) USAGE (NORMAL) DEFPSIST(YES)DEFINE QLOCAL (STORE_04241) USAGE (NORMAL) DEFPSIST(YES) BOQNAME(STORE_04241.ERROR) BOTHRESH(1)

b. Run the call_configureMQSeries.bat.



2. Create Websphere MQ resource on CO server:a. Log in to the WebSphere Administrative console. b. Create queue references on WebSphere:

i. In the WebSphere Admin Console, navigate to Resources >JMS, >Queues.ii. Set the scope to the server level .

iii. Click New, and select WebSphere MQ messaging provider, and then click OK.

iv. Enter the following details JNDI Name: jms/<StoreId> Base Queue Name: <Name of the queue on Websphere MQ

>( created in Step 1) Base Queue Manager Name: co.queue.manager



3. Create listener port on CO server. i. To do so, in the WebSphere Admin Console, navigate to Servers > Application

Servers> server 1> Messaging> Message Listener Service> Listener Ports. ii. Then create the listener port:

Name: TestStore<StoreId>MDPPort Connection factory JNDI name: jms/ApplicationQCF Destination JNDI name: <JNDI name of the queue>

4. Restart WebSphere CO Application Server.5. Create Websphere MQ resource with JNDI name as ‘ThisStore’ on BO server:



6. Create listener port on BO server.



7. Restart WebSphere BO Application Server.


jndi.properties

#This is for WebSphere. Please uncomment these if you are using WebSphere and keep it commented if not using WebSphere

java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory

java.naming.provider.url=corbaloc:iiop:<BackOfficeServerName>:<BackOfficePortNo.>(e.g. java.naming.provider.url=corbaloc:iiop:o360-test-bo:2810)

java.naming.factory.url.pkgs=com.ibm.ws.naming

jndi.properties

#This is for OracleAS. Please uncomment these if you are using OracleAS and keep it commented if not using OracleAS #java.naming.provider.url=ormi://"store_server_host_name":"store_server_port_number"

#java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory

#java.naming.security.principal=oc4jadmin

#java.naming.security.credentials=oc4jadmin


5 Export data from Back Office to POS

5.1 Export Parameters from BO to POS

Parameters are exported from BO to POS using topic - parameters. All registers subscribe to this topic.

5.1.1 Configuring POS Client

Confirm the following:

1. Ensure that the following entries in OracleRetailStore\Client \pos\bin\jndi.properties file point to Back Office.

Ensure that the following is commented out


comm.properties

comm.jms.topicConnectionFactory.name=jms/ApplicationTCFcomm.jms.queueConnectionFactory.name=jms/ApplicationQCF

ClientConduit.xml<TECHNICIAN name="ParameterTechnician" class = "ParameterTechnician"package = "com.extendyourstore.foundation.manager.parameter"export = "Y" ><PROPERTY propname="paramScript"propvalue="classpath://config/manager/PosParameterTechnician.xml"/><PROPERTY propname="JmsProviderTopicName"propvalue="jms/parameters"/><PROPERTY propname="listenForUpdates" propvalue="Y"/><PROPERTY propname="clientID" propvalue="reg129"/><PROPERTY propname="jmsID" propvalue="mqusr"/><PROPERTY propname="jmsPassword" propvalue="pos@123"/></TECHNICIAN>

Application.properties

WorkstationID=129


2. Check the Back Office queue and topic connection factory entries in OracleRetailStore\Client \pos\bin\comm.properties file.

3. Edit ParameterTechnician in the OracleRetailStore\Client\pos\config\conduit\ClientConduit.xml file.

4. Verify OracleRetailStore\Client\pos\config\application.properties file.

Note: The value of clientID must match the WorkstationID specified in the application.properties file.

Note: You must create a user on the host where Back Office is installed and add that user to the mqm group. The values for jmsID and jmsPassword specified in the Password Technician definition must match the values for the UNIX user and password.

5.1.2 Configuring POS Server



jndi.properties





jndi.properties





backoffice.jndi.properties







2. Check the following entries in OracleRetailStore\Server \pos\config\backoffice.jndi.properties



Backoffice.jndi.properties





centraloffice.properties



java.naming.provider.url=corbaloc:iiop:<CentralOfficeServerName>:<CentralOfficePortNo.>(e.g. java.naming.provider.url=corbaloc:iiop:o360-test-co:2811)



#This is for OracleAS; it will give you access to the POSLog and EJournalImport Queues AND the #Transaction Service Session Bean for CTR. #Please uncomment these if you are using OracleAS and keep it commented if not using OracleAS

#java.naming.provider.url=ormi://172.16.0.167:2810/CentralOffice#java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory#java.naming.security.principal=pos#java.naming.security.credentials=pos


3. Check the following entries inOracleRetailStore\Server \pos\config\centraloffice.jndi.properties to point to Central Office.



comm.properties


comm.properties

comm.jms.topicConnectionFactory.name.<CentralOfficeServerName>=jms/ApplicationTCFcomm.jms.queueConnectionFactory.name.<CentralOfficeServerName>=jms/ApplicationQCF


4. Check the Back Office queue and topic connection factory entries to the OracleRetailStore\Server \pos\bin\comm.properties file.

5. Check the Central Office queue and topic connection factory entries to the OracleRetailStore\Server \pos\bin\comm.properties file.


jndi.properties






6 Export data from POS to CO and BO

6.1 Export Sales Transactions from POS to BO & CO

Transactions flow from POS to BO to using POSLog queue at the BO server. Transactions flow from POS to CO to using POSLog queue at the BO server.

6.1.1 Check POS Log Queue on BO Server

1. Login in to WebSphere Admin Console.2. Navigate to Servers > Application Servers> server 1> Messaging> Message Listener Service>

Listener Ports. 3. Ensure that POSLog status is green. If not then run the BO Queue creation script

BO_Queue_Creation_Scripts\was \call_configureMQSeries.bat .4. Start the port.

6.1.2 Check POS Log Queue on CO Server


Listener Ports. 3. Ensure that POSLog status is green. If not then run the CO Queue creation script

CO_Queue_Creation_Scripts\was \call_configureMQSeries.bat .4. Start the port.





jndi.properties





comm.properties


jndi.properties












jndi.properties



























comm.properties








comm.properties


<Central Office Server Name>.jndi.properties


java.naming.provider.url=ormi://<Central Office Server Name>:<Central Office Port Number>(e.g. java.naming.provider.url=corbaloc:iiop:o360-test-co:2811)






6. Check the OracleRetailStore\Server \pos\config\<Central Office Server Name>.jndi.properties file to point to Central Office. This creates access to the POSLog and EJournalImport queues only


7. Check log export configuration in the OracleRetailStore\Server\pos\config\conduit\StoreServerConduit.xml file by changing only one of the section. To use data replication, edit the DataReplicationDaemonTechnician section.


StoreServerConduit.xml

<TECHNICIAN name="DataReplicationDaemonTechnician" class="DataReplicationDaemonTechnician" package="com.extendyourstore.domain.manager.datareplication" export="Y"> <PROPERTY propname="daemonClassName"propvalue="com.extendyourstore.domain.manager.datareplication.DataReplicationExportDaemonThread"/> <PROPERTY propname="sleepInterval" propvalue="10"/> <PROPERTY propname="logWriterClass" propvalue="com.extendyourstore.domain.manager.datareplication.JMSDataReplicationWriter"/> <PROPERTY propname="extractorConfigurationFileName" propvalue="config/ReplicationExportConfig.xml"/> <PROPERTY propname="extractorObjectFactoryName" propvalue="com.oracle.xmlreplication.ExtractorObjectFactory"/> <PROPERTY propname="queueHostName" propvalue="<CO SERVER NAME>"/> <PROPERTY propname="maximumTransactionsToExport" propvalue="10"/> <PROPERTY propname="queueName" propvalue="jms/POSLog"/> </TECHNICIAN>


6.2 Export Journal from POS to CO

6.2.1 Check EJournalImport and EJournal Queue on BO Server

EJournal is used as the temporary queue for the store (BO) before store server (BO) forwards it on to Central's (CO) EJournalImport queue.

EJournalImport differs from EJournal in that an actual MDB listens on EJournalImport and is responsible for parsing an ejournal xml file. The EJournal queue is simply a staging area.


Listener Ports. 3. Ensure that EJournalImport and EJournal status is green. If not then run the BO Queue creation

script BO_Queue_Creation_Scripts\was \call_configureMQSeries.bat .4. Start the port.

6.2.2 Check EJournalImport Queue on CO Server


Listener Ports. 3. Ensure that EJournalImport status is green. If not then run the CO Queue creation script

CO_Queue_Creation_Scripts\was \call_configureMQSeries.bat .4. Start the port.


jndi.properties





jndi.properties





comm.properties









ClientConduit.xml



 <MANAGER name="JournalManager" class="QueuedJournalManager" package="com.extendyourstore.foundation.manager.journal" export="N"> <PROPERTY propname="configScript" propvalue="classpath://config/manager/PosJournalManager.xml" /> </MANAGER> 



 <TECHNICIAN name="JournalTechnician" class="DBJournalTechnician" package="com.extendyourstore.foundation.manager.journal" export="Y"> <PROPERTY propname="consolePrintable" propvalue="N"/> </TECHNICIAN> 


3. Ensure that Journal entries are saved to database instead of flat file. Check entries in OracleRetailStore\Client \pos\ config\conduit\ClientConduit.xml file.

jndi.properties





jndi.properties















comm.properties


comm.properties




java.naming.provider.url=ormi://<Central Office Server Name>:<Central Office Port Number>(e.g. java.naming.provider.url=corbaloc:iiop:o360-test-co:2811)


java.naming.security.principal=posjava.naming.security.credentials=pos




6. Check the OracleRetailStore\Server \pos\config\<Central Office Server Name>.jndi.properties file to point to Central Office. This creates access to the POSLog and EJournalImport queues only







<TECHNICIAN name="JMSJournalTechnician"class="JMSJournalTechnician"package="com.extendyourstore.foundation.manager.journal"export="Y"><PROPERTY propname="journalFormatterClass"propvalue="com.extendyourstore.pos.manager.journal.POSJournalFormatter"/><PROPERTY propname="journalHandlerClass"propvalue="com.extendyourstore.pos.manager.journal.POSJMSJournalHandler"/><PROPERTY propname="queueName" propvalue="jms/EJournal"/><PROPERTY propname="consolePrintable" propvalue="N"/></TECHNICIAN>


7. Check JMSJournalTechnician in the OracleRetailStore\Server\pos\config\conduit\StoreServerConduit.xml file.

8. Check MessageCenterDaemonTechnician in the OracleRetailStore\Server \pos\config\conduit\StoreServerConduit.xml file.



<TECHNICIAN name="MessageCenterDaemonTechnician"class="MessageCenterDaemonTechnician"package="com.extendyourstore.domain.manager.messagecenter"export="Y"><PROPERTY propname="daemonClassName"propvalue="com.extendyourstore.domain.manager.messagecenter.MessageCenterDaemonThread"/><PROPERTY propname="senderQueueName"propvalue="jms/EJournalImport"/><PROPERTY propname="senderBrokerName"propvalue="<Central Office Server Name>"/><PROPERTY propname="receiverQueueName"propvalue="jms/EJournal"/><PROPERTY propname="receiverBrokerName"propvalue=""/></TECHNICIAN>

Example – cutomerC0.db2

load client from "c:\dataimport\workingDir\POLLC0.DWN" of asc method L(1 10,11 20, 21 21, 22 31, 32 36, 37 46, 47 76, 77 106, 107 136, 137 146, 147 176, 177 216) RESTART into HC_CST_POLLC0;


Note: The value set for the queueName property for the JMSJournalTechnician and the value set for thereceiverQueueName property for the MessageCenterDaemonTechnician must be the same.

7 TroubleShooting Interfaces

7.1 Jar Not Created - SQL0668N Operation not allowed for reason code "3" on table

This means that the previous LOAD had failed. You cannot perform any operations on the involved tables unless the LOAD completes. You can however TERMINATE or RESTART the load. To do so, edit the LOAD statement for all involved tables as below

Try building the JAR again.

7.2 Jar Not Created - SQL0289N Unable to allocate new pages in table space "USERSPACE1".

USERSPACE is the default tablespace that the DB2 uses when a user tablespace is not specified. One cannot increase Free pages in the automatic storage by the following command



DB2 "ALTER TABLESPACE tablespace_name EXTEND (ALL 100000)"

One user tablespaces can be extended by the above command. I dropped unused databases to create more free pages in USERSPACE1.

8 Revision History

Version DatePrepared /

Modified by Comments

0.1 Jan 06, 2011 Pratima Gupta Incorporated review comments

1.0 Jan 07, 2011 Pradeep Jain Minor updates and baseline for delivery

1.1 Feb 04, 2011 Pratima Gupta Made changes for following Added more details to section 2.3.1.2

- Processes on Back Office machine Added section 2.1.3 - Configuring

‘dataimport’ to connect to stage1, stage2, BO and CO databases on Remote machine

Added section 7 - TroubleShooting Interfaces


data import and export

Documents