WEM 8.5 - command line application and switching to a different stage

Hi,

using WEM 8.5 there is a command line application that looks like this:

com.vignette.config.client.appserver.AppServerClient appServerClient = new com.vignette.config.client.appserver.AppServerClient(hostname, port, username, password);com.vignette.as.client.javabean.IPagingList siteIPagingList = com.vignette.as.client.javabean.Site.findAll();

So we get all sites in the management stage.
How can we change the stage? We want to get all sites in a delivery stage.

Thanks in advance.

Regards
Thomas

Find more posts tagged with

Comments

William_Prentice

Hi Thomas,

You would have to change the –Dcom.vignette.workingDir java command line arg to point to the directory which has your delivery stage vgncfg.properties and as.cfg file. The vgncfg.properties file has a parameter that points to the location of the as.cfg file, so if you copy these files from another location you will have to adjust this location.

Thanks,

Bill

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Thursday, February 16, 2017 6:58 AM
To: eLink Recipient
Subject: WEM 8.5 - command line application and switching to a different stage

WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/16/2017 07:54 AM

Hi,

using WEM 8.5 there is a command line application that looks like this:

com.vignette.config.client.appserver.AppServerClient appServerClient = new com.vignette.config.client.appserver.AppServerClient(hostname, port, username, password);

com.vignette.as.client.javabean.IPagingList siteIPagingList = com.vignette.as.client.javabean.Site.findAll();

So we get all sites in the management stage.
How can we change the stage? We want to get all sites in a delivery stage.

Thanks in advance.

Regards
Thomas

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Thomas_Rehbein

Hi Bill,

using the -Dcom.vignette.workingDir argument pointing to the delivery stage the program fails when invoking siteIPagingList.asList():

com.vignette.as.client.javabean.IPagingList siteIPagingList = com.vignette.as.client.javabean.Site.findAll();List<com.vignette.as.client.javabean.Site> sites = siteIPagingList.asList();

The error:

ERROR com.vignette.as.client.exception.ApplicationException: Error 9 (RemoteError), Message 026-133-0008: Method invocation from RemotablePagingList failed.    at com.vignette.as.client.exception.ApplicationException.getOne(ApplicationException.java:175)    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.getReflectedPagingList(RemotablePagingListDispatcherOpsLogic.java:316)    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.invokeAsList(RemotablePagingListDispatcherOpsLogic.java:194)    at com.vignette.as.client.javabean.RemotablePagingList.asList(RemotablePagingList.java:184)...Nested exception is:java.lang.reflect.InvocationTargetException    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)    at java.lang.reflect.Method.invoke(Method.java:606)    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.getReflectedPagingList(RemotablePagingListDispatcherOpsLogic.java:308)    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.invokeAsList(RemotablePagingListDispatcherOpsLogic.java:194)    at com.vignette.as.client.javabean.RemotablePagingList.asList(RemotablePagingList.java:184)...Caused by: java.lang.RuntimeException    at com.vignette.as.client.javabean.Site.getTypeObjectTypeRef(Site.java:794)    at com.vignette.as.server.logic.site.SiteOpsLogic.findAll(SiteOpsLogic.java:1925)    at com.vignette.as.server.logic.site.SiteOpsLogic.findAll(SiteOpsLogic.java:1828)    ... 11 more

The program does not fail using the management stage.
Are there any dependencies I should check? Do I need another jars at the classpath? At the moment the WEM related jars are:

log4j.jarsdk-thirdparty-combined.jarvgn-appsvcs-cma.jarvgnhpdapi.jarvgn-shared-logging.jarvgnssl.jarwlthint3client.jar

And do you know any documentation covering the setup of a command line application?

Thank you.
Regards
Thomas

William_Prentice

Hi Thomas,

Please ensure that your application can read from the vgncfg.properties and as.cfg files – permissions, etc.

Also, if you have a datasource defined for your delivery stage (app server) then you will have to modify a copy of the as.cfg file to remove that datasource and we will then use our internal connection pool to retrieve that information.

Thanks,

Bill

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Thursday, February 16, 2017 8:53 AM
To: eLink Recipient
Subject: RE WEM 8.5 - command line application and switching to a different stage

RE WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/16/2017 09:45 AM

Hi Bill,

using the -Dcom.vignette.workingDir argument pointing to the delivery stage the program fails when invoking siteIPagingList.asList():

com.vignette.as.client.javabean.IPagingList siteIPagingList = com.vignette.as.client.javabean.Site.findAll();

List<com.vignette.as.client.javabean.Site> sites = siteIPagingList.asList();

The error:

ERROR com.vignette.as.client.exception.ApplicationException: Error 9 (RemoteError), Message 026-133-0008: Method invocation from RemotablePagingList failed.

    at com.vignette.as.client.exception.ApplicationException.getOne(ApplicationException.java:175)

    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.getReflectedPagingList(RemotablePagingListDispatcherOpsLogic.java:316)

    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.invokeAsList(RemotablePagingListDispatcherOpsLogic.java:194)

    at com.vignette.as.client.javabean.RemotablePagingList.asList(RemotablePagingList.java:184)

....

Nested exception is:

java.lang.reflect.InvocationTargetException

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.getReflectedPagingList(RemotablePagingListDispatcherOpsLogic.java:308)

    at com.vignette.as.server.logic.common.RemotablePagingListDispatcherOpsLogic.invokeAsList(RemotablePagingListDispatcherOpsLogic.java:194)

    at com.vignette.as.client.javabean.RemotablePagingList.asList(RemotablePagingList.java:184)

....

Caused by: java.lang.RuntimeException

    at com.vignette.as.client.javabean.Site.getTypeObjectTypeRef(Site.java:794)

    at com.vignette.as.server.logic.site.SiteOpsLogic.findAll(SiteOpsLogic.java:1925)

    at com.vignette.as.server.logic.site.SiteOpsLogic.findAll(SiteOpsLogic.java:1828)

    ... 11 more

The program does not fail using the management stage.
Are there any dependencies I should check? Do I need another jars at the classpath? At the moment the WEM related jars are:

log4j.jar

sdk-thirdparty-combined.jar

vgn-appsvcs-cma.jar

vgnhpdapi.jar

vgn-shared-logging.jar

vgnssl.jar

wlthint3client.jar

And do you know any documentation covering the setup of a command line application?

Thank you.
Regards
Thomas

[To post a comment, use the normal reply function]
Topic:	WEM 8.5 - command line application and switching to a different stage
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Trilochan_Singh

You can do from the same code:

Iterate the siteIPagingList and get the site object

Get siteStageAssocData from site object:

SiteStageAssocData[] siteStageAssocData= site.getData().getStageAssocs();

for(int j=0;j<siteStageAssocData.length;j++){
System.out.println(" >> "+siteStageAssocData[j].getStageName());
}

Add the condition as per your requirement to show specific sites with xyz delivery stage.

Regards,
Trilochan

From: eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com>
Sent: Thursday, February 16, 2017 6:57 AM
To: eLink Recipient
Subject: WEM 8.5 - command line application and switching to a different stage

This is anEXTERNAL EMAIL. Stop and think before clicking a link or opening attachments.

WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/16/2017 07:54 AM

Hi,using WEM 8.5 there is a command line application that looks like this:com.vignette.config.client.appserver.AppServerClient appServerClient = new com.vignette.config.client.appserver.AppServerClient(hostname, port, username, password);com.vignette.as.client.javabean.IPagingList siteIPagingList = com.vignette.as.client.javabean.Site.findAll();So we get all sites in the management stage.
How can we change the stage? We want to get all sites in a delivery stage.Thanks in advance.Regards
Thomas

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Thomas_Rehbein

