Repository Data Import StartSQLImport BCC

The following section explains the steps which  are used one of the  project.

pre Configruation:

1)  As part of CA module's MetaInfo file (MANIFEST.MF), need to add the following one.
path :%ATGROOT%/modules/CA/META-INF

   ATG-Required: DafEar.Admin DCS-UI.Versioned BIZUI PubPortlet DCS-UI.SiteAdmin.Versioned SiteAdmin.Versioned DCS.Versioned DCS-UI DAF.Endeca.Index.Versioned DCS.Endeca.Index.Versioned DCS.Endeca.Index.SKUIndexing modules.Commerce


2) Need to set the server layer pub_import and create the JTDataSource and FakeXADataSource components.This will be explain at the end of this section.
  The following files need to kept in the path /opt/ATG/ATG10.2/home/servers/pub_import/localconfig/atg/dynamo/service/jdbc.

 JTDataSource.properties
JTDataSource_production.properties
FakeXADataSource_pub.properties
FakeXADataSource.properties
DirectJTDataSource_production.properties
DirectJTDataSource.properties
IdGenerator.properties
IdGenerator_production.properties
SwitchingDataSource.properties
FakeXADataSource_core.properties

And the values of these components will be given down.

  


The following command can be executed at  Linux box. Before executing this command, need to copy the OneProductParentCateoryChange.xml file at specified location.

cd /opt/ATG/ATG10.2/home/bin
nohup startSQLImport -m modules.CA -s pub_import -repository /atg/commerce/catalog/ProductCatalog -file /opt/ATG/ATG10.2/home/bin/xxFolderN/OneProductParentCateoryChange.xml -project ProductsParentCategoryChange > /opt/ATG/ATG10.2/home/bin/Logs/importedProductslog.txt &


Once it is ran successfully, project  (ProductsParentCategoryChange ) need to deploy manually at BCC UI.


Here -s pub_import,is server layer. Need to copy the pub_import folder in the /opt/ATG/ATG10.2/home/servers path.Then  need to add the localconfig in the folder pub_import.So finally it will be as follows.

/opt/ATG/ATG10.2/home/servers/pub_import/localconfig/atg



On executing this command, the project is created at BCC with the  project name ProductsParentCategoryChange.But this project name can be seen on restarting the server only and can deploy the project without having any issues.  Or on flushing the cache at PublishingRepository component of BCC Dynamo/admin.


The Log will be as follows.Once the import is done, the started Nucleus will be shutdown.




*** info    Thu May 04 15:11:49 IST 2017    1493890909311    /atg/commerce/pricing/Promotions    Resolving reference to /atg/commerce/catalog/ProductCatalog
**** info    Thu May 04 15:11:49 IST 2017    1493890909323    /atg/commerce/claimable/Claimable-ver    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909324    /atg/commerce/claimable/ClaimableRepository    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909406    /atg/dynamo/service/jdbc/SQLRepository    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909435    /atg/userprofiling/PersonalizationRepository-ver    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909436    /atg/userprofiling/PersonalizationRepository    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909469    /atg/epub/process/ProcessData-ver    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909471    /atg/epub/process/ProcessDataRepository    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909529    /atg/epub/file/PublishingFiles-ver    SQL Repository startup complete
**** info    Thu May 04 15:11:49 IST 2017    1493890909538    /atg/epub/file/PublishingFileRepository    SQL Repository startup complete

Nucleus running


**** info    Thu May 04 15:11:50 IST 2017    1493890910325    /atg/epub/PublishingRepository    SQL Repository startup complete

*** info    Thu May 04 15:12:13 IST 2017    1493890933024    /atg/epub/deployment/DeploymentManager    Resolving reference to /atg/deployment/DeploymentManager
**** info    Thu May 04 15:12:13 IST 2017    1493890933076    /atg/dynamo/service/InternalCurrentDate    Resolving reference to /atg/dynamo/service/CurrentDate
[info@2017-05-04 15:12:13.215] created project: ParentCategoryChange
[info@2017-05-04 15:12:13.217] parsing input data

[info@2017-05-04 15:12:13.241] importing 1 items.

[info@2017-05-04 15:12:13.241] checking out versioned items in batch

