Content Administration - Import data to a versioned repository using SOLID and DAS

[Vincy]

Hi,
Can anyone please help me on the problem specified below?

I have a normal module running under ATG2006.3. I exported all the
repositories that i have created or to which i have added new data.

I want a Versioned repository for the module. I have set everything
accordingly. All the tables related to versioned have been set and the
propeties file too.
I am able to bring up my bcc and see the repository names.

I am using Solid and DAS6.3.0

But when i try to do a import of the data taken earlier to the DB, the
below exception is thrown after a set of data have been entered:

-- creating definition of contract:100002
-- creating definition of contract:100004
*** atg.repository.RepositoryException: current development line null
is not an open workspace.
atg.repository.RepositoryException: current development line null is
not an open workspace.
at
atg.adapter.version.VersionRepository.createItem(VersionRepository.java:
1618)
at
atg.adapter.version.VersionRepository.createItem(VersionRepository.java:
907)
at
atg.adapter.gsa.xml.TemplateParser.createItem(TemplateParser.java:
990)
at
atg.adapter.gsa.xml.TemplateParser.importAddElements(TemplateParser.java:
841)
at
atg.adapter.gsa.xml.TemplateParser.processTransaction(TemplateParser.java:
1815)
at
atg.adapter.gsa.xml.TemplateParser.loadOperationElements(TemplateParser.java:
802)
at
atg.adapter.gsa.xml.TemplateParser.addDocumentToTemplate(TemplateParser.java:
689)
at
atg.adapter.gsa.xml.TemplateParser.addToTemplate(TemplateParser.java:
494)
at
atg.adapter.gsa.xml.TemplateParser.importFiles(TemplateParser.java:
6127)
at
atg.adapter.gsa.xml.TemplateParser.runParser(TemplateParser.java:
5235)
at atg.adapter.gsa.xml.TemplateParser.main(TemplateParser.java:
4792)
**** info Tue Jan 22 13:30:23 IST 2008 1200988823875 /atg/
dynamo/service/Scheduler Scheduler shutting down.
**** info Tue Jan 22 13:30:23 IST 2008 1200988823875 /atg/
dynamo/service/Scheduler Scheduler stopped.

Any idea? I gave the option with -workspace and -comment too. but both
resulted in the same.

Hope to get a suggestion soon
Vincy

[John Cooke]

what is the command line you are using to do the import? (the whole
thing with all of the options)

Are you using any custom or modified workflows?

If not which standard workflow are you using (the default?) ?

Gordon Cooke
Spark::red - ATG Managed Hosting
http://sparkred.com

[Vincy]

Hi John,

Below is my commandline:

C:\ATG\ATG2006.3\home\bin>startSQLRepository -m MotorpriseJSPVer -
repository /atg/userprofiling/ProfileAdapterRepository -import c:
\Jan18Profile.xml

I also gave options for -workspace and -comment.

C:\ATG\ATG2006.3\home\bin>startSQLRepository -m MotorpriseJSPVer -
repository /atg/userprofiling/ProfileAdapterRepository -import c:
\Jan18Profile.xml -workspace test -comment testversion

Both produced the same results.

Do you have any idea why this is happening?

It would be a great help if you could suggest something.

On Jan 22, 1:28 pm, John Cooke <jwgco...@gmail.com> wrote:
> what is the command line you are using to do the import? (the whole  
> thing with all of the options)
>
> Are you using any custom or modified workflows?
>
> If not which standard workflow are you using (the default?) ?
>
> Gordon Cooke

> Spark::red - ATG Managed Hostinghttp://sparkred.com

> > Vincy- Hide quoted text -
>
> - Show quoted text -

[John Cooke]

It looks like below you are exporting/importing your Profile Adapter
repository?? This should not be versioned... The data in the Profile
repository is dynamic and typically env. specific. I am not sure that
this is even supported by ATG. Do you have the Profile Repository set
up as a versioned repository? If it is not that could be why it is
failing.

If all else is in place this should work (you are missing the user
argument) but I would be surprised to hear that it does with the
Profile Repository.

startSQLRepository -m <module> -repository <repository path> -user
<user name> -workspace <unique workspace identifier> -comment <some
comment>

Gordon Cooke
Spark::red - Managed ATG Hosting
http://sparkred.com

[Vincy]

Hi John,

Thank you for your repsonse.

What you said is right that the ProfileAdapter Repository is not
Versioned. It is just copying the data from one DB to another.
But still i am getting the error.
Why it is failing is what i dont understand.
I never used -user option.

startSQLRepository -m MotorpriseJSPVer -repository /atg/userprofiling/

ProfileAdapterRepository -user publishing -workspace Motorprise -
comment profileversion -import c:\Jan18Profile.xml

Now that i have tried that too. But it is again the same exception in
the end showing "development line is null".

I am not able to understand this development line being null.
Can you please tell me what development line is and where should i
specify this development line ? :(

Thank you
Vincy

On Jan 23, 12:12 am, John Cooke <jwgco...@gmail.com> wrote:
> It looks like below you are exporting/importing your Profile Adapter  
> repository??  This should not be versioned...  The data in the Profile  
> repository is dynamic and typically env. specific.  I am not sure that  
> this is even supported by ATG.  Do you have the Profile Repository set  
> up as a versioned repository?  If it is not that could be why it is  
> failing.
>
> If all else is in place this should work (you are missing the user  
> argument) but I would be surprised to hear that it does with the  
> Profile Repository.
>
> startSQLRepository -m <module> -repository <repository path> -user  
> <user name> -workspace <unique workspace identifier>  -comment <some  
> comment>
>
> Gordon Cooke

> Spark::red - Managed ATG Hostinghttp://sparkred.com

> >> - Show quoted text -- Hide quoted text -

[Gordon Cooke]

If you are not importing into a versioned repository you do not need
the workspace, user or comment options. These are only needed if you
are importing into a versioned repository on a server running CA/
Publishing. If you are simply moving the profile repository use the
options on startSQLRepository that are spec'd out in the repository
dev. guide.

Gordon Cooke
Spark::red - Managed ATG Hosting
http://sparkred.com

[Naga]

Vincy,

Whats the requirement for importing user data into versioned repository ???

Naga

[Vincy]

Hi everyone,

I think i need to repharse my question.
what should i do to make the MotorpriseJSP module to be a versioned
module?
I have added new catalogs, pricelists, promotions and made changes in
organization and profile.

I need all these in the versioned repository.

How do i do it?

Vincy

On Jan 24, 10:08 am, Naga <a.s.nagara...@gmail.com> wrote:
> Vincy,
> Whats the requirement for importing user data into versioned repository ???
>
> Naga
>

[Naga]

Vincy,

You dont need to have the user and organization data in the versioned repository as user data is not going to be modified by the Merchandising or CMS or Outreach systems. If you need to have your new Catalog info in your Merchandising module. You may have to export your ProductCatalog repository and import them into the versioned system and thats it. I dont know if the MotorpriseJSP has an extended ProductCatalog - i mean if there is any new tables added or anything like that..in that case you may have to create a MotorpriseJSPVer using ATGRequired as Publishing.base and have the extended productcatalog xml and pricing model xml copied over to the new module and make changes for deployable and other attributes if need be and the start you versioned module using B2BCommerce.versioned PubPortlet and MotorpriseJSPVer and you are good to go to see all your merchandising changes...

Naga

On Jan 24, 2008 11:01 AM, Vincy <vincyse...@gmail.com> wrote:

Hi everyone,

I think i need to repharse my question.
what should i do to make the MotorpriseJSP module to be a versioned
module?
I have added new catalogs, pricelists, promotions and made changes in
organization and profile.

I need all these in the versioned repository.

How do i do it?

Vincy

[Vincy]

Hi Everyone,

Thank you very much for all the response.
I have benefitted from each suggestion provided by you.

As i got it correct i am writing down the steps i took to get it
done.

1. First is exporting the data from your non-versioned repository:

startSQlRepository -m MotorpriseJSP -repository /atg/userprofiling/
ProfileAdapterRepository -export All c:\24JanProfile.xml

startSQlRepository -m MotorpriseJSP -repository /atg/commerce/catalog/
ProductCatalog -export All c:\24JanCatalog.xml

startSQlRepository -m MotorpriseJSP -repository /atg/commerce/pricing/
priceLists/PriceLists -export All c:\24JanPriceLists.xml

startSQlRepository -m MotorpriseJSP -repository /atg/commerce/pricing/
Promotions -export All c:\24JanPromotions.xml

2. Second is on the new DB settting up the versioned tables.

C:\ATG\ATG2006.3\DAS\solid\i486-unknown-win32\solsql.exe "tcp 1313"
publishing publishing C:\ATG\ATG2006.3\DCS\Versioned\sql\install\solid
\dcs_versioned_ddl.sql

C:\ATG\ATG2006.3\DAS\solid\i486-unknown-win32\solsql.exe "tcp 1313"
publishing publishing C:\ATG\ATG2006.3\DCS\CustomCatalogs\Versioned\sql
\db_components\solid\versioned_custom_catalog_ddl.sql

C:\ATG\ATG2006.3\DAS\solid\i486-unknown-win32\solsql.exe "tcp 1313"
publishing publishing C:\ATG\ATG2006.3\B2BCommerce\Versioned\sql
\install\solid\b2bcommerce_versioned_ddl.sql

3. Third is updating the property files.

Create /config/atg/commerce/catalog/CatalogRepository.properties in
the place of original repository configuration XML file with the
following details

$class=atg.adapter.version.VersionRepository
versionManager=/atg/epub/version/VersionManagerService
versionItemsByDefault=true
checkTables=false

MotorpriseJSPVer/config/atg directory , create epub/version directory
structure. Then create a new file in that directory structure called
VersionManagerService.properties with the following property :

versionedRepositories+=\
CatalogRepository=/atg/commerce/catalog/ProductCatalog

4. Fourth import the data to the new tables:

startSQLRepository -m MotorpriseJSPVer -repository /atg/commerce/
catalog/ProductCatalog -import c:\24JanCatalog.xml -workspace motor -
comment motorversion

startSQLRepository -m MotorpriseJSPVer -repository /atg/commerce/
pricing/priceLists/PriceLists -import c:\24JanPriceList.xml -workspace
motorprice -comment motorversion


Hope this would help someone else with the same trouble as i had.
Thank you all.

Vincy

On Jan 24, 10:46 am, Naga <a.s.nagara...@gmail.com> wrote:
> Vincy,
> You dont need to have the user and organization data in the versioned
> repository as user data is not going to be modified by the Merchandising or
> CMS or Outreach systems. If you need to have your new Catalog info in your
> Merchandising module. You may have to export your ProductCatalog repository
> and import them into the versioned system and thats it. I dont know if the
> MotorpriseJSP has an extended ProductCatalog - i mean if there is any new
> tables added or anything like that..in that case you may have to create a
> MotorpriseJSPVer using ATGRequired as Publishing.base and have the extended
> productcatalog xml and pricing model xml copied over to the new module and
> make changes for deployable and other attributes if need be and the start
> you versioned module using B2BCommerce.versioned PubPortlet and
> MotorpriseJSPVer and you are good to go to see all your merchandising
> changes...
>
> Naga
>

[srikanth]

Hi ,

Thanks for sharing the info. Do we need to create any FakeXADatasource prior to this as mentioned in the blog http://world-of-atg.blogspot.in/2012/07/using-startsqlrepository-beginners-iv.html

Thanks,

Srikanth