Hi Bill,

permissions look fine and should not be a problem.

Yes, indeed, we have defined a delivery stage datasource that is used by our delivery application server.
The as.cfg file seems to be encrypted (it is genereated by the configuration console, right?). How can I modify the as.cfg file?

Thank you for your kind support.

Regards
Thomas

William_Prentice

Hi Thomas,

NOTE: Please make sure you are doing this with a copy of the original delivery stage as.cfg file.

You can modify it by using the following utility that is in the …/8.5/bin directory. cfgedit –F c:\temp\as.cfg

At the prompt if you do a ? you will see the commands available. You will then use the cfgedit commands to navigate to the variable and change it.

cd /vcm-vgninst/cdsvcs/stage-Production/cds-Production/as/HAS_DATA_SOURCE

get HAS_DATA_SOURCE

set HAS_DATA_SOURCE 0

commit

exit

Thanks,

Bill

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Friday, February 17, 2017 12:55 AM
To: eLink Recipient
Subject: RE RE WEM 8.5 - command line application and switching to a different stage

RE RE WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/17/2017 01:52 AM

Hi Bill,

permissions look fine and should not be a problem.

Thank you for your kind support.

Regards
Thomas

[To post a comment, use the normal reply function]
Topic:	WEM 8.5 - command line application and switching to a different stage
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Thomas_Rehbein

Hi Bill,

thank you.
I've created a copy of the as.cfg file with HAS_DATASOURCE 0.
But unforunately the program still fails with the same error.
So I think it's more about the classpath and the java libraries that cause the error?
Do you have any idea left?

Regards
Thomas

William_Prentice

Hi Thomas,

This will work we just need to figure out what is missing. Based on the nested exception,

Caused by: java.lang.RuntimeException

at com.vignette.as.client.javabean.Site.getTypeObjectTypeRef(Site.java:794)

I would like to confirm that you have published an entire site to the delivery stage.

Thanks,

Bill

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Monday, February 20, 2017 7:49 AM
To: eLink Recipient
Subject: RE RE RE WEM 8.5 - command line application and switching to a different stage

RE RE RE WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/20/2017 08:47 AM

Hi Bill,

Regards
Thomas

[To post a comment, use the normal reply function]
Topic:	WEM 8.5 - command line application and switching to a different stage
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Thomas_Rehbein

Hi Bill,

yes, there is at least one site published.
In the VGNASSITE table there is one site in the delivery stage database.

Regards
Thomas

William_Prentice

Hi Thomas,

Please check the vgnasobjecttype table in the delivery stage database and ensure it has the objects with the following names:

ObjectType

Site

AsLocale

Channel

StaticFile

ContentType

If it does not, please let me know. I am doing a test right now against my WEM 8.5 delivery stage with your code sample and will let you know what I find.

Thanks,

Bill

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Tuesday, February 21, 2017 1:02 AM
To: eLink Recipient
Subject: RE RE RE RE WEM 8.5 - command line application and switching to a different stage

RE RE RE RE WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/21/2017 01:58 AM

Hi Bill,

yes, there is at least one site published.
In the VGNASSITE table there is one site in the delivery stage database.

Regards
Thomas

[To post a comment, use the normal reply function]
Topic:	WEM 8.5 - command line application and switching to a different stage
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Thomas_Rehbein

Hi Bill,

the VGNASOBJECTTYPE table looks fine.

I have adapted your command line parameters and now it is working. Some of the jar files were missing in the classpath. Thanky you for sending me your test program and how to execute it. That helped a lot!
So the jars at the classpath have to be the following, right?

wem/Content/8_5/lib/sdk/thirdparty-combined.jarwem/Content/8_5/lib/sdk/vgn-appsvcs-cda.jarwem/Content/8_5/lib/sdk/custom-apps/cda-classpath/ojdbc5.jarwem/Content/8_5/lib/sdk/custom-apps/cda-classpath/log4j.jarwem/Content/8_5/lib/sdk/custom-apps/cda-classpath/vgnclasspath-cda.jarwem/Content/8_5/lib/sdk/custom-apps/cda-classpath/vgn-shared-logging.jarwem/Content/8_5/lib/sdk/shared-resources/jta.jarwem/Content/8_5/lib/vgnssl.jarwem/Content/8_5/lib/servlet.jar

Finally there are some more questions:

1) Using the -Dcom.vignette.workingDir parameter the command line application does not need any further authorization, right? Are you automatically logged in with the admin user? Or do you have read rights only and you have to log in if you need write rights?

2a) If there is a datasource defined at the management or delivery stage you always have to deactivate these datasources, right? The command line application does not work with a datasource configuration, right?

2b) If you change some properties using the configuration console, when do you have have to update the as.cfg for the command line application? As the as.cfg is a copy of the original configuration, do you have to manually update the copied files after cerain configuration changes? Or do you only need to update the as.cfg file when the database configuration changes?

Thank you.
Regards
Thomas

William_Prentice

Hi Thomas,

So glad you were able to get that working. Here are the answers to your additional questions:

So the jars at the classpath have to be the following, right?

That list looks correct. If you run the cdawartool to generate the wars/jars for a app server, then the classes/jars needed will be in the custom-apps\cda-classpath directory.

<WEM Install dir>\WEM\Content\8_5\lib\sdk\custom-apps\cda-classpath

For a standalone app there maybe a couple more that need to be included and you can get those out of our lib (vgnssl.jar, servlet.jar) directory or the shared-resources (jta.jar) directory.

A Content Delivery Application (CDA) does not need any permissions to read data from the WEM database – this is true for any stage (mgmt, delivery). The only time authentication is needed is when you are performing updates to the data or making changes to the system as you would through /AppConsole or /content.

Yes, you are correct. As far as I know datasources are only available when you configure them in the app server.

As a best practice you should update the as.cfg file for the application anytime you make configuration changes that update the as.cfg file. When you push the changes the config console will let you know which processes need to be restarted and if Application Services is specified then you know you need to update the as.cfg file for your standalone app. Example:

Status

The following processes need to be restarted if they are currently running:

Deployment Agent - Appsvcs (/vcm-vgninst/cdsvcs/stage-Prod2/cds-Prod2/cdagents/cda-Appsvcs)

Application Services (/vcm-vgninst/cdsvcs/stage-Prod2/cds-Prod2/as)

Thanks,

Bill

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, February 22, 2017 2:31 AM
To: eLink Recipient
Subject: RE RE RE RE RE WEM 8.5 - command line application and switching to a different stage

RE RE RE RE RE WEM 8.5 - command line application and switching to a different stage

Posted by Rehbein, Thomas On 02/22/2017 03:28 AM

Hi Bill,

the VGNASOBJECTTYPE table looks fine.

wem/Content/8_5/lib/sdk/thirdparty-combined.jar

wem/Content/8_5/lib/sdk/vgn-appsvcs-cda.jar

wem/Content/8_5/lib/sdk/custom-apps/cda-classpath/ojdbc5.jar

wem/Content/8_5/lib/sdk/custom-apps/cda-classpath/log4j.jar

wem/Content/8_5/lib/sdk/custom-apps/cda-classpath/vgnclasspath-cda.jar

wem/Content/8_5/lib/sdk/custom-apps/cda-classpath/vgn-shared-logging.jar

wem/Content/8_5/lib/sdk/shared-resources/jta.jar

wem/Content/8_5/lib/vgnssl.jar

wem/Content/8_5/lib/servlet.jar

Finally there are some more questions:

Thank you.
Regards
Thomas

[To post a comment, use the normal reply function]
Topic:	WEM 8.5 - command line application and switching to a different stage
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center CS16

Thomas_Rehbein

Thank you very much!

Much appreciated!