[info@2017-05-04 15:12:22.306] Phase 1 of 2: 100%

[info@2017-05-04 15:12:22.306] performing add/update/removes phase 2

[info@2017-05-04 15:12:23.364] Phase 2 of 3: 100%

[info@2017-05-04 15:12:23.367] performing add/update/removes phase 3

[info@2017-05-04 15:12:24.417] Phase 3 of 3: 100%

[info@2017-05-04 15:12:24.423] imported 1 items in 0:00:34 hh:mm:ss (excluding checkin)

[info@2017-05-04 15:12:24.438] imported 1 items at 0.03 items/second

[info@2017-05-04 15:12:24.438] shutting down

**** info    Thu May 04 15:12:24 IST 2017    1493890944461    /atg/commerce/payment/PaymentPipelineManager    Stopping PipelineManager.
**** info    Thu May 04 15:12:24 IST 2017    1493890944461    /atg/commerce/approval/ApprovalPipelineManager    Stopping PipelineManager.
**** info    Thu May 04 15:12:24 IST 2017    1493890944464    /atg/commerce/endeca/index/CategoryTreeService    service stopped.
**** info    Thu May 04 15:12:24 IST 2017    1493890944465    /atg/commerce/PipelineManager    Stopping PipelineManager.
**** info    Thu May 04 15:12:24 IST 2017    1493890944466    /atg/commerce/invoice/pipeline/InvoicePipelineManager    Stopping PipelineManager.
**** info    Thu May 04 15:12:35 IST 2017    1493890955884    /atg/dynamo/service/Scheduler    Scheduler shutting down.
**** info    Thu May 04 15:12:35 IST 2017    1493890955885    /atg/dynamo/service/Scheduler    Scheduler stopped.
**** debug    Thu May 04 15:15:14 IST 2017    1493891114886    /atg/epub/version/VersionManagerService    Uninitializing the VersionManagerService

................


Note: startSQLImport command won't be available with ATG 10.2 . Once the patch5(P5) is applied, then only the startSQLImport will be available at  %ATG_HOME%/bin folder.  If patch is not applied properly, on importing the catalog items, relation ships between items will be missed.


 Preconfiguration steps  , point 2 in details


 JTDataSource.properties
JTDataSource_production.properties
FakeXADataSource_pub.properties
FakeXADataSource.properties
DirectJTDataSource_production.properties
DirectJTDataSource.properties
IdGenerator.properties
IdGenerator_production.properties
SwitchingDataSource.properties
FakeXADataSource_core.properties



 JTDataSource.properties
 $class=atg.service.jdbc.MonitoredDataSource

# only use this data source if you do not have an JDBC driver
# which provides true XA data sources
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource_pub
# Minimum and maximum number of connections to keep in the pool
min=10
max=500
blocking=true#maxBlockTime=
#maxCreateTime=
#maxCreateAttempts=#
# This will log any SQLWarnings that are generated.  By default, we turn
# these off since they tend to be informational, not really warnings.  If
# you want the full traceback for where these messages are generated,
# set loggingWarning to true.
#
loggingSQLWarning=false#
# The monitored connection by default logs all sql through the log info
# path.
#
loggingSQLInfo=false

JTDataSource_production.properties


$class=atg.service.jdbc.MonitoredDataSource

# only use this data source if you do not have an JDBC driver
# which provides true XA data sources
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource_core
# Minimum and maximum number of connections to keep in the pool
min=10
max=10
blocking=true
#maxBlockTime=
#maxCreateTime=
#maxCreateAttempts=#
# This will log any SQLWarnings that are generated.  By default, we turn
# these off since they tend to be informational, not really warnings.  If
# you want the full traceback for where these messages are generated,
# set loggingWarning to true.
#
loggingSQLWarning=false
#
# The monitored connection by default logs all sql through the log info
# path.
#
loggingSQLInfo=false


FakeXADataSource_pub.properties

#-------------------------------------------------------------------
#-------------------------------------------------------------------
# This is a non-XA DataSource that creates simulated XAConnections.
# It is useful when a true XADataSource cannot be obtained.  Note that
# the behaviour of the Connections will not be that of normal
# XAConnections, i.e. they will not be able to participate in
# two-phase commits in the true two-phase commit style.
#-------------------------------------------------------------------

$class=atg.service.jdbc.FakeXADataSource

#driver=oracle.jdbc.xa.client.OracleXADataSource
driver=oracle.jdbc.driver.OracleDriver
URL=jdbc:oracle:thin:@DBHostIPAddress:1521:SID
user=userName (pub username)
password=PWD(pub password)

FakeXADataSource.properties

#-------------------------------------------------------------------
# This is a non-XA DataSource that creates simulated XAConnections.
# It is useful when a true XADataSource cannot be obtained.  Note that
# the behaviour of the Connections will not be that of normal
# XAConnections, i.e. they will not be able to participate in
# two-phase commits in the true two-phase commit style.
#-------------------------------------------------------------------

$class=atg.service.jdbc.FakeXADataSource

#driver=oracle.jdbc.xa.client.OracleXADataSource
driver=oracle.jdbc.driver.OracleDriver

URL=jdbc:oracle:thin:@DBHostIPAddress:1521:SID
user=userName (cata username)
password=PWD(cata PWD)


DirectJTDataSource_production.properties
 $class=atg.service.jdbc.MonitoredDataSource

# only use this data source if you do not have an JDBC driver
# which provides true XA data sources
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource_core

# Minimum and maximum number of connections to keep in the pool
min=10
max=10
blocking=true
#maxBlockTime=
#maxCreateTime=
#maxCreateAttempts=#
# This will log any SQLWarnings that are generated.  By default, we turn
# these off since they tend to be informational, not really warnings.  If
# you want the full traceback for where these messages are generated,
# set loggingWarning to true.
#
loggingSQLWarning=false
#
# The monitored connection by default logs all sql through the log info
# path.
#
loggingSQLInfo=true

DirectJTDataSource.properties

$class=atg.service.jdbc.MonitoredDataSource
# only use this data source if you do not have an JDBC driver
# which provides true XA data sources
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource

# Minimum and maximum number of connections to keep in the pool
min=10
max=10
blocking=true
#maxBlockTime=
#maxCreateTime=
#maxCreateAttempts=
#
# This will log any SQLWarnings that are generated.  By default, we turn
# these off since they tend to be informational, not really warnings.  If
# you want the full traceback for where these messages are generated,
# set loggingWarning to true.
#
loggingSQLWarning=true
#
# The monitored connection by default logs all sql through the log info
# path.
#
loggingSQLInfo=true

IdGenerator.properties
 dataSource=/atg/dynamo/service/jdbc/JTDataSource

IdGenerator_production.properties
dataSource=/atg/dynamo/service/jdbc/JTDataSource_production

SwitchingDataSource.properties

$class=atg.service.jdbc.MonitoredDataSource

# only use this data source if you do not have an JDBC driver
# which provides true XA data sources
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource

# Minimum and maximum number of connections to keep in the pool
min=10
max=10
blocking=true
#maxBlockTime=
#maxCreateTime=
#maxCreateAttempts=
#
# This will log any SQLWarnings that are generated.  By default, we turn
# these off since they tend to be informational, not really warnings.  If
# you want the full traceback for where these messages are generated,
# set loggingWarning to true.
#
loggingSQLWarning=false
#
# The monitored connection by default logs all sql through the log info
# path.
#
loggingSQLInfo=true

FakeXADataSource_core.properties

#-------------------------------------------------------------------
#-------------------------------------------------------------------
# This is a non-XA DataSource that creates simulated XAConnections.
# It is useful when a true XADataSource cannot be obtained.  Note that
# the behaviour of the Connections will not be that of normal
# XAConnections, i.e. they will not be able to participate in
# two-phase commits in the true two-phase commit style.
#-------------------------------------------------------------------

$class=atg.service.jdbc.FakeXADataSource
driver=oracle.jdbc.xa.client.OracleXADataSource
URL=jdbc:oracle:thin:@DB HOstIP address:1521:SIDValue
user=userName (core schema username)
password=pwd(core schema  pwd)




----

This import is used to verify whether parent categories are updated along with product items even if the property is read only.  The parent category is not updated and also at the share table(DB) dcs_cat_chidprods level, the entry is missed. It looks like data is corrupted.