nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Resyncing the missing versions.

msr

Hi,

We are using Workflow to deploy the content to target servers and then to Database using FILELIST concept.

ISSUE: Last month,we got some issue with JDBC Drivers, so it took almost two weeks to fix this issue. That time, users has been deployed the content to target servers. Due to the DD issue, the content has not pushed to DB.
Now we need to push the missing versions to the DB.

As per I know, we have one option, revert the versions and then deploy to target servers and DB by initiating the Workflow manually.

Is there any automate process to fix this issue?

Any ideas would be helpful. Thanks.

If it helps, I'm using:
TeamSite version: 6.5.0
Platform: Unix

Find more posts tagged with

Comments

santosh013

Hi,

We are using Workflow to deploy the content to target servers and then to Database using FILELIST concept.

ISSUE: Last month,we got some issue with JDBC Drivers, so it took almost two weeks to fix this issue. That time, users has been deployed the content to target servers. Due to the DD issue, the content has not pushed to DB.
Now we need to push the missing versions to the DB.

As per I know, we have one option, revert the versions and then deploy to target servers and DB by initiating the Workflow manually.

Is there any automate process to fix this issue?

Any ideas would be helpful. Thanks.

If it helps, I'm using:
TeamSite version: 6.5.0
Platform: Unix

Hi,
If I am not wrong then I hope you are pushing the contents to the DB as well as updating it with the latest content/contents in your Teamsite Server.
Assuming that you are only updating your Database tables/fields with your latest content then I hope you will only have to use DD to deploy your updated contents to the DB but with little precaution.
Now when you say the term "reverting the version" then I hope that you have some different concept for pushing the content to DB.
Can you clarify this?

Thanks.

msr

Thanks for your reply.

I am pushing the content to target application server nodes and DB using OD one by one.

>> Now when you say the term "reverting the version" then I hope that you have some different concept for pushing the content to DB.

'Reverting the version' means manually get the required version from version history and then deploy to application server nodes and DB using OD.

I am looking for an idea of doing the same without manual effort.

Let me know, if you still not clear about the issue.

santosh013

Thanks for your reply.

I am pushing the content to target application server nodes and DB using OD one by one.

>> Now when you say the term "reverting the version" then I hope that you have some different concept for pushing the content to DB.

'Reverting the version' means manually get the required version from version history and then deploy to application server nodes and DB using OD.

I am looking for an idea of doing the same without manual effort.

Let me know, if you still not clear about the issue.

Hi,
This is what I wanted to know that why are you willing to revert the version when your goal is to push the updated content.
I don't think that you are maintaining versions in DB and if it holds true then obviously you want to push only updated contents to DB.
I am not very sure as to why you are willing to revert and then deploy the contents to DB when you only need to update the DB with latest version files.
Is it right or you have some other logic/concept?

Thanks.

Bhargav Coca

Hi,

We are using Workflow to deploy the content to target servers and then to Database using FILELIST concept.

ISSUE: Last month,we got some issue with JDBC Drivers, so it took almost two weeks to fix this issue. That time, users has been deployed the content to target servers. Due to the DD issue, the content has not pushed to DB.
Now we need to push the missing versions to the DB.

As per I know, we have one option, revert the versions and then deploy to target servers and DB by initiating the Workflow manually.

Is there any automate process to fix this issue?

Any ideas would be helpful. Thanks.

If it helps, I'm using:
TeamSite version: 6.5.0
Platform: Unix

If your whole DD is set up good and if there were no changes in your schema . You can always write a script to deploy the files from last three weeks though your workflow. That will solve your problem.

Thanks

msr

Hello Santosh/Lilly,

Thanks for your reply.

>> I don't think that you are maintaining versions in DB and if it holds true then obviously you want to push only updated contents to DB.

Yes..We are maintaining versions in the DB. For each version in teamsite, there should be corresponding entry in DB table.

While the Data Deploy (3 Weeks period) was in issue, user have created new content with more than one versions. So I need to push all the versions to the DB.

I hope, you guys understand my problem.

santosh013

Hello Santosh/Lilly,

Thanks for your reply.

>> I don't think that you are maintaining versions in DB and if it holds true then obviously you want to push only updated contents to DB.

Yes..We are maintaining versions in the DB. For each version in teamsite, there should be corresponding entry in DB table.

While the Data Deploy (3 Weeks period) was in issue, user have created new content with more than one versions. So I need to push all the versions to the DB.

I hope, you guys understand my problem.

Hi,
If you are maintaining the versions in DB then I don't think that there is any automatic way of doing this.
I think you will have to do it manually only.

Thanks.

Bhargav Coca

Hello Santosh/Lilly,

Thanks for your reply.

>> I don't think that you are maintaining versions in DB and if it holds true then obviously you want to push only updated contents to DB.

Yes..We are maintaining versions in the DB. For each version in teamsite, there should be corresponding entry in DB table.

While the Data Deploy (3 Weeks period) was in issue, user have created new content with more than one versions. So I need to push all the versions to the DB.

I hope, you guys understand my problem.

I do not know how many version you have in you downtime of your DB, but I guess Manual revert and publishing seems easier and little time consuming Job for you.

HTH

ccprofessional

Yes..We are maintaining versions in the DB. For each version in teamsite, there should be corresponding entry in DB table.

Smells like a bad architecture

santosh013

Smells like a bad architecture

I will not comment on the architecture and about what compelled them to go this way but I am also thinking what made them to keep the versions in DB.
But answering to this problem I think msr will have to do it manually.