[opencms-dev] RES: OpenCMS Shell script?

[Daniel Cassiani Rezende]

Yeah, I saw the documentation for the new OCEE 2.1.4 and we are running the final tests for its module upgrade, so we can run the "deleteClusterModule" and "importClusterModule" commands.

That -script argument will work like a glove to automate. Everything else is under control in our development, even lib and xml merge-control. Thanks a lot!!


Daniel Cassiani Rezende

------

Message: 14
Date: Tue, 31 May 2011 18:39:02 +0000
From: "Brabenetz, Harald"
	<harald.brabenetz at bearingpointconsulting.com>
Subject: Re: [opencms-dev] OpenCMS Shell script?
To: "'opencms-dev at opencms.org'" <opencms-dev at opencms.org>
Message-ID:
	<441DE678B488E44A8287592A8B6F46D6029E8F at ATGRZSRVEXMB02.corp.kpmgconsulting.com>
	
Content-Type: text/plain; charset="utf-8"

Maybe:

The shell-Script
--------------------------------------
....do somthing bevor
echo 'Execute cmsshell'
bash cmsshell.sh -script=MyCmsShellScript.txt
....do something after
--------------------------------------

MyCmsShellScript.txt:
-------------------------------
login "Admin" "admin"
setSiteRoot "/sites/default/"
deleteModule "%MODULE_NAME%"
importModuleFromDefault "%MODULE_ZIP%"
replaceModuleFromDefault "%MODULE_NAME%" "%MODULE_ZIP%"
-------------------------------

If you search for new, deleted and changed modules automatically you must generated the "MyCmsShellScript.txt".

hope it helps,
Harald


-----Original Message-----
From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Daniel Cassiani Rezende
Sent: Dienstag, 31. Mai 2011 18:26
To: opencms-dev at opencms.org
Subject: [opencms-dev] OpenCMS Shell script?

Hi, folks,


I was researching about a way to create a scheduled deploy of a new module (in a linux), and I found out about OpenCMS Shell.

My goal is to create a robot application that, let's say at 1:00 AM, do the following routine:

1- search for new modules in a pre-set DEVelopment machine's folder;
2- if a new module is found, copy the module.zip in a PRODuction's machine pre-set folder (WEB-INF\packages\modules is fine by me);
3- run the OpenCMS Shell in PROD;
4- delete the old module;
5- import the new module;
6- since I have OCEE, replicate the module across the cluster's slaves;
7- leave the OpenCMS Shell;
8- restart JBoss;
9- clean our PROXY's cache (that's kinda ready already; it supports single line command from a linux prompt);
10- run an application that warns me by e-mail and sms that a module was found and deployed (also, ready as well).

However, I'm having trouble about how to put steps 3 to 7 in a linux script...

Any ideas about how to automate a chain of commands in OpenCms Shell?


Thanks,


Daniel Cassiani Rezende
________________________________
 INFONOVA GmbH
Sitz: Unterpremst?tten bei Graz
Firmenbuchgericht: Landesgericht f?r ZRS Graz
Firmenbuchnummer: FN 44354b

------------------------------

Message: 22
Date: Wed, 1 Jun 2011 00:41:35 -0700 (PDT)
From: Eska <sven.kiesow at interone.de>
Subject: Re: [opencms-dev] OpenCMS Shell script?
To: opencms-dev at opencms.org
Message-ID: <31747293.post at talk.nabble.com>
Content-Type: text/plain; charset=UTF-8


Hi Daniel,

having OCEE in this process is a NO-GO for this process, as far as I can
tell.
OCEE does NOT publish changes which get inserted in the opencms-modules.xml
like new resources or files that get exported e.g. to the lib-folder on its
own. 

Those changes have to be transfered MANUALLY to the Servers in the Cluster!

ESKA

------------------------------

Message: 24
Date: Wed, 01 Jun 2011 10:23:31 +0200
From: Tobias Herrmann <t.herrmann at alkacon.com>
Subject: Re: [opencms-dev] OpenCMS Shell script?
To: The OpenCms mailing list <opencms-dev at opencms.org>
Message-ID: <4DE5F703.4000302 at alkacon.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi Daniel,

since OCEE 2.1.3 there is a special shell extension to support module import within a OCEE Cluster. This will import the resources, update the module configuration and write the export points across all servers of the cluster. For more details please refer to the Alkacon support for OCEE at
opencms-support at alkacon.com

Kind regards,

Tobias Herrmann

--

Alkacon Software GmbH - The OpenCms Experts
Tobias Herrmann
-------------- next part --------------

Esta mensagem e seus anexos podem conter informações confidenciais ou privilegiadas. Se você não é o destinatário, você não está autorizado a utilizar o material para qualquer fim. Solicitamos que você apague a mensagem e avise imediatamente o remetente. O conteúdo desta mensagem e seus anexos não representam necessariamente a opinião e a intenção da empresa, não implicando em qualquer obrigação ou responsabilidade por parte desta. 
 
This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. The contents of this message and its attachments do not necessarily express the opinion or the intention of the company, and do not imply any legal obligation or responsibilities from this company.