Histórico da Página
| HTML |
|---|
<div id="main-content" class="wiki-content group">
<h1 id="ConversãoTOTVSECMparaFluig-Índice">Contents</h1>
<p>
<style type='text/css'>/*<![CDATA[*/
div.rbtoc1412695582537 {
padding: 0px;
}
div.rbtoc1412695582537 ul {
list-style: none;
margin-left: 0px;
}
div.rbtoc1412695582537 li {
margin-left: 0px;
padding-left: 0px;
}
/*]]>*/
</style>
<div class='toc-macro rbtoc1412695582537'>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>1</span> <a
href='#ConversãoTOTVSECMparaFluig-Objetivo'>Objective</a></li>
<li><span class='TOCOutline'>2</span> <a
href='#ConversãoTOTVSECMparaFluig-ConversãoparaoFluig'>Conversion
to Fluig</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>2.1</span> <a
href='#ConversãoTOTVSECMparaFluig-CópiadeSegurança'>Backup
copy</a></li>
<li><span class='TOCOutline'>2.2</span> <a
href='#ConversãoTOTVSECMparaFluig-AntesdaConversão'>Before
conversion</a></li>
<li><span class='TOCOutline'>2.3</span> <a
href='#ConversãoTOTVSECMparaFluig-IniciandooFluig'>Starting
Fluig</a></li>
<li><span class='TOCOutline'>2.4</span> <a
href='#ConversãoTOTVSECMparaFluig-Conversão'>Conversion</a></li>
<li><span class='TOCOutline'>2.5</span> <a
href='#ConversãoTOTVSECMparaFluig-Pós-conversãooumigração'>Post
conversion or migration</a></li>
</ul></li>
</ul>
</div>
</p>
<h1 id="ConversãoTOTVSECMparaFluig-Objetivo">Objective</h1>
<p>The goal of this guide is to instruct system administrators who
wish to perform the conversion of TOTVS ECM to the Fluig platform.</p>
<h1 id="ConversãoTOTVSECMparaFluig-ConversãoparaoFluig">Conversion
to Fluig</h1>
<p>See the following steps and procedures necessary for the
conversion of TOTVS ECM to Fluig. </p>
<h3 id="ConversãoTOTVSECMparaFluig-CópiadeSegurança">Backup copy</h3>
<div class="aui-message warning shadowed information-macro">
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>In order to preserve the resources and data from TOTVS ECM in
case there is an error during the conversion process, it is
important to run a backup of the following items:</p>
<ul>
<li><strong>Resources used in TOTVS ECM:</strong> as
Binders, customized Dataset, Workflow processes, Binder events,
process events, global events, services, applications, general
parameters, e-mail templates, attribute mechanisms, and other
customizations used in TOTVS ECM. It is important to export as many
of these resources as possible, for better handling during the
approval process after the conversion of TOTVS ECM to Fluig in
addition to enabling the import to Fluig, if necessary, later on.</li>
<li><strong>Database:</strong> It is important to have a
backup copy of the database to restore the last valid state of
installation of TOTVS ECM, if necessary. If you want to keep the
old installation, it is a good idea to replicate the database so
that the same content assumes a new name. For example, the database
of TOTVS ECM, by default, is called <strong>totvsecm</strong>,
while for Fluig, they are named <strong>fluig</strong>.</li>
<li><strong>Volume:</strong> If you wish to keep the old
installation of TOTVS ECM, after conversion, the volumes registered
in TOTVS ECM will still be used. With this, the data in them may
suffer changes in the use of Fluig, and this sharing between the
two systems can cause conflicts and errors during use. To avoid
this situation it is necessary to copy the volumes to a new
location. It is important to have a backup copy of the volume <span>to
restore the last valid state of installation of TOTVS ECM, if
necessary.</span></li>
</ul>
</div>
</div>
<h3 id="ConversãoTOTVSECMparaFluig-AntesdaConversão">Before
conversion</h3>
<div class="aui-message warning shadowed information-macro">
<p class="title">Important</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>
In order to carry out the conversion process successfully, it is
necessary that TOTVS ECM is in its most current version update
package, available in the <a href="http://suporte.fluig.com"
class="external-link" rel="nofollow">Customer Portal</a>. If the
environment is outdated it is recommended to update it and then
proceed with the steps for conversion.
</p>
</div>
</div>
<p>Run backups described in the previous item and, if a new
database is used, restore the backup copy of the database on this new
one.</p>
<p>Before executing the conversion, it is necessary to follow some
procedures:</p>
<ol>
<li>Make sure that Fluig will respond on the same IP address and
HTTP/HTTPS port as the current version of TOTVS ECM. If you do not
use these same access criteria, start the TOTVS ECM service for this
new database, if applicable.<strong> </strong>When you start the
TOTVS ECM service, access the TOTVS ECM companies registers and
change access settings, i.e. the <strong>Web server</strong> and <strong>Web
port</strong> fields, as shown in Figure 1.<br />
<p>
<strong><br />
<img class="confluence-embedded-image image-center"
src="http://tdn.totvs.com/download/attachments/146182479/empresa.png?version=1&modificationDate=1403645521000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/146182479/empresa.png?version=1&modificationDate=1403645521000&api=v2"></strong>
</p>
<p align="center">
<strong>Figure 1- Company's parameters in the ECM.</strong>
</p>
<p align="center">
<strong><br /></strong>
</p>
</li>
<li>If you wish to change the location of the volumes, it is
important that you execute the action before the conversion so access
the Volume tab and make the necessary changes.<br />
<p>
<img class="confluence-embedded-image image-center"
src="http://tdn.totvs.com/download/attachments/146182479/volume.png?version=1&modificationDate=1403645532000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/146182479/volume.png?version=1&modificationDate=1403645532000&api=v2">
</p>
<p align="center">
<strong>Figure 2 - Data volume of TOTVS ECM.</strong>
</p>
<p align="center">
<strong><br /></strong>
</p>
</li>
<li>The number of registered users in TOTVS ECM cannot exceed the
number of available users in the License Service.</li>
<li>Make sure that all the users that are registered in TOTVS ECM
meet the following requirements:<br />
<ol>
<li>The user cannot possess duplicate login, email or
registration;</li>
<li>The user's login must have only alphanumeric characters,
period (.), hyphen (-) and underscore (_);</li>
<li>The name of the user cannot exceed the maximum limit of 255
characters;</li>
<li>The user's email must be a valid email address;</li>
<li>The user's password cannot be blank;</li>
</ol>If any of the users do not meet the requirements provided, it is
necessary to adapt them to these requirements;
</li>
<li>Remove any global event or other customization that handles
the posting of documents or other features of TOTVS ECM. For example:
a global event beforeDocumentPublisher that does not allow posting in
the root folder;</li>
<li>Remove all scheduled tasks registered in TOTVS ECM;<br />
<br />
<br /></li>
</ol>
<p>When you finish these procedures, disconnect and stop the TOTVS
ECM service. </p>
<p>
<span style="font-size: 10.0pt; line-height: 13.0pt;">From this
point on, the installation of Fluig can be executed according to the
instructions in the guide</span><a href="73075634.html">Fluig
installation (Installer) -Windows</a><span
style="font-size: 10.0pt; line-height: 13.0pt;"> or  </span><a
href="146181961.html">Fluig installation (Installer) -Linux</a><span
style="font-size: 10.0pt; line-height: 13.0pt;"> </span>
</p>
<h3 id="ConversãoTOTVSECMparaFluig-IniciandooFluig">Starting Fluig</h3>
<p>
<span style="font-size: 10.0pt; line-height: 13.0pt;">For the
migration process, when Fluig is initialized on a database used by
TOTVS ECM, table structures belonging to the latter remain the same.
However, Fluig will create its tables separately. </span>
</p>
<div class="aui-message hint shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
<p>
In the case of a new service initialization or failure on reboot, it
may be necessary to terminate processes with <strong>Image
name</strong> equal to <strong>soffice.bin </strong>and the location of the
file is for the Fluig installation directory in the Windows Task
Manager. This is accessible through the CTRL + SHIFT + ESC shortcut
keys or by right-clicking on the task bar and in the pop-up menu
selecting the <strong>Start the Task Manager</strong> option. If
these processes exist, they should be terminated.
</p>
</div>
</div>
<div class="aui-message warning shadowed information-macro">
<p class="title">Important</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>It is mandatory that the user used to boot the system by the
console mode or as operating system service has permission to change
the Fluig setup folders and volume used by Fluig.</p>
</div>
</div>
<p>Check the startup modes below and choose the one you want to use
to start Fluig:</p>
<a name="composition-deck-samples"></a>
<div id="samples" class="deck" history="false" loopcards="false"
effecttype="fade" effectduration="0.5" nextafter="0.0">
<ul class="tab-navigation"></ul>
<!-- // .tab-navigation -->
<div class="deck-cards panel" style="">
<div id="1" class="deck-card active-pane" style="" cssclass=""
accesskey="" label="Modo Console (Windows)" title="" nextafter="0"
effecttype="default" effectduration="-1.0">
<p>
Run the file <em><<FLUIG_HOME_PATH>>
\jboss\bin\standalone.bat</em>. With this a command prompt window opens
displaying the startup information and messages of the JBoss
server. When it is necessary to stop the execution of the system,
press the CTRL + C keys.
</p>
</div>
<div id="2" class="deck-card " style="" cssclass="" accesskey=""
label="Modo Servi&ccedil;o (Windows)" title="" nextafter="0"
effecttype="default" effectduration="-1.0">
<p>
Access Windows Services through Control Panel and Administrative
Tools group, or execute the <strong>services.msc</strong> command
in <strong>Command prompt</strong>. Locate the Fluig service and
click the <strong>Start the service</strong> button, on the menu
bar, or <strong>Start</strong> in the pop-up menu displayed by
right-clicking on the service.
</p>
<p align="center">
<img class="confluence-embedded-image"
src="http://tdn.totvs.com/download/attachments/146182479/conversor1.png?version=1&modificationDate=1403645513000&api=v2"
data-image-src="attachments/146182479/146118769.png">
</p>
<p align="center">
<strong>Figure 3 - Windows Services window. Fluig service
selected and initialized.</strong>
</p>
<p>
The Fluig startup conference can be observed through the log file
in <em><<FLUIG_HOME_PATH>>
\jboss\standalone\log\server.log</em>, when it has about 1.0 MB and
contains the inscription:
</p>
<p>
<em>HH:MM:SS,mmm INFO
[com.fluig.startup.service.FluigStartupBean] (EJB default - x)
===============================================</em><br />
<em>HH:MM:SS,mmm INFO
[com.fluig.startup.service.FluigStartupBean] (EJB default - x) ==
Fluig is up and running right now. ==</em><br />
<em>HH:MM:SS,mmm INFO
[com.fluig.startup.service.FluigStartupBean] (EJB default - x)
===============================================</em>
</p>
<p>The time for service startup may vary according to the
capabilities of the server on which Fluig will be executed.</p>
</div>
<div id="3" class="deck-card " style="" cssclass="" accesskey=""
label="Modo Console (Linux)" title="" nextafter="0"
effecttype="default" effectduration="-1.0">
<p>
Run the file <em><<FLUIG_HOME_PATH>>\jboss\bin\standalone.sh</em>.
With this the boot log is displayed in the terminal, with the boot
information and messages of the JBoss server. When it is necessary
to stop the execution of the system, press the CTRL + C keys.
</p>
</div>
</div>
</div>
<!-- // .deck -->
<div>
<h3 id="ConversãoTOTVSECMparaFluig-Conversão">Conversion</h3>
<p>At this point, you can start the conversion process. </p>
<div class="aui-message warning shadowed information-macro">
<p class="title">Important</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<ul>
<li>This is an irreversible process, because Fluig will do the
reading of the tables of TOTVS ECM and transport its data to the
respective tables of Fluig. Some tables of TOTVS ECM will be
deleted in this conversion process.</li>
<li><span>Failures can occur during the process, and
compromise the database. If this happens use the </span><span>backup
copy created earlier, to restore the database.</span></li>
<li><span><span>In case of use of the SQL Server
database, refer to the settings in item </span><a href="73078837.html">SQL
Server database settings</a><span>.</span></span></li>
<li><span><span><span>The <strong>Portal</strong>
and <strong>PortalPage</strong> type of documents will not be
converted. Its conversion must be executed manually, i.e. you
will need to create the pages on Fluig, through the <strong>My
Pages </strong> item in the  <strong>Control</strong> <strong>Panel</strong>tab,
<strong>WCM</strong>tab.
</span></span></span></li>
</ul>
</div>
</div>
<p>Pay attention to the following steps to start the conversion:</p>
<ol>
<li><span><span style="font-size: small;"><span
style="line-height: 13.0pt;">After initializing Fluig, it
is necessary to login using the </span></span>user name<span
style="font-size: small;"><span style="line-height: 13.0pt;"> <strong>wcmadmin</strong>
and password <strong>adm;</strong></span></span></span></li>
<li>Once you've logged in, access the <strong>Control
Panel</strong>menu item and click on the <strong>ECM</strong> tab, in that
tab access the <strong>Base converter </strong>option;
</li>
<li>With this, the base validation to verify that the conversion
can be started will be executed. Figure 4 illustrates this process;<br />
<br />
<p align="center">
<img class="confluence-embedded-image" width="500"
src="attachments/146182479/146118765.png"
data-image-src="attachments/146182479/146118765.png">
</p>
<p align="center">
<strong>Figure 4 - Process of conversion of ECM base to
Fluig.</strong>
</p>
<p align="center">
<strong><br /></strong>
</p>
</li>
<li>If non-conformities are not found, click <strong>Convert;</strong></li>
<li><span style="font-size: 10.0pt; line-height: 13.0pt;">When
you click <strong>Convert</strong>, a message is displayed, as
shown in Figure 5, indicating the beginning of the conversion;
</span><br />
<span style="font-size: 10.0pt; line-height: 13.0pt;"><br /></span>
<p>
<img class="confluence-embedded-image image-center" width="500"
src="attachments/146182479/146118766.png"
data-image-src="attachments/146182479/146118766.png">
</p>
<p align="center">
<strong>Figure 5 - Conversion process started.</strong><br />
<span style="font-size: 10.0pt; line-height: 13.0pt;"><br /></span>
</p></li>
<li><span style="font-size: 10.0pt; line-height: 13.0pt;">To
track the conversion process, access the file: <em><<FLUIG_HOME_PATH>>
\jboss\standalone\log\conversion.log;</em>
</span></li>
<li><span style="font-size: 10.0pt; line-height: 13.0pt;">The
phrase "Conversion completed successfully" appears at the end of
the log file and indicates the end of the conversion process;</span></li>
<li><span style="font-size: 10.0pt; line-height: 13.0pt;">From
this moment, it is possible to connect Fluig with users and
passwords that existed in TOTVS ECM. To manage companies, the user
wcmadmin is used and not wdkAdmin any longer.</span></li>
</ol>
<p>
<img class="confluence-embedded-image image-center"
src="attachments/146182479/146118768.png"
data-image-src="attachments/146182479/146118768.png">
</p>
<p align="center">
<strong>Figure 6 - Fluig login screen.</strong>
</p>
<p align="center">
<strong><br /></strong>
</p>
<h3 id="ConversãoTOTVSECMparaFluig-Pós-conversãooumigração">Post
conversion or migration</h3>
<p>When a conversion process is executed, some procedures are
necessary so that Fluig services can present its features properly.
The following steps are recommended:</p>
<ol>
<li>Indexation of volume.</li>
<li>Data services update for TOTVS ECM. This is the modification
of these services for the recreation of stubs, in case of changes in
the webservice URLs used.</li>
<li><p>
For migration and where TOTVS ECM was integrated with TOTVS
ECM/HCM, see if the folder <em><<FLUIG_HOME_PATH>>
\jboss\modules\com</em> contains the directories <strong>progress</strong>\<strong>main</strong> with
libraries (JAR) of their Progress. 
</p>
<div class="aui-message warning shadowed information-macro">
<p class="title">Attention</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>This is not the JAR generated by ProxyGen (Proxy
Generator), they are the old environment libraries registered in
TOTVS ECM. This procedure is necessary, because in this version
of the product such register of environments and indication of
libraries no longer exist. The JBoss AS 7, requires that access
to these common JAVA classes of Progress are initialized as a
module of JBoss.</p>
</div>
</div>
<p>Inside this folder next to libraries there must be a file
called "module.xml." Within its contents, all these libraries must
be related. Remember that the file must be saved with UTF-8 code
(without BOM). The file follows the standard:</p>
<div class="code panel pdl" style="border-width: 1px;">
<div class="codeContent panelContent pdl">
<pre class="theme: Confluence; brush: html/xml; gutter: false"
style="font-size: 12px;"><?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="com.progress">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="o4glrt.jar"/>
<resource-root path="common.jar"/>
<resource-root path="commonj.sdo.jar"/>
<resource-root path="ecore.change.jar"/>
<resource-root path="ecore.jar"/>
<resource-root path="ecore.resources.jar"/>
<resource-root path="ecore.sdo.jar"/>
<resource-root path="ecore.xmi.jar"/>
<resource-root path="openedge.jar"/>
<resource-root path="progress.jar"/>
</resources>
</module></pre>
</div>
</div>
<div class="aui-message hint shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
<p>
After this setting the restart of Fluig is mandatory so that
these libraries are loaded into the <em>classpath</em> of
JBoss AS 7. Until this is executed, the operations will return an
error like: JavaException: java.lang.ClassNotFoundException:
com.progress.open4gl.ProDataGraphHolder. Or another class in an
attempt to create an object in the <em>package</em> <em>com.progress.*</em>.
</p>
</div>
</div>
<div class="aui-message warning shadowed information-macro">
<p class="title">Alternative treatment</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>
A way to enable the use of these <em>classes</em> by
the <em>proxy</em> generated is to add the contents of
these libraries within the package of this <em>proxy</em>,
that is, the files of type and extension JAR are compressed files
like ZIP, each of these libraries can be opened by your preferred
file compression application (WinZIP, WinRAR, 7-ZIP, among
others) and their contents copied into the .JAR file of the <em>proxy</em>.
Only the folders and their "META-INF" contents should be ignored,
not copied.
</p>
</div>
</div>
<p> </p>
<p> </p></li>
<li>Re-add the global events or other customizations that have
been removed before starting the conversion;</li>
<li>Re-register the task schedules that were removed before
starting the conversion, if they are still needed;</li>
<li>If, when accessing Fluig, targeting occurs to the
address <em><host>:<port></em> which belonged to
TOTVS ECM, that means the address of access was not changed before
the conversion (as mentioned in the session <strong>Before
conversion</strong>)<strong> </strong>and therefore it will be
necessary to change the access address in Fluig, entering as <strong>wcmadmin</strong> and
going to the <strong>Control</strong><strong>Panel</strong> tab, <strong>WCM</strong>
tab, <strong>System settings</strong>item.<strong><br /></strong>
</li>
</ol>
<div>
<strong><br /></strong>
</div>
<div>
<strong><br /></strong>
</div>
</div>
</div> |
Índice
| Índice | ||||||
|---|---|---|---|---|---|---|
|
Objetivo
El objetivo de este guía es instruir a los administradores de sistemas que desean realizar la conversión del TOTVS ECM para la plataforma Fluig.
Conversión para el Fluig
Siga a continuación las etapas y procedimientos necesarios para la conversión del TOTVS ECM para el Fluig.
Copia de Seguridad
| Nota |
|---|
A fin de preservar los recursos y datos del TOTVS ECM en el caso que ocurra algún error durante el proceso de conversión es importante realizar una copia de seguridad de los siguientes ítems:
|
Antes de la Conversión
| Nota | ||
|---|---|---|
| ||
Para que el proceso de conversión se realice con éxito, es necesario que el TOTVS ECM esté en la versión más actual de los paquetes de actualización, disponible en el Portal de Clientes. En el caso que el ambiente esté desactualizado, se recomienda realizar la actualización y posteriormente proseguir con las etapas para conversión. |
Realice las copias de seguridad descritas en el ítem anterior y en el caso que se utilice una nueva base de datos, restaure la copia de seguridad de la base de datos sobre esta nueva base.
Antes de realizar la conversión es necesario realizar algunos procedimientos:
...
Figura 1 - Parámetros de la Empresa en el ECM.
...
Figura 2 - Volume(s) de dados do TOTVS ECM.
...
- El colaborador no puede poseer login, e-mail o matrícula duplicada;
- El login del colaborador debe poseer solamente caracteres alfanuméricos, punto (.), guión ( - ) y guión bajo (_);
- El nombre del colaborador no puede exceder el límite máximo de 255 caracteres;
- El e-mail del colaborador debe ser un e-mail válido;
- La contraseña del colaborador no puede ser en blanco.
...
Elimine todas las programaciones de tareas registradas en el TOTVS ECM.
Al finalizar estos procedimientos, desconecte y pare el servicio del TOTVS ECM.
A partir de eso, se puede realizar la instalación del fluig conforme a instrucciones disponibles en la guía Instalación Fluig (Instalador) - Windows o Instalación Fluig (Instalador) - Linux.
Iniciando el Fluig
Para el proceso de migración, cuando el Fluig se inicializa sobre una base de datos utilizada por el TOTVS ECM las estructuras de las tablas de este último permanecen de la misma forma. Sin embargo, el Fluig creará sus tablas, separadamente.
| Informações | ||
|---|---|---|
| ||
En el caso de que una nueva inicialización del servicio o fallas en la reinicialización puede ser necesario finalizar los procesos con Nombre de la Imagen igual a soffice.bin y el lugar del archivo esté para el directorio de instalación del Fluig en el Administrador de Tareas del Windows (Task Manager). Este es accesible por las teclas de atajo CTRL+SHIFT+ESC o haciendo clic con el botón derecho del mouse sobre la barra de tareas y en el menú popup seleccionar la opción de Iniciar el Administrador de Tarefas. Si estos procesos existen se deben finalizar. |
| Nota | ||
|---|---|---|
| ||
Es obligatorio que el usuario utilizado para inicializar el sistema por el modo console o como servicio del sistema operativo posea permiso de modificación de las carpetas de la instalación del Fluig y del(de los) Volumen(es) utilizado(s) por los Fluig. |
Verifique los modos de inicialización a seguir y elija aquel que desea utilizar para iniciar el Fluig:
| Deck of Cards | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
|
Conversión
En este momento, se puede iniciar el proceso de conversión.
| Nota | ||
|---|---|---|
| ||
|
Esté atento a los pasos a seguir para iniciar la conversión:
...
Figura 4 - Proceso de conversión de la base ECM para Fluig.
...
...
Figura 6 - Pantalla de login Fluig.
Posconversión o migración
Cuando un proceso de conversión se realiza, algunos procedimiento son necesarios para que los servicios del Fluig puedan presentar sus funcionalidades correctamente. Se recomiendan los siguientes pasos:
...
Para la migración y donde el TOTVS ECM se integraba al TOTVS EMS/HCM, se debe verificar si en la carpeta <<FLUIG_HOME_PATH>>\jboss\modules\com, existen los directorios progress\main con las bibliotecas (JAR) del respectivo Progress.
| Nota | ||
|---|---|---|
| ||
Esto no es el JAR, generado por el ProxyGen (Proxy Generator), son las bibliotecas del antiguo Ambiente registrado en el TOTVS ECM. Este procedimiento es necesario, pues en esta version del producto no existe más dicho registro de ambientes e indicación de las bibliotecas. El JBoss AS 7, requiere que el acceso a estas clases JAVA comunes del Progress se inicialicen como un módulo del JBoss. |
Dentro de esta carpeta junto a las bibliotecas debe existir un archivo “module.xml”. En su contenido todas estas bibliotecas se deben relacionar. Recordando que el archivo se debe guardar con la codificación UTF-8 (sin BOM). El archivo sigue el modelo:
| Bloco de código | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="com.progress">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="o4glrt.jar"/>
<resource-root path="common.jar"/>
<resource-root path="commonj.sdo.jar"/>
<resource-root path="ecore.change.jar"/>
<resource-root path="ecore.jar"/>
<resource-root path="ecore.resources.jar"/>
<resource-root path="ecore.sdo.jar"/>
<resource-root path="ecore.xmi.jar"/>
<resource-root path="openedge.jar"/>
<resource-root path="progress.jar"/>
</resources>
</module> |
| Informações | ||
|---|---|---|
| ||
Después de realizar esta configuración es obligatoria la reinicialización del Fluig para que estas bibliotecas se carguen en el classpath del JBoss AS 7. Hasta que esto se realice, las operaciones devolverán un error como: JavaException: java.lang.ClassNotFoundException: com.progress.open4gl.ProDataGraphHolder. U otra clase en el intento de crear un objeto dentro del packagecom.progress.*. |
| Nota | ||
|---|---|---|
| ||
Una forma de posibilitar la utilización de estas clases por el proxy generado es incluir el contenido de estas bibliotecas dentro del paquete de este proxy, es decir, los archivos del tipo y extensión JAR son archivos compactados como los del tipo ZIP, cada una de estas bibliotecas se puede abrir a través de su aplicación de compactación de archivos preferido (WinZIP, WinRAR, 7-ZIP, entre otros) y su contenido copiado para dentro del archivo JAR del proxy. Solamente las carpetas y su contenido “META-INF” se deben ignorar, no copiar. |
...
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas