Forte Release 2F

Hello all!
I would appreciate any information on the 2F release. Specifically, I am
looking for information on known bugs, environment and coding changes that
was required, behavioral changes noticed if any from the previous release,
level of effort that was required, etc. We are gearing up for this migration
and judging from past experience this could be a long process. We would like
to be better prepared this time around and any information will be greatly
appreciated.
Please include your email addresses also so that we can get in touch with
you if need be.
Also, I was wondering if there is a Forte User Group in the Washington, DC
area. If so, how often does the group meet and when is the next one?
Thanks in advance.
Gopal Krishnan
LCI International, McLean, VA
[email protected]
Tel: (703) 918 4630

Krishnan, Gopal wrote:
>
Hello all!
I would appreciate any information on the 2F release. Specifically, I am
looking for information on known bugs, environment and coding changes that
was required, behavioral changes noticed if any from the previous release,
level of effort that was required, etc. We are gearing up for this migration
and judging from past experience this could be a long process. We would like
to be better prepared this time around and any information will be greatly
appreciated.
Please include your email addresses also so that we can get in touch with
you if need be.
Also, I was wondering if there is a Forte User Group in the Washington, DC
area. If so, how often does the group meet and when is the next one?
Thanks in advance.
Gopal Krishnan
LCI International, McLean, VA
[email protected]
Tel: (703) 918 4630Krishnan,
I just upgraded my site to 2F two days ago. We are using Express also.
The upgrade was a success and it took the least (yes, you read that
correctly) amount of time I have ever spent. I would like to compliment
Forte on the packaging of 2F, first class! Some of the niceties include
a classy box, and comprehensive release notes (combined for Forte and
Express).
I have been installing Forte since 1.0 and understand your concerns. I
have not seen any problems under 2F. We have not had to make any coding
changes either.
Here are a few things I have learned doing installs:
1) Read the release notes thoroughly, they have a tremendous amount of
information in them. Also, make sure all developers get to read them.
The known bugs and workarounds can save developers from wasting time if
they encounter a known bug.
2) Make a simple migration plan. It does not take much time and I use
it as a checklist. The release notes have procedures on upgrading
repositories, environments and deployments. This will save you time and
make the install a success. We can not afford to be down, so I do the
upgrades dialed in from home.
3) Get a good backup before you start. You never know...
4) Export your environment definition so it can be reloaded from a file,
not your memory!
5) Load the client version of Forte on your LAN (PC_WIN, PC_NT, etc.
directories) so developers can upgrade their PC's in parallel.
I do not know of a Forte User Group in the Washington, DC. area.
However, if someone starts one, I know a lot of people that will join.
Good luck, I am sure you will not need it. Call me if you have any
questions.
Robert Crisafulli
[email protected]
AMISYS
301-838-7540

Similar Messages

Linked forte environments in Forte release 3

I am trying to link two Forte (3.0.E.0) environments together
following the discussion in the System Administration manual and although I
have had some success much of the material presented in the Forte manual
does not seem relevant to what I am trying to accomplish. I would be very
interested in talking (or emailing) with anyone who has some hands-on
experience with linked Forte environments (especially in Forte release 3).
Thanks,
Jim (Hutchinson)
Chordiant Software, Inc,
(650) 493-2506

You're not alone. I spent several hours thinking I did something wrong, but I think there must be some incompatability with the ie & db tags supplied with Forte and the MySQL 2.0.4 driver.
I've been searching the forums and the only suggestion that I've found is to not use the ie & db tags supplied with Forte and to replace them similar tags from Apache. Unfortunately, it isn't a tag for tag replacement. You're going to have to reference new tags with a different API.
I downloaded dbtags.jar from http://jakarta.apache.org/builds/jakarta-taglibs/nightly/projects/dbtags/
In looking at the documentation, it looks like they have tags that will do most of the things that the ie & db tags will do.
Good luck!
Scott

Forte Transaction Management & 2PC

Forte Transaction Management & 2PC
The main purpose of 2PC in a distributed transaction manager is
to enable recovery from a failure that occurs during the window
of transaction commit processing. The Forte transaction manager was built
with this in mind but only with respect to the "volatile" (or "in memory")
objects that Forte manages. What this implies is that because Forte stores
objects in memory and not persistently on disk, the requirement of recovery
for these objects is significantly reduced (if not eliminated all together).
Forte follows a distributed 2PC model in that tasks and messages carry
along with them transaction identification and, during commit processing,
every distributed participant is polled for its availability to commit
the transaction. Applications saving persistent data to disk during a
distributed Forte transaction need to concern themselves with the potential
for failure during the commit processing window. Forte's prepare phase polls
each site (confirming a communications link with each distributed participant)
but no prepare request goes to the database primarily because (in release 1 and
2 of forte) no database supported a general distributed two-phase commit
(one could take issue with that in the case of Sybase, but rather than debate
this point, suffice it to say that the general direction in the industry for
support of this functionality was through TP monitors -- more on that later).
Once all sites are ready to commit Forte expects that the commit will
complete successfully. If at this moment, for example, a participating
Sybase server terminates (with data not yet committed) while a participating
Oracle server has already committed its unit of work, then the outcome of
the distributed transaction is inconsistent - if no one has yet committed
Forte will still abort the transaction. This "window of inconsistency"
is documented in the Forte TOOL manual.
Mission critical applications that require distributed transactions can
address this window of inconsistency in a number of ways:
* Utilize a TP monitor such as Encina (see below)
* Log distributed updates in an auxiliary database table (much like a
distributed transaction monitor's transaction-state log). This approach has
been the traditional banking application solution prior to the commercial
availability of products like Encina, Tuxedo, TopEnd, etc.
This solution is somewhat complex and is usually not generic enough
so as not to have to change code every time a new table or database
site is introduced into the application's data model.
* Rearrange the data model in order to eliminate the need for distributed
transactions. This is usually only a temporary solution (with smaller
numbers of active clients) and cannot be applied to complex legacy systems.
With the advent of the X/Open distributed transaction architecture (the
XA Interface) more database vendors have found that by complying with the
XA interface they can plug their database-specific implementation of
transaction into a globally managed transaction, with commit and abort
processing being conducted by a central coordinator. Of course, the
overall transaction manager coordinating the global transaction must
itself, persistently record the state of the different distributed
branches participating in the transaction. A significant portion of
the functionality provided by products such as Encina, Tuxedo, TopEnd and
OpenTP1 is to provide exactly this global transaction management.
Rather than extend the Forte distributed transaction manager with the
functionality necessary to manage and recover distributed transactions
that modify data on disk, Forte has chosen to integrate with the emerging
set of commercial transaction monitors and managers. This decision was
built into the original design of the Forte transaction model (using XA and
early Tuxedo white-papers as guidelines):
* In Forte release 2 an integration with Encina was delivered.
* In January 1997 a press release announced an integration of
OpenTP1 with Forte for release 3.
* The Forte engineering staff is currently investing integration
with other transaction management products as well.
Neil Goodman,
Forte Development.

You don't. ("manage" a transaction)
There is nothing really to "manage".
A transaction is automatically started when you make any changes to data (e.g. fire off a DML statement).
You simply needs to issue a COMMIT or ROLLBACK when needed. A COMMIT at the end of the business transaction and not before (i.e. no committing every n number of rows). A ROLLBACK when hitting an exception or business logic error that requires the uncommitted changes to be undone.
That in a nutshell is it. It is that simple.
Oracle also supports creating savepoints and rolling back only some changes made thus far in the transaction.
The only other thing to keep in mind that a DDL in Oracle issues an implicit commit. Firing off a DDL with cause any exiting uncommitted transaction to be committed.
Transaction "logic/management" should not be made more complex than this.

Re: (forte-users) Forte on Solarix box problem

Hi All,
Thank you very much, for all the help you
people extended towards this problem.Its solved, the
problem was i had 2 users, and i started from one user
Nodemanager ( which does not have oracle home path
set) and from the other user id, i started the
launcher, ( which have oracle home set), so the
application, was running locally, but when i
distributed the application, it was not finding oracle
home variable from the other user, from which node
manager was started. So that was the problem. I found
this specifically after setting FORTE_STACK_SIZE,
variable(as suggested by Thomas), it was throwing
error saying that, tns name is not resolved,( kudos to
Thomas :) ).
Once again thank you all.
Babu
--- Thomas Degen - Sun Germany Forte Tools - Bonn
<thomas.degensun.com> wrote:
>
Hi Babu,
ok, maybe we need to go now a bit more in some
details of
your Forte nodemanager environment on the Sparc
Solaris box.
Q1: Which operating system release ? Solaris
2.51,2.6,7 or 8 ?
Q2: Which Forte Release are you running on all nodes
Q3: Where's the Forte environment manager located ?
Q4: Which Oracle RDBMS release have you installed on
the Sun ?
Q5: Which Oracle client release have you probably
installed
on your PC which is running NT4 I guess ?
(These questions are just the generic Tech Support
approach
to get an idea about your environment).
Q6: You mentioned in your very first message that
during
Forte installation on the Sun, you've left the
path to
Oracle empty....it is mandatory for the Forte
nodemanager
on any box/operating system to find in its
environment
the relevant third party environmental
informations...
For Oracle the Forte nodemanager on Sun
requires a
valid setting for ORACLE_HOME !
Could you send me the complete environment for
the user
who is starting the Forte nodemanager on your
Sun ?
Q7: This is more a necessary suggestion than a
question
but is and when yes, how have you setted
FORTE_STACK_SIZE
on the Sun ?
If it's not there or only set as
FORTE_STACK_SIZE=42000,
then add or reconfigure FORTE_STACK_SIZE to
100000 in the
nodemanager's environment and re-boot the
nodemanager!
Q8: Once more a recommendation than question but can
you
just try to access your Oracle DB instance with
the Forte
sample program DynamicSQL ? You will find this
in
the $FORTE_ROOT/install/examples/database
directory
and it will require the Utility plan that you
may import
from $FORTE_ROOT/install/examples/frame .
Try to access your Oracle instance from local
directly
out of your workspace and later on full
distributed
via an own Forte server partition from the
Partition
Workshop. Send to me all errors thrown during
these
procedures on the client and within the remote
server
partition logfile on the Sun.
BTW: When you can access the Oracle RDBMS running in
the
Forte IDE locally, this is an indicator to me that
you have
setted up the Oracle client on your PC and have
configured
Oracle locally correctly (tnsnames.ora) to connect
to your
remote Oracle instance...hence when test running
locally, Forte
will use this locally configured Oracle SQL*Net V2
client
to connect to your remote Oracle RDBMS instance.
That's one
shortcut making it possible for you as the Forte
developer
to debug DB access within the Forte IDE...when
running completly
distributed debugging of remote partitions is not
possible.
Hope this helps ! Best Regards from Germany !
Thomas
Thomas Degen
Sun Microsystems - Forte Tools
Forte CTE & Sustaining Group
Technical Support Germany
tel.:+49.228/91499-50
MailTo:thomas.degensun.com
At 10:55 09.09.00 -0700, you wrote:
HI Mark,
I have setup all the resources properly.Even
given new names, and tried again, no use so far.
Thanks,
Babu
--- Mark Musgrove <musgrovemarkyahoo.com> wrote:
The message "Loading partition
DatabaseTestSolaris_cl0_Part2 built on
<unknown>."
is
bizarre.
It sounds like the partition workshop is notassigning
the partition containing the DBSession to thecorrect
server node. Normally you would see "built on<node name>."
Have you setup the supported resource managerson
the solaris node? If not, then forte will notassign the
DBSession to the correct node. You mustdesignate in
the environment that the server node supportsall of
the required resources (Oracle, ODBC, etc).
Mark Musgrove
Senior Consultant
Object Technologies, Inc
(540) 977-3861 (home)
(540) 977-2794 (fax)
http://mail.yahoo.com/

Hi All,
Thank you very much, for all the help you
people extended towards this problem.Its solved, the
problem was i had 2 users, and i started from one user
Nodemanager ( which does not have oracle home path
set) and from the other user id, i started the
launcher, ( which have oracle home set), so the
application, was running locally, but when i
distributed the application, it was not finding oracle
home variable from the other user, from which node
manager was started. So that was the problem. I found
this specifically after setting FORTE_STACK_SIZE,
variable(as suggested by Thomas), it was throwing
error saying that, tns name is not resolved,( kudos to
Thomas :) ).
Once again thank you all.
Babu
--- Thomas Degen - Sun Germany Forte Tools - Bonn
<thomas.degensun.com> wrote:
>
Hi Babu,
ok, maybe we need to go now a bit more in some
details of
your Forte nodemanager environment on the Sparc
Solaris box.
Q1: Which operating system release ? Solaris
2.51,2.6,7 or 8 ?
Q2: Which Forte Release are you running on all nodes
Q3: Where's the Forte environment manager located ?
Q4: Which Oracle RDBMS release have you installed on
the Sun ?
Q5: Which Oracle client release have you probably
installed
on your PC which is running NT4 I guess ?
(These questions are just the generic Tech Support
approach
to get an idea about your environment).
Q6: You mentioned in your very first message that
during
Forte installation on the Sun, you've left the
path to
Oracle empty....it is mandatory for the Forte
nodemanager
on any box/operating system to find in its
environment
the relevant third party environmental
informations...
For Oracle the Forte nodemanager on Sun
requires a
valid setting for ORACLE_HOME !
Could you send me the complete environment for
the user
who is starting the Forte nodemanager on your
Sun ?
Q7: This is more a necessary suggestion than a
question
but is and when yes, how have you setted
FORTE_STACK_SIZE
on the Sun ?
If it's not there or only set as
FORTE_STACK_SIZE=42000,
then add or reconfigure FORTE_STACK_SIZE to
100000 in the
nodemanager's environment and re-boot the
nodemanager!
Q8: Once more a recommendation than question but can
you
just try to access your Oracle DB instance with
the Forte
sample program DynamicSQL ? You will find this
in
the $FORTE_ROOT/install/examples/database
directory
and it will require the Utility plan that you
may import
from $FORTE_ROOT/install/examples/frame .
Try to access your Oracle instance from local
directly
out of your workspace and later on full
distributed
via an own Forte server partition from the
Partition
Workshop. Send to me all errors thrown during
these
procedures on the client and within the remote
server
partition logfile on the Sun.
BTW: When you can access the Oracle RDBMS running in
the
Forte IDE locally, this is an indicator to me that
you have
setted up the Oracle client on your PC and have
configured
Oracle locally correctly (tnsnames.ora) to connect
to your
remote Oracle instance...hence when test running
locally, Forte
will use this locally configured Oracle SQL*Net V2
client
to connect to your remote Oracle RDBMS instance.
That's one
shortcut making it possible for you as the Forte
developer
to debug DB access within the Forte IDE...when
running completly
distributed debugging of remote partitions is not
possible.
Hope this helps ! Best Regards from Germany !
Thomas
Thomas Degen
Sun Microsystems - Forte Tools
Forte CTE & Sustaining Group
Technical Support Germany
tel.:+49.228/91499-50
MailTo:thomas.degensun.com
At 10:55 09.09.00 -0700, you wrote:
HI Mark,
I have setup all the resources properly.Even
given new names, and tried again, no use so far.
Thanks,
Babu
--- Mark Musgrove <musgrovemarkyahoo.com> wrote:
The message "Loading partition
DatabaseTestSolaris_cl0_Part2 built on
<unknown>."
is
bizarre.
It sounds like the partition workshop is notassigning
the partition containing the DBSession to thecorrect
server node. Normally you would see "built on<node name>."
Have you setup the supported resource managerson
the solaris node? If not, then forte will notassign the
DBSession to the correct node. You mustdesignate in
the environment that the server node supportsall of
the required resources (Oracle, ODBC, etc).
Mark Musgrove
Senior Consultant
Object Technologies, Inc
(540) 977-3861 (home)
(540) 977-2794 (fax)
http://mail.yahoo.com/

RE: Using CORBA as Middleware with Forte'

This is one solution when the two sides want to be somewhat independent of
each other.. To use Forte messaging the environments have to be connected,
identical Forte versions, probably identical versions of all objects
involved (rather than just correct IDL), etc. I've toyed with this as well
for a client with two major Forte application development efforts occurring
in completely different business units.
-Greg
-----Original Message-----
From: Sean Brown [SMTP:[email protected]]
Sent: Thursday, October 22, 1998 1:56 PM
To: Giuseppe Sorce; Lenny Hon
Cc: [email protected]
Subject: Re: Using CORBA as Middleware with Forte'
If you don't mind me asking, why would you ever want to do this? If
you are
talking between two Forte services, why would you not want to use
the native
protocol which is bound to be more efficient since it was written
specifically for that purpose? The only reason I can think of is if
you
need two Forte services to talk to each other through a firewall and
the
firewall is configured to only allow certain protocols through, such
as
IIOP. Is this what you are trying to do? If not, what is your
reasoning?
Thanks,
Sean Brown
Cornice Consulting Inc.
mailto:[email protected]
-----Original Message-----
From: Giuseppe Sorce <[email protected]>
To: Lenny Hon <[email protected]>
Cc: [email protected] <[email protected]>
Date: Thursday, October 22, 1998 10:05 AM
Subject: RE: Using CORBA as Middleware with Forte'
>
>Lenny, I'm sorry but I think that my problem is more complicated.
>No java clients or java servers are involved: I want to use CORBA
as
>middleware between 2 different Forte' partitions (running on
different
>forte' environments).
>For example imagine you have 2 different Forte' applications (say
>application A and application B) in 2 different forte'
environments.
>Now imagine to define an IIOP-enabled service object (Inbound) in
>application A and, starting from the generated IDL (using corbagen
utility)
>to create a IIOP-enabled service object (Outbound) in application
B.
>Application B will be the Corba Client and application A will be
the Corba
>Server.
>They don't use Forte' middleware for communication (they are in
different
>Forte' envs).
>
>Giuseppe Sorce
>
>
>
>
>
>Lenny Hon <[email protected]> on 22/10/98 15.35.40
>
>Please respond to Lenny Hon <[email protected]>
>
>To: Giuseppe Sorce/CSI/IT, "'[email protected]'"
> <[email protected]>
>cc:
>Subject: RE: Using CORBA as Middleware with Forte'
>
>
>
>
>I have successfully used Forte IIOP-enabled service object to
communicate
>with my client Java program that uses VisiBroker 3.2 for Java ORB.
For the
>information, you can read the Forte Web Enterprise manual and the
following
>tech notes: 10950, 10951, 11145, 11152. I found them from Web
manual.
>
>Lenny Hon
>
>-----Original Message-----
>From: Giuseppe Sorce [mailto:[email protected]]
>Sent: Thursday, October 22, 1998 5:58 AM
>To: [email protected]
>Subject: Using CORBA as Middleware with Forte'
>
>
>
>I would like to find a way to use CORBA middleware as an
alternative for
>communications between Forte' partitions (I'm using Forte' rel.
3.0.G plus
>Visibroker 3.1 ORB).
>
>I found a technical note (ID 10520) but it is quite old and it is
related
> to Forte' release 2.0.E.2 (!).
>
>Any experience with Forte' release 3 and Visibroker would be
greatly
> appreciated.
>
>
>
>TIA
>
>Giuseppe Sorce
>
>CSI Piemonte - C.so Unione Sovietica 216 - 10134 Torino - ITALY
>
>tel. +39-011-3168736
>
>fax +39-011-3168212
>
>e-mail [email protected]
>
>url http://www.csi.it
>
>
>
>-
>To unsubscribe, email '[email protected]' with
>'unsubscribe forte-users' as the body of the message.
>Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
>-
>To unsubscribe, email '[email protected]' with
>'unsubscribe forte-users' as the body of the message.
>Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
>
>
>
>
>
>
>-
>To unsubscribe, email '[email protected]' with
>'unsubscribe forte-users' as the body of the message.
>Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

This is one solution when the two sides want to be somewhat independent of
each other.. To use Forte messaging the environments have to be connected,
identical Forte versions, probably identical versions of all objects
involved (rather than just correct IDL), etc. I've toyed with this as well
for a client with two major Forte application development efforts occurring
in completely different business units.
-Greg
-----Original Message-----
From: Sean Brown [SMTP:[email protected]]
Sent: Thursday, October 22, 1998 1:56 PM
To: Giuseppe Sorce; Lenny Hon
Cc: [email protected]
Subject: Re: Using CORBA as Middleware with Forte'
If you don't mind me asking, why would you ever want to do this? If
you are
talking between two Forte services, why would you not want to use
the native
protocol which is bound to be more efficient since it was written
specifically for that purpose? The only reason I can think of is if
you
need two Forte services to talk to each other through a firewall and
the
firewall is configured to only allow certain protocols through, such
as
IIOP. Is this what you are trying to do? If not, what is your
reasoning?
Thanks,
Sean Brown
Cornice Consulting Inc.
mailto:[email protected]
-----Original Message-----
From: Giuseppe Sorce <[email protected]>
To: Lenny Hon <[email protected]>
Cc: [email protected] <[email protected]>
Date: Thursday, October 22, 1998 10:05 AM
Subject: RE: Using CORBA as Middleware with Forte'
>
>Lenny, I'm sorry but I think that my problem is more complicated.
>No java clients or java servers are involved: I want to use CORBA
as
>middleware between 2 different Forte' partitions (running on
different
>forte' environments).
>For example imagine you have 2 different Forte' applications (say
>application A and application B) in 2 different forte'
environments.
>Now imagine to define an IIOP-enabled service object (Inbound) in
>application A and, starting from the generated IDL (using corbagen
utility)
>to create a IIOP-enabled service object (Outbound) in application
B.
>Application B will be the Corba Client and application A will be
the Corba
>Server.
>They don't use Forte' middleware for communication (they are in
different
>Forte' envs).
>
>Giuseppe Sorce
>
>
>
>
>
>Lenny Hon <[email protected]> on 22/10/98 15.35.40
>
>Please respond to Lenny Hon <[email protected]>
>
>To: Giuseppe Sorce/CSI/IT, "'[email protected]'"
> <[email protected]>
>cc:
>Subject: RE: Using CORBA as Middleware with Forte'
>
>
>
>
>I have successfully used Forte IIOP-enabled service object to
communicate
>with my client Java program that uses VisiBroker 3.2 for Java ORB.
For the
>information, you can read the Forte Web Enterprise manual and the
following
>tech notes: 10950, 10951, 11145, 11152. I found them from Web
manual.
>
>Lenny Hon
>
>-----Original Message-----
>From: Giuseppe Sorce [mailto:[email protected]]
>Sent: Thursday, October 22, 1998 5:58 AM
>To: [email protected]
>Subject: Using CORBA as Middleware with Forte'
>
>
>
>I would like to find a way to use CORBA middleware as an
alternative for
>communications between Forte' partitions (I'm using Forte' rel.
3.0.G plus
>Visibroker 3.1 ORB).
>
>I found a technical note (ID 10520) but it is quite old and it is
related
> to Forte' release 2.0.E.2 (!).
>
>Any experience with Forte' release 3 and Visibroker would be
greatly
> appreciated.
>
>
>
>TIA
>
>Giuseppe Sorce
>
>CSI Piemonte - C.so Unione Sovietica 216 - 10134 Torino - ITALY
>
>tel. +39-011-3168736
>
>fax +39-011-3168212
>
>e-mail [email protected]
>
>url http://www.csi.it
>
>
>
>-
>To unsubscribe, email '[email protected]' with
>'unsubscribe forte-users' as the body of the message.
>Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
>-
>To unsubscribe, email '[email protected]' with
>'unsubscribe forte-users' as the body of the message.
>Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
>
>
>
>
>
>
>-
>To unsubscribe, email '[email protected]' with
>'unsubscribe forte-users' as the body of the message.
>Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Random numbers in Forte V 1.0

Hi everyone,
has anyone implemented a method to generate random numbers in Forte Release 1?
Forte release 2 has just such a utility object, but would love some
already written code if anyone has it.
Thanks
John
John Jamison
Engineering Manager
Sage Solutions, Inc.
415 392 7243 x 508
[email protected]

For everyone's info, there is one on the FSHARE CD that I contributed.
It is called 'ransort' I believe. It will randomly generate as many
random numbers as desired, and then provide another option to sort
them. We no longer need the random generation part in V2, but the
QuickSort routine is very fast, and worth taking a look at.
Send me a note if you don't have access to FSHARE, and would prefer
an export over the net.
Lee Wei
>
Hi everyone,
has anyone implemented a method to generate random numbers in Forte Release 1?
Forte release 2 has just such a utility object, but would love some
already written code if anyone has it.
Thanks
John
John Jamison
Engineering Manager
Sage Solutions, Inc.
415 392 7243 x 508
[email protected]

Bug Forte F

Hi to everybody,
I hope you can help me.
I was wondering if someone knows about bugs of Forte release F.
We had a client server application developed with Forte Express (client
Windows NT, server Sun Solaris) that starts at 08.00 a.m. every day.
At beginning clients connect to the server (cluster Sun) until circa
8.50 a.m. gradually, then at 9.10 a.m. they are more numerous until we
have almost 400 clients connected.
Usually between 9.00 and 9.30 a.m. the node manager crashes. I specify
that the memory setted with -fm flag is more than double of used memory
and there are no other different processes started on the server during
this period.
We don't think that it could be a problem due to the application
because, in this case, the partitions (compiled) should crash but, on
the contrary, they stay up.
Thanks anyway and happy new year,
Dr. Tesi Giovacchino
Fortè Developper
Telesoft S.p.A.

Hi to everybody,
I hope you can help me.
I was wondering if someone knows about bugs of Forte release F.
We had a client server application developed with Forte Express (client
Windows NT, server Sun Solaris) that starts at 08.00 a.m. every day.
At beginning clients connect to the server (cluster Sun) until circa
8.50 a.m. gradually, then at 9.10 a.m. they are more numerous until we
have almost 400 clients connected.
Usually between 9.00 and 9.30 a.m. the node manager crashes. I specify
that the memory setted with -fm flag is more than double of used memory
and there are no other different processes started on the server during
this period.
We don't think that it could be a problem due to the application
because, in this case, the partitions (compiled) should crash but, on
the contrary, they stay up.
Thanks anyway and happy new year,
Dr. Tesi Giovacchino
Fortè Developper
Telesoft S.p.A.

Multi-Lingual Forte Applications

We have at least one application site that needs to have their applications in
multiple languages. If any of you out there have experience in doing this and
can offer tips/techniques it is appreciated.
Also, have any of you evaluated Lindhard Forte Solutions product called
Ambassador Translation Wizard or know
of any other products?
Thanks in advance,
Peggy Adrian
Global Forte Support
Eli Lilly and Company
[email protected]

Hello Peggy Lynn & Joseph,
My name is Kerry Bellerose. I work for Lindhard Forte Solutions
and I saw your note in the Forte User's list concerning multi-lingual
applications.
I just wanted to send out a quick note to let you know that we would
be happy to answer any questions you have about the Ambassador
Translation Wizard.
Did you know that you can download a free demo version that you can
use to quickly evaluate the product yourself? All you need is a PC
running Windows 95 or Windows NT and Forte release 2 or release 3.
Just go to our web page at:
http://www.lindhard.com/forte/ambassador.html
Then select the Download a Free Demo Version image. The demo version
is very simple to install (it comes packaged in a self-extracting
installation program that are common in windows).
The demo version itself is a Forte application, not an animated
presentation, which means you can actually use the program directly
to get a complete understand of how it works.
The only restriction is that the demo version will only translate
the demo project we provide. Otherwise, it has all the functionality
of the full release.
As far as we know, there are no other products available on the
market that automate the process of adding multi-lingual support
to an application. The only alternative is to hand-code your
own solution. As Joseph points out, this is a lot of work,
including at least hundreds of GetMsg statements.
But multi-lingual support requires more than just writing GetMsg
statements, and Ambassador does much more than just automatically
generate this code for you. Ambassador also maintains this code
as you modify your application. Ambassador generates the message
catalog for you. Ambassador minimizes the amount of translation
work you need to do by reducing the number duplicate strings in
your message catalogs. Ambassador also provides a Translation
Editor to make the translation work itself easier. And Ambassador
supports all the languages that Forte supports, both European and
Asian.
All in all, compared with manually supporting multi-lingual
applications in Forte, Ambassador can potentially save your
project months of developer time. That is why there are already
several Forte customers who have choosen Ambassador, and others
that have approved it for use in appropriate projects.
Please let us know if we can help out in any way.
Cheers,
Kerry
PS. If for any reason you are unable to access our web page,
please let us know, we'll be happy to send you a copy
of the demo version on CD ROM.
| | / \ Kerry Bellerose e-mail: [email protected]
| || C | FORTE' SOLUTIONS http://www.lindhard.com/
| | \___/ Lindhard Computer Systems direct: +45 45 94 01 03
| |_____ Datavej 52 desk: +45 45 82 21 21
| | 3460 Birkeroed fax: +45 45 82 21 22
|_________| Denmark

Forte M / ORACLE 8.1.5 upgrade

Hi,
We plan to upgrade to Forte Release M and ORACLE release 8.1.5. We have the
technical note information. We also would like to find out whether any of
you have experienced with this upgrade.
Appreciate any information that you can share with us.
Thanks,
Sharon Hampe
CIA & Systems Integration
Concert Telecommunications
2033 Gateway Place
Suite 200
San Jose, CA 95110-1002
USA
Phone: +1 408 501 4813
Fax: +1 408 501 4953
Email: sharon.hampeconcert.com
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
Antigen for the presence of computer viruses.
http://www.concert.com
**********************************************************************

Please refer [url http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/conditions10a.htm
]'Patterns Without % Example' on Oracle9i SQL Reference.
Here is [url http://download-west.oracle.com/docs/cd/F49540_01/DOC/server.815/a67779/operator.htm#997970]Oracle8i SQL Reference.
If a pattern does not contain the "%" character, the condition can be TRUE only if both operands have the same length.
So... there are bugs on 8.1.x, 9.2.0.4...
SQL> select * from v$version where rownum <= 1;
BANNER
Personal Oracle7 Release 7.3.2.3.1 - Production Release
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
no rows selected
SQL> select * from v$version where rownum <= 1;
BANNER
Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
COL1
xyz
SQL> select * from v$version where rownum <= 1;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
COL1
xyz
SQL> select * from v$version where rownum <= 1;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
SQL> create table tab1 (col1 char(6));
Table created.
SQL> insert into tab1 values ('xyz');
1 row created.
SQL> select * from tab1 where col1 like 'xyz';
no rows selected

Re: Actuate/Forte, multithreading API calls

Geoff,
Your link to the Actuate API looks great, and it came just in
time: I had just started doing it myself.
A question: how can calls to the Actuate API be multithreaded?
Your C project has the extended property MultiThreaded = FALSE.
That's probably prudent, since we don't know how the Actuate
application works internally. However, we have a need for
running both (i) intensive reports and (ii) on-demand light
reports simultaneously. So, we need to multithread those two
sorts of tasks.
A possible way to multithread Actuate would be to load separate
copies of the dll's for each of the two tasks. Now, I don't
know how dynamic loading works, but my guess is that there is
only one copy per OS process, which means only one copy per
running Forte application.
John Hodgson |Descartes Systems Group Inc.|[email protected]
Systems Engineer|120 Randall Drive |http://www.descartes.com
|Waterloo, Ontario |Tel.: 519-746-8110 x250
|CANADA N2V 1C6 |Fax: 519-747-0082
Geoff Puterbaugh wrote:
>
I just recently completed a two-way integration project
between Forte and Actuate. To make both ways work for
you, you will need Forte release 3 (now in beta).
The integration project shows you how to use the Actuate
API from Forte (Forte --> Actuate) to set up report runs,
print reports, parameterize reports, etc. (You still have
to create the reports using the Actuate Developer's Workbench.)
This part should work with any version of Forte.
Going the other way (Actuate --> Forte) requires the OLE
automation features found in Forte R3. This enables a
Forte service object to fetch the data for your report,
as an alternative or addition to the standard SQL queries
running against an RDBMS.
You can find documentation and source code on the Forte
home page, under Technical Info, and then "Shareware." You
need a password to get there, but Forte technical support
can provide you with one in a jiffy.
Hope this helps some!
Geoff

Geoff,
Your link to the Actuate API looks great, and it came just in
time: I had just started doing it myself.
A question: how can calls to the Actuate API be multithreaded?
Your C project has the extended property MultiThreaded = FALSE.
That's probably prudent, since we don't know how the Actuate
application works internally. However, we have a need for
running both (i) intensive reports and (ii) on-demand light
reports simultaneously. So, we need to multithread those two
sorts of tasks.
A possible way to multithread Actuate would be to load separate
copies of the dll's for each of the two tasks. Now, I don't
know how dynamic loading works, but my guess is that there is
only one copy per OS process, which means only one copy per
running Forte application.
John Hodgson |Descartes Systems Group Inc.|[email protected]
Systems Engineer|120 Randall Drive |http://www.descartes.com
|Waterloo, Ontario |Tel.: 519-746-8110 x250
|CANADA N2V 1C6 |Fax: 519-747-0082
Geoff Puterbaugh wrote:
>
I just recently completed a two-way integration project
between Forte and Actuate. To make both ways work for
you, you will need Forte release 3 (now in beta).
The integration project shows you how to use the Actuate
API from Forte (Forte --> Actuate) to set up report runs,
print reports, parameterize reports, etc. (You still have
to create the reports using the Actuate Developer's Workbench.)
This part should work with any version of Forte.
Going the other way (Actuate --> Forte) requires the OLE
automation features found in Forte R3. This enables a
Forte service object to fetch the data for your report,
as an alternative or addition to the standard SQL queries
running against an RDBMS.
You can find documentation and source code on the Forte
home page, under Technical Info, and then "Shareware." You
need a password to get there, but Forte technical support
can provide you with one in a jiffy.
Hope this helps some!
Geoff

Actuate/Forte

I just recently completed a two-way integration project
between Forte and Actuate. To make both ways work for
you, you will need Forte release 3 (now in beta).
The integration project shows you how to use the Actuate
API from Forte (Forte --> Actuate) to set up report runs,
print reports, parameterize reports, etc. (You still have
to create the reports using the Actuate Developer's Workbench.)
This part should work with any version of Forte.
Going the other way (Actuate --> Forte) requires the OLE
automation features found in Forte R3. This enables a
Forte service object to fetch the data for your report,
as an alternative or addition to the standard SQL queries
running against an RDBMS.
You can find documentation and source code on the Forte
home page, under Technical Info, and then "Shareware." You
need a password to get there, but Forte technical support
can provide you with one in a jiffy.
Hope this helps some!
Geoff

Andrew,
There is some stuff on the shareware section of Forte's web site. I think
it is just the wrappering of the C-API's
Regards,
Richard Stobart
Consultant, ECSoft, UK
101 Wigmore Street
London W1H 9AA
(0171) 355 1101
-----Original Message-----
From: Andrew Leong <[email protected]>
To: '[email protected]' <[email protected]>
Date: 26 March 1998 03:30
Subject: Actuate & Forte Integration.
Hi,
I am using forte (3.0.f.2) and actuate (3.0). And looking to see if we
can integrate actuate to my forte application directly, that is by
passing the informix database.
Opinions are welcome.
Andrew Leong
Manager Project & Network
Kontena Nasional Berhad
email : [email protected]
tel : 603-774-0928 fax : 603-774-0652

Forte TIBCO support in R3

Hi,
In the "Forte Release 3 Feature Summary" I read that R3 somehow "integrates" Teknekron TIBCO messaging system:
since we are TIBCO distributors for Italy and we have quite a few customers using it, is it possible to know
the details of this integration? Has anybody ever used this new feature? (We have already interafaced to TIBCO
using the External Connection Class and would like to know the advantages, if any, of this new "technique").
Thanks,
Ernesto Moscatelli
EDS Italy
Banking Division

Hi,
In the "Forte Release 3 Feature Summary" I read that R3 somehow "integrates" Teknekron TIBCO messaging system:
since we are TIBCO distributors for Italy and we have quite a few customers using it, is it possible to know
the details of this integration? Has anybody ever used this new feature? (We have already interafaced to TIBCO
using the External Connection Class and would like to know the advantages, if any, of this new "technique").
Thanks,
Ernesto Moscatelli
EDS Italy
Banking Division

Forte Connected Environments

Hello,
Is there anybody on this mailing list who has experience in
using forte connected environments? Particularly to do with named
anchored objects?
We are attempting to use named anchored objects to communicate
between 2 forte connected environments and are having a few problems
with the nameservice.
When the application starts up we register the anchored objects.
However when we check the nameservice entries some (not all) of the
anchored objects are shown as unavailable and cannot be found using
BindObject. If we deregister the object and register it again it
becomes available and can be used.
No exceptions are raised when the objects are registered but the
object cannot be found.
We are running Forte release 3.0.G.2 on Windows NT server and
Window95 client.
Any Thoughts?
David McPaul
Lumley Technology
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hello,
Is there anybody on this mailing list who has experience in
using forte connected environments? Particularly to do with named
anchored objects?
We are attempting to use named anchored objects to communicate
between 2 forte connected environments and are having a few problems
with the nameservice.
When the application starts up we register the anchored objects.
However when we check the nameservice entries some (not all) of the
anchored objects are shown as unavailable and cannot be found using
BindObject. If we deregister the object and register it again it
becomes available and can be used.
No exceptions are raised when the objects are registered but the
object cannot be found.
We are running Forte release 3.0.G.2 on Windows NT server and
Window95 client.
Any Thoughts?
David McPaul
Lumley Technology
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Calling 16 bit OLE server from Forte H2

All,
A Forte application loads and makes calls to a 16 bit OLE server. When the
Forte application terminates the 16 bit OLE server remains loaded and is
visible to the task manager.
It is surprising that the OLE automation server is visible after the
calling application has terminated and I have some questions:
1. Has anyone encountered this behaviour?
2. Does it cause problems?
3. Is there a known solution?
4. What is causing this behavior.?
The Forte application executes on a NT 4.0 client using Forte release H2.
The OLE automation server was written in VB. 4.0 and is a 16 bit solution.
Thanks for your help,
Eamonn.

not sure if anyone is watching this thread anymore but i have this scenario. i am using the excel connection manager in SSIS to create an excel spreadsheet with VS 2012. To do this from what I have read I am required to use the 32-bit driver for "Microsoft
Access database engine 2007", if I use the 64-bit driver I cannot connect to the Excel connection manager. i get 0xc020801c message.
i can install the 32-bit "Microsoft Access database engine 2007" and resolve this problem. but i also have a stored procedure that creates a spreadsheet (i use this because i have to leave some cells intact), it appears to require the
64-bit "Microsoft Access database engine 2007". in 32-bit mode i get the following message
Msg 7438, Level 16, State 1, Procedure sp_CreateGRfile, Line 26
The 32-bit OLE DB provider "Microsoft.ACE.OLEDB.12.0" cannot be loaded in-process on a 64-bit SQL Server.
so i need both the 32-bit "Microsoft Access database engine 2007" and 64-bit "Microsoft Access database engine 2007".
any thoughts on getting around this issue?

Using CORBA as Middleware with Forte'

I would like to find a way to use CORBA middleware as an alternative for
communications between Forte' partitions (I'm using Forte' rel. 3.0.G plus
Visibroker 3.1 ORB).
I found a technical note (ID 10520) but it is quite old and it is related
to Forte' release 2.0.E.2 (!).
Any experience with Forte' release 3 and Visibroker would be greatly
appreciated.
TIA
Giuseppe Sorce
CSI Piemonte - C.so Unione Sovietica 216 - 10134 Torino - ITALY
tel. +39-011-3168736
fax +39-011-3168212
e-mail [email protected]
url http://www.csi.it
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

I would like to find a way to use CORBA middleware as an alternative for
communications between Forte' partitions (I'm using Forte' rel. 3.0.G plus
Visibroker 3.1 ORB).
I found a technical note (ID 10520) but it is quite old and it is related
to Forte' release 2.0.E.2 (!).
Any experience with Forte' release 3 and Visibroker would be greatly
appreciated.
TIA
Giuseppe Sorce
CSI Piemonte - C.so Unione Sovietica 216 - 10134 Torino - ITALY
tel. +39-011-3168736
fax +39-011-3168212
e-mail [email protected]
url http://www.csi.it
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Forte Release 2F

Similar Messages

Maybe you are looking for