RE: (forte-users) Object Request Brokers.....

Hi Rajeev,
I just happen to have the following two technotes on hand that helped me
answers the very same questions..
<<forte.zip>>
Hope it helps... if you need more help... fell free to give me a shout!
Ciao
Kim
-----Original Message-----
From: Rajeev Talwar [SMTP:rtalshotmail.com]
Sent: Monday, February 21, 2000 6:34 PM
To: kamranaminyahoo.com
Subject: (forte-users) Object Request Brokers.....
Hi All,
We are writing a cold fusion application which needs to use some
services from a Forte application. We also have a Cold Fusion Visi
Broker(ORB)to communicate with Forte. I was wondering what all we need
in order to get a handle to all the service objects used by Forte
application in our Cold Fusion application.
Also do we need to change our deployment scheme for the Forte
application. I
believe we have to make a special deployment
for Forte application to be available to ORB's. By default,
Forte uses Unix internal communication mechanism like sockets
etc. for service objects to be available across different
partitions.
Also do we need to run both applications and ORB on the same box
or can we put them in some kind of network.
I hope I made myself quite clear what we are looking for. I will be
more than happy to put some more details in case someone needs
further clarification.
Are there any technotes out there whcih we can refer to.
I will appreciate any thoughts.
-Rajeev Talwar
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a
new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com

You can also use the HTTP-DC project.... You don't
need Web Enterprise for this. From what I can tell,
this is available in L.x on....
There is api documentation in M.2 (with scant
examples.)
There's a special process to put the project in your
repository (it isn't installed in the repository in
the standard install,) the documentation in M.2
(probably in M.0 too, AFAIK) that tells you how to do
this (look for HTTP-DC in the online help.)
I haven't done much with it yet, I've just installed
it. If anybody out there has examples, that'd be
great. I'll try to contribute more the moment I get a
chance to explore it....
Christopher Fury
BellSouth Communications Systems
--- Daniel Nguyen <dnguyenclub-internet.fr> wrote:
Hi,
If you have Web Enterprise, you can user
HttpAccess.SendRequest().
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Amin, Kamran a écrit:
Is there any way to make a HTTP request from TOOLto another HTTP Service?
thanks in advance.
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. Tounsubscribe, send in a new
email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

Similar Messages

Re: (forte-users) HTTP request through proxy server

Daniel -
No, it does not. ;)
How do you say to HTTPRequest to go through proxy?
Thanks,
Taras
Daniel Nguyen wrote:
>
Hi,
It works very well. I have experienced this model for a distant Forte client
calling a Forte Server service Object for instance without any environment
and without TCP access (passing through firewall for instance).
It has also worked very well to make an injectot to improve Web Enterprise
and IIS using the SendRequest from HTTPAccess.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
http://perso.club-internet.fr/dnguyen/
Taras Katkov a écrit:
HTTP request through proxy server using forte HTTP library?
Any experience?
Thanks,
Taras
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

You can also use the HTTP-DC project.... You don't
need Web Enterprise for this. From what I can tell,
this is available in L.x on....
There is api documentation in M.2 (with scant
examples.)
There's a special process to put the project in your
repository (it isn't installed in the repository in
the standard install,) the documentation in M.2
(probably in M.0 too, AFAIK) that tells you how to do
this (look for HTTP-DC in the online help.)
I haven't done much with it yet, I've just installed
it. If anybody out there has examples, that'd be
great. I'll try to contribute more the moment I get a
chance to explore it....
Christopher Fury
BellSouth Communications Systems
--- Daniel Nguyen <dnguyenclub-internet.fr> wrote:
Hi,
If you have Web Enterprise, you can user
HttpAccess.SendRequest().
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
Amin, Kamran a écrit:
Is there any way to make a HTTP request from TOOLto another HTTP Service?
thanks in advance.
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. Tounsubscribe, send in a new
email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To
unsubscribe, send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

Object Request Brokers.....

Hi All,
We are writing a cold fusion application which needs to use some
services from a Forte application. We also have a Cold Fusion Visi
Broker(ORB)to communicate with Forte. I was wondering what all we need
in order to get a handle to all the service objects used by Forte
application in our Cold Fusion application.
Also do we need to change our deployment scheme for the Forte application. I
believe we have to make a special deployment
for Forte application to be available to ORB's. By default,
Forte uses Unix internal communication mechanism like sockets
etc. for service objects to be available across different
partitions.
Also do we need to run both applications and ORB on the same box
or can we put them in some kind of network.
I hope I made myself quite clear what we are looking for. I will be
more than happy to put some more details in case someone needs
further clarification.
Are there any technotes out there whcih we can refer to.
I will appreciate any thoughts.
-Rajeev Talwar

Check if the OSS Note 872649 helps you on this issue??

Subject: RE :(forte-users) Web enterprise & user visibleservice Objects

A few months ago we faced a similar problem while migrating from classic
Forte to Web. We had to protect our investment in various frameworks that we
wrote for the classic Forte apps, which made use of extensive
user-level-caching among other things.
We solved the problem using a custom routing mechanism. In brief, we created
several( replicated) server partitions that contains all the user-level
Service objects that existed in the class-Forte apps. Then we wrote a
'custom-router' which mimics Forte load-balanced router( dialog duration =
session ) to intelligently route incoming HTTPRequests to one of these
replicated partitions. The router would look at the some tag on the session
and then route the request to one of these replicated "client clone" using
the tag. Successive requests from the same client will go to the same
replicated partition so that you can use the client-cache or any other
per-user services.
The advantages of this approach are
1) You can continue to make use of caching and other user-level components
that you may have.
2) The web and classic Forte clients can work seamlessly if you write them
to use reference partitions that hosts the other shared( Environment visible
) service objects.
Ofcourse you will have to write ( and maintain )the custom-routing code and
also pay attention to house-keeping. For example, the burdon of cleaning up
the cache on logout or session expiration lies on you. If you don't do this,
then your new user might be looking at an old cache of some other user.
Hope this helps,
Ajith
Forte Systems Consultant.
Subject: (forte-users) Web enterprise & user visible service objects
Hi
We have taken a forte application and converted it to run on the web using
* forte web enterprise &
* fortecgi.exe
In the forte application we have a user visible Local Cache Manager
Service Object (i.e. each users has their own copy) for storing things
like
* the details of the current user id
* the details of the current client chosen
* arrays that are needed by other windows
With web enterprise this service object is no longer user visible, how can
we make it user visible?
Thanks in advance.
Deborah Wallis
dwallisnbs.co.za
WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, the BoE Group does
not accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.nbs.co.za/emaildisclaim.htm
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

A few months ago we faced a similar problem while migrating from classic
Forte to Web. We had to protect our investment in various frameworks that we
wrote for the classic Forte apps, which made use of extensive
user-level-caching among other things.
We solved the problem using a custom routing mechanism. In brief, we created
several( replicated) server partitions that contains all the user-level
Service objects that existed in the class-Forte apps. Then we wrote a
'custom-router' which mimics Forte load-balanced router( dialog duration =
session ) to intelligently route incoming HTTPRequests to one of these
replicated partitions. The router would look at the some tag on the session
and then route the request to one of these replicated "client clone" using
the tag. Successive requests from the same client will go to the same
replicated partition so that you can use the client-cache or any other
per-user services.
The advantages of this approach are
1) You can continue to make use of caching and other user-level components
that you may have.
2) The web and classic Forte clients can work seamlessly if you write them
to use reference partitions that hosts the other shared( Environment visible
) service objects.
Ofcourse you will have to write ( and maintain )the custom-routing code and
also pay attention to house-keeping. For example, the burdon of cleaning up
the cache on logout or session expiration lies on you. If you don't do this,
then your new user might be looking at an old cache of some other user.
Hope this helps,
Ajith
Forte Systems Consultant.
Subject: (forte-users) Web enterprise & user visible service objects
Hi
We have taken a forte application and converted it to run on the web using
* forte web enterprise &
* fortecgi.exe
In the forte application we have a user visible Local Cache Manager
Service Object (i.e. each users has their own copy) for storing things
like
* the details of the current user id
* the details of the current client chosen
* arrays that are needed by other windows
With web enterprise this service object is no longer user visible, how can
we make it user visible?
Thanks in advance.
Deborah Wallis
dwallisnbs.co.za
WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, the BoE Group does
not accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.nbs.co.za/emaildisclaim.htm
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Error in SMQ2 - Object requested is currently locked by user ...

HI together,
we send IDOCs from SAP R/3 through XI into an other SAP R/3 system (ORDERS). all messages will be processed but only 2 messages are get stuck in XI with the error message:
"Object requested is currently locked by user" in SMQ2.
Do anybody know a solution for that?
If i trigger the IDOC in WE19 again, the same error occurs again and again.
Many thanks
Alex

HI together,
very strange happening!!
i check the mapping of the error message and found out that we have a used a multiply function in the mapping (quantity * price). we have a price > 100000.00 and a quantity of 3. In testtab the mapping runs and runs and runs... nothing happens.
i created u UDF that solve the problem. i do not know why this is needed or what is wrong the the SAP standard mapping function.
Unfortunately we have this issue only in production, not in DEV or QA.
cheers,
alex

RE: (forte-users) User-visible service object

This solution will cause network traffic for all method calls on the
environment visible SO. This overhead is not incurred when calling methods
on a user visible SO in the same partition. Depending on the frequency of
calls and the volume of data being passed in and out, this could be
significant overhead.
We have successfully implemented the following.
Create a second User Visible SO based on the same class. Then you will be
able to partition the one SO into the client partition and the second into
the server partition.
For example, assume the underlying class is named MessageService then define
your SO's as
ClientMessageService -> MessageService
ServerMessageService -> MessageService
Andy
-----Original Message-----
From: Amin, Kamran [mailto:kamran.aminlendware.com]
Sent: Wednesday, August 23, 2000 10:17 PM
To: 'Duncan Kinnear'; kamranaminyahoo.com
Subject: RE: (forte-users) User-visible service
object
Duncan,
Make the user visible service object to an
environment visible
service object. This way the client and any service object
on the server
can access it.
ka
-----Original Message-----
From: Duncan Kinnear [mailto:duncanmccarthy.co.nz]
Sent: Wednesday, August 23, 2000 7:47 PM
To: kamranaminyahoo.com
Subject: (forte-users) User-visible service object
Hi folks!
We've got a user-visible service object that handles
initialisation of and
access to the message catalog.
This works well on the client, but we would like to use the
same
mechanism (and even the same service object) on the server
so that
service objects on the server have access to their message
catalog on
the
server.
I was hoping that if we referenced this user-visible service
object in
both the client and the server code, that it would partition
a copy in
each of the client and server partitions. However, we
cannot get this
user-visible service object duplicated on the server. If we
drag and drop
it onto the server partition in the partition workshop, it
disappears from
the client partition!
Anybody got any idea how we could do this?
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
duncanMcCarthy.co.nz
PO Box 764, McLean Towers, Phone: +64
6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64
6 834 3369
Providing Integrated Software to the Meat Processing
Industry for over 10
years
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe,
send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com
For the archives, go to:
http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe,
send in a new
email the word: 'Unsubscribe' to:
forte-users-requestlists.xpedior.com

I would try going to the "lowest common denominator" between WindowsNT and
Windows95 - DOS. Both windowing OS's sort of have their roots in DOS, or at
least both are capable of opening a DOS session.
Therefore, from a DOS prompt type "set" to view the environment variables for
both OS types. Look for a common variable between the two that stores the
userID. If you can find one of these your application will be that much more
portable between these two Windows mutations.
I used "set" on my NT and found my userID assigned to a few variables. I haven't
done this on a Windows95 machine in quite some time, but if the machine is on
the network it should have at least one environment variable with the userID.
I'm just guessing that DOS has a variable to store the userID that will be
common to both machines.
Good luck....
Kelsey PetrychynSaskTel Technical Analyst
ITM - Technology Solutions - Distributed Computing
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:kelsey.petrychynSasktel.sk.ca
Quality is not job 1. It is the only job!
"Olivier Andrieux" <oandrieuxaxialog.fr> on 07/19/2000 09:12:41 AM
To: forte-userslists.xpedior.com
cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
Subject: (forte-users) user name
Hi
I use this command to catch the username:
task.part.operatingsystem.getenv('username')
with NT, there is no problem
but with windows95 or 98 the command doesn't find the username.
Thanks in advance.
Olivier Andrieux
Axialog
Lille
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Re: (forte-users) loadbalancing a service object

Hi,
If you need to share the values between your So, you can find a sample on
http://perso.club-internet.fr/dnguyen
It was designed to show how to manage shared states between replicates using
fail over. It could also be used for load-bancing. A better way should be to
manage the names of service objects within Forte (with the application,
project name and compatibility level), but through the NameServer.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
http://perso.club-internet.fr/dnguyen/
Xiao, Menghua a écrit:
Hello,
I tried to loadbalance a service object that has both methods and
attributes. The first copy of the service object works fine. However, all
the attributes of the second copy of the service object are nil when a
client try to use this copy. How can I make those two copies exactly the
same?
I am new to Forte. Any input will be greatly appreciated.
Menghua Xiao
Regional Transportation District,
Denver, Colorado, USA
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Hi,
If you need to share the values between your So, you can find a sample on
http://perso.club-internet.fr/dnguyen
It was designed to show how to manage shared states between replicates using
fail over. It could also be used for load-bancing. A better way should be to
manage the names of service objects within Forte (with the application,
project name and compatibility level), but through the NameServer.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
http://perso.club-internet.fr/dnguyen/
Xiao, Menghua a écrit:
Hello,
I tried to loadbalance a service object that has both methods and
attributes. The first copy of the service object works fine. However, all
the attributes of the second copy of the service object are nil when a
client try to use this copy. How can I make those two copies exactly the
same?
I am new to Forte. Any input will be greatly appreciated.
Menghua Xiao
Regional Transportation District,
Denver, Colorado, USA
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

RE: (forte-users) Does anyone have experience using OracleLarge Objects

hi ,
A few months ago, I tried a oracle stored procedure with a BLOB parameter,
but Forte(3.l2) could not recognize the blob variable. I used oracle 8.0
hth
suma
-----Original Message-----
From: Amin, Kamran [mailto:kamran.aminlendware.com]
Sent: Thursday, March 29, 2001 2:40 PM
To: 'Forte User Group'
Cc: Magaliff, Bill
Subject: (forte-users) Does anyone have experience using Oracle Large
Objects (LOB's)?
Does anyone have experience using Oracle Large Objects (LOB's) -
specifically the CLOB datatype? Forte supports Oracle LONG's but given that
Oracle is going to phase out that datatype and they're trying to push users
towards CLOB's instead of LONG's, I want to find out if Forte can handle it
and, if so, what we should know about mapping Forte datatypes to the Oracle
CLOB. [Their compatibility matrix for v3.5 indicates suppport under Oracle
8.1.x, and CLOB's were introduced back in 8.0.x - but the word from Forte is
that they currently don't support it.]
thanks in advance.
ka
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Hi,
Did you get any solution to this. If yes, please share.
Thanks,
Tints

Re: (forte-users) Service Object

what about subclassing it and putting the agent stuff in there
Matthew Middleton Ph: +61 2 9239 4972
Oryx Software Consultant Fax: +61 2 9239 4900
Lawpoint Pty. Ltd. E-mail matthewmwriteme.com
----- Original Message -----
From: Ramarao Pabbaraju <RPabbarajulmimsno.com>
To: <kamranaminyahoo.com>
Sent: Tuesday, February 29, 2000 9:02 AM
Subject: (forte-users) Service Object
Hi,
We have a class X which we would like to use it for service object andalso
to instantiate it locally to call some methods. We would like to have
system agents for the service object, but not for objects instantiated
locally. In other words, if the object is used for service object, only
then we want the agents (customized) to be initialized. How do we find out
whether it is service object in Init method self? Service objectproperties
(like isAnchored) or attributes (given from ServiceObject
properties/initial values window) are set only at the end of init method.
One workaround we could think of is start a task at the end of init method
and also delay the execution of method. Is there any clean way of doing
this?
Thanks in advance,
Ramarao
IonIdea
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Request: compare and propagate user objects

After making changes to table definitions, views, program units, and so on, it may be useful to propagate these changes to another database user. This maybe another development environment, or a testing environment in same or another database. Like "Compare user objects" option in PLSQL/Developer.
/* BEGIN: cut and paste from PLSQL Developer Help */
Compare User Objects
After making changes to table definitions, views, program units, and so on, it may be useful to propagate these changes to another database user. This maybe another development environment, or a testing environment. To compare the objects of your development user with another user, you can use the Compare User Objects function in the Tools menu. This will bring up the following dialog:
On the Selection tab page you can select the objects you wish to compare. After making this selection, you can press the Target Session button, to select the user and database that you want to compare. This will enable the Compare button, which you can press to start the compare operation. You can select the Include storage... option to include the storage information such as tablespace names and initial sizes for new objects. These may differ across databases, so this may not always be appropriate.
When the compare operation is finished, the dialog will switch to the Differences tab page, which will show a list of all objects that are different:
This list is sorted in order of dependency. Below the list of different objects of the target user, you see the SQL that needs to be executed to make these objects equal to the corresponding objects of the current user. If no object is selected, the SQL of all objects is displayed. If one or more objects are selected, only the SQL for the selected object(s) is displayed. In the example above, a missing EMP_MGR_EMPNO check constraint was added to the EMP table.
The Show Differences button will show a visual line-by-line difference of the old and new source file of an object. This can be useful to view the changes made in Program Units, or can help you determine why a specific DDL statement was generated for other object types. The Configure External Difference Tool allows you to configure the difference tool should be used. By default the ExamDiff utility will be used, for which a Pro version is available (See the About item of ExamDiffs Info menu). See also Tools - Differences.
You can now press the Apply SQL button to execute this SQL in the target session. You can alternatively save the SQL in a file by pressing the Save SQL button, or you can copy it to the clipboard by pressing the Copy SQL button.
When objects are compared, the following properties are ignored:
·     Storage Properties such as the next extent and pct free of tables and indexes are not considered relevant for comparison.
·     Constraints with system generated names These constraints will have different names for the 2 users, so they cannot be compared. If a table is new in the target session, these constraints will be generated though.
·     Table creation properties Properties that would require the recreation of the table are ignored.
·     Table data To export table data, use the Export Table function (see Export Tables).
·     Sequence values The current value of a sequence is considered data.
/* END: cut and paste from PLSQL Developer Help */

This is on the list but not for 1.0.
-kris

RE: (forte-users) Reporting tools/components for ForteApplications?

Hi Robert,
A good place to start when it comes to reporting is Forte Consulting. They
have developed a tool called ReportKit, which is ActiveX integration with
Seagate Software's Crystal Reports tool. Crystal is not really a three-tier
tool (although, your Forte Consultant can probably set it up to mimic a
three-tier tool), but it is a quick, easy way to get quality reports from
your existing Forte applications. If you're interested, give your Forte
Sales Rep (or, better still, your Forte Regional Consulting Director) a
call. They can discuss pricing and scheduling. I've done several
integration projects with Crystal, and I highly recommend ReportKit for
small- to medium-sized reporting requirements. As for costs, I don't recall
how much CrystalReports runs, but I think there are developer licenses and
runtime licenses.
FYI, the actual integration of ReportKit is pretty quick. The more
time-consuming piece of any report tool integration is the design and
implementation of the reports to be used.
I hope this helps.
-Katie
Katie Tierney
Quality Management Analyst
Akili Systems Group
601 Jefferson, Suite 3975
Houston, Texas 77002
Office: (713) 655-1400
Cell: (409) 255-1643
"The bitterness of poor quality remains long after the sweetness of low
price is forgotten" --Larry Anderson
-----Original Message-----
From: Robert Brooke-N502365 [mailto:Robert.Brookeca.michelin.com]
Sent: Monday, February 14, 2000 8:17 AM
To: kamranaminyahoo.com
Subject: (forte-users) Reporting tools/components for Forte
Applications?
Hi all,
We are looking for what is currently in the marketplace to enhance the
reporting
capabilities of Forte. Ideally, we are looking for component libraries that
we
could import into our repository. Do these exist?
Currently, I have found six reporting tools that are out there. The
tools
are Actuate, Crystal Reports, Report Workshop from Indus Consultancy
Services, Brio Technologies (SQR) VisualBRIO, Visual CyberQuery from
Cyberscience Corp., and Beacon from Brahma Software Solutions FORTify
Components. Are there any others for Forte?
If anyone is currently using one of these Reporting Tools for Forte or
any
others, could you give me any indications as to the costs, training, type
of
application using the Reporting tool, would you recommend using the
product
again, does it use wrappering or API, or is it a component based tool, and
any
other relevant information on the product?
Thanks,
Robert Brooke
Application Developer
Michelin North America (Canada) Inc. CA0/CA1
PO Box 399
New Glasgow, Nova Scotia
B2H-3E6
Phone: (902) 753-1977
Fax: (902) 396-2180
Note: We are currently developing in Forte 3.0.L.2. However, we would
like
to select a reporting tool/component within the next month. We are in the
initial phases of our next project, an application to be developed
in-house.
Probably will have two databases, one for real-time data and another one
for
archived data. Probably will need reporting functionality and capabilities
for
both real-time data and archived data.
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
MIMEsweeper for the presence of computer viruses.
The E-Mail System is to be used for business purposes only.
www.mimesweeper.com
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

At 09:33 AM 4/20/01, Rottier, Pascal wrote:
Forte 4GL is:
1) A language, TOOL (Compare to Java)
2) An IDE (Compare to e.g. JBuilder or FJCE)
3) A collaborative development environment, with central repository (Compare
to ????)
4) A distributed application server / object request broker (Compare to J2EE
servers and/or CORBA)Let's not forget WebEnterprise, Express, and especially Fusion.
I think, SUN is not al all interested in TOOL.If TOOL were just a language and had no market yet, you are probably
right. But, not only is TOOL the key to the Forte environment, but it has
an existing and profitable market. Sun still sells FORTRAN, after all, and
continues to put money into ADE development for all its language
products. The real kicker, though, is that I think iPlanet is very clear
that Fusion, now iIS, is a very key product for them. There may be those
who wish it were written in Java and who might lobby for doing a Java
version, but it was clear at the conference that the iPlanet management
recognize that Java just isn't up to the task at this point. It isn't as
if all the iPlanet tools are actually written in Java, after all.
They will only support them for as long as they need.Or, more likely, for as long as they make money.
Now, in response to Microsofts .NET stratagy. We have yet to see how
succesfull this will be, but I expect Microsoft to push this down the
throats of developers and companies quite succesfully.Like they did DCOM?
=========================================================================
Thomas Mercer-Hursh, Ph.D email: [email protected]
Computing Integrity, Inc. sales: 510-233-9329
550 Casey Drive - Cypress Point support: 510-233-9327
Point Richmond, CA 94801-3751 fax: 510-233-6950

Re: (forte-users) Delays in data transfer..server-to-client

I would try using DOM (distributed object manager) traces. trc:do:20 will
give you information on each messages sent from and received by the
partition. Levels are 1, 2, 5, 7, and 8, and trc:do:*:8 is very
verbose. trc:do:20:1 may tell you what you want to know. trc:do:1:1 will
give you a basic 1-line-per DOM event trace that may also be all you need.
Communications manager traces will tell you about network and socket-level
activity, but not about the sizes of the messages themselves. In addition,
the operating system makes decisions about physical packet size and
send/receive timing, so CM activities only generally map to actual network
activity.
-tdc
iPlanet Integration Server Engineering
At 09:24 AM 5/1/01 -0700, you wrote:
All,
We are experiencing delays in object transfer between server and client. The
delays are longer with large objects (a single object with an array of objects
that reflect the rows returned in a database) than small (ie: 10 rows vs 400).
Does anyone have any (actual) experience using the various Forte' flags in
order
to show the actual size of the object/packets being passed between the server
and client?
We are using input/output between client and server, input on all the SO's
within a partition. Response on the server side is good, roughly 6 seconds or
so. The round trip fare however from the time the client makes the SO call to
the time that it completes is in the 25-30 second range, leaving roughly 20-25
seconds unaccounted for. I have brought in the network guys who are
requesting
the data size and packet information. I did not see what I am looking for
using
the trc:cm:*:4 and trc:cm:*:8 flags. I will be trying the trc:cm:*:10
flag, but
Forte' indicates that this flag is very verbose, the systems group hates
it when
I use up all of THEIR disk space!
Any ideas would be appreciated as always.

Jeff,
If the object you are passing does not require changes made to it in the
server partition to be returned, pass the object as copy input (pass by
value not reference). If it is necessary to pass the object as input, try
to pass only the attributes that are required to the remote partition
instead of the whole object.
Input/Output is normaly used with scalar variables. When a scalar is passed
to a remote partition, if the value is changed in that partition, the value
is not returned to the calling partition unless Input/Output is used.
Input/Output should not be used for object type parameters, if you need to
pass a reference, use Input only. If you can pass by value, use Copy Input.
You will notice a huge difference in performance changing from Input to Copy
input when passing large objects.
Hope this helps,
Travis Foote
Fortedeveloper.com Inc.
----- Original Message -----
From: "Jeff Bennett" <[email protected]>
To: <[email protected]>
Sent: Tuesday, May 01, 2001 9:24 AM
Subject: (forte-users) Delays in data transfer.. server-to-client
>
All,
We are experiencing delays in object transfer between server and client.The
delays are longer with large objects (a single object with an array ofobjects
that reflect the rows returned in a database) than small (ie: 10 rows vs400).
>
Does anyone have any (actual) experience using the various Forte' flags inorder
to show the actual size of the object/packets being passed between theserver
and client?
We are using input/output between client and server, input on all the SO's
within a partition. Response on the server side is good, roughly 6seconds or
so. The round trip fare however from the time the client makes the SOcall to
the time that it completes is in the 25-30 second range, leaving roughly20-25
seconds unaccounted for. I have brought in the network guys who arerequesting
the data size and packet information. I did not see what I am looking forusing
the trc:cm:*:4 and trc:cm:*:8 flags. I will be trying the trc:cm:*:10flag, but
Forte' indicates that this flag is very verbose, the systems group hatesit when
I use up all of THEIR disk space!
Any ideas would be appreciated as always.
-jeff
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Re: forte-users-digest V1 #89

forte-users-digest Tuesday, 8 October 1996 Volume 01 : Number 089
From: Alexander Ananiev <[email protected]>
Date: Tue, 08 Oct 1996 16:36:14 -0500
Subject: "Single DBSession" approach
The standard Forte approach for the database access assumes
that one DBSession handles requests from several users
(clients), so the database connection is not associated with
the particular user. This significantly impacts the
architecture of the Forte application. Some of the problems
caused by this approach are:
1) An application-level security system should be developed
instead of using the DBMS security system. Suffice it to say
that application-level security system cannot provide the
protection from back-door access to the database.
2) The application cannot utilize the DBMS locking mechanism
for the case when the record is retrieved to the client for
editing purposes ("long" transaction).
It means that SecurityManager and LockManager should be
developed to resolve these problems. This does not seem to be
very good solution because these objects are intended to repeat
the functionality of the DBMS. And these parts of the
application may become pretty complicated. For example, my
project's experience shows that the development of the lock
manager is not a trivial task and most likely this lock manager
will be worse than the DBMS locking mechanism in terms of
reliability and performance just because it acts as an outside
program to the database. Besides, this approach could cause
serious problems if the database can be updated by non-Forte
applications (e.g., by some legacy system or batch process).
"One DBSession per several users" approach makes sense if each
user connection to the database is implemented as one
server process.(Another good argument in favor of single
DBsession is a heterogeneous environment where there is no
stable connection to one database, but here I'm talking about a
"regular" application that uses only one DBMS.) Since most of
the time this process is idle, then, of course, decreasing the
number of processes leads to better server utilization and
performance. But by its sense, database connection is just the
current transaction ID (with the user id, of course). So the
connection could be just a number that should be passed to the
DBMS along with each request and then DBMS can create a thread
to handle the request or forward it to the next available
process if it does not support multithreading.
DBMS vendors realize this and some of them already implemented
this approach (I know that Oracle and Informix did that and
Sybase was mentioned in the recent "one-threaded DBSession"
discussion). And one-threaded DBSession that lives on the
server doesn't fit well to that. The better approach would be
to make DBSession the attribute of the TransactionHandle
object, so the current connection will always be passed from
the client to the service and this service can work through
this connection.
So, my point is that the application should let DBMS do its
work and use as much of the functionality of the DBMS as
possible and the "single DBsession" approach doesn't help it to
do that.
I would be glad to hear any other opinion on this topic. I
think that the "DBsession" problem is extremely important for
any multi-tier application (for example, all Web applications
are facing this problem). I'm also interested in how people
are dealing with this problem on other projects, for example if
there are some projects where the alternative approach (one
DBSession per each user) was implemented and what problems were
encountered during that.
Alexander Ananyev
Price Waterhouse
End of forte-users-digest V1 #89
One of the first issues that needs to be addressed is that passing
DBSessions from partition to partition is a huge performance hit. When
Forte executes a SQL SELECT or FETCH statement on a DBSession that exists
outside the current partition (DBSessions are "anchored" objects that are
accessed via proxies.) Forte fetches the result set into the partition
containing the DBSession and then passes proxies or creates copies into
the partition where the SQL code is located. These are some of the
largest performance hits you can take in Forte.

forte-users-digest Tuesday, 8 October 1996 Volume 01 : Number 089
From: Alexander Ananiev <[email protected]>
Date: Tue, 08 Oct 1996 16:36:14 -0500
Subject: "Single DBSession" approach
The standard Forte approach for the database access assumes
that one DBSession handles requests from several users
(clients), so the database connection is not associated with
the particular user. This significantly impacts the
architecture of the Forte application. Some of the problems
caused by this approach are:
1) An application-level security system should be developed
instead of using the DBMS security system. Suffice it to say
that application-level security system cannot provide the
protection from back-door access to the database.
2) The application cannot utilize the DBMS locking mechanism
for the case when the record is retrieved to the client for
editing purposes ("long" transaction).
It means that SecurityManager and LockManager should be
developed to resolve these problems. This does not seem to be
very good solution because these objects are intended to repeat
the functionality of the DBMS. And these parts of the
application may become pretty complicated. For example, my
project's experience shows that the development of the lock
manager is not a trivial task and most likely this lock manager
will be worse than the DBMS locking mechanism in terms of
reliability and performance just because it acts as an outside
program to the database. Besides, this approach could cause
serious problems if the database can be updated by non-Forte
applications (e.g., by some legacy system or batch process).
"One DBSession per several users" approach makes sense if each
user connection to the database is implemented as one
server process.(Another good argument in favor of single
DBsession is a heterogeneous environment where there is no
stable connection to one database, but here I'm talking about a
"regular" application that uses only one DBMS.) Since most of
the time this process is idle, then, of course, decreasing the
number of processes leads to better server utilization and
performance. But by its sense, database connection is just the
current transaction ID (with the user id, of course). So the
connection could be just a number that should be passed to the
DBMS along with each request and then DBMS can create a thread
to handle the request or forward it to the next available
process if it does not support multithreading.
DBMS vendors realize this and some of them already implemented
this approach (I know that Oracle and Informix did that and
Sybase was mentioned in the recent "one-threaded DBSession"
discussion). And one-threaded DBSession that lives on the
server doesn't fit well to that. The better approach would be
to make DBSession the attribute of the TransactionHandle
object, so the current connection will always be passed from
the client to the service and this service can work through
this connection.
So, my point is that the application should let DBMS do its
work and use as much of the functionality of the DBMS as
possible and the "single DBsession" approach doesn't help it to
do that.
I would be glad to hear any other opinion on this topic. I
think that the "DBsession" problem is extremely important for
any multi-tier application (for example, all Web applications
are facing this problem). I'm also interested in how people
are dealing with this problem on other projects, for example if
there are some projects where the alternative approach (one
DBSession per each user) was implemented and what problems were
encountered during that.
Alexander Ananyev
Price Waterhouse
End of forte-users-digest V1 #89
One of the first issues that needs to be addressed is that passing
DBSessions from partition to partition is a huge performance hit. When
Forte executes a SQL SELECT or FETCH statement on a DBSession that exists
outside the current partition (DBSessions are "anchored" objects that are
accessed via proxies.) Forte fetches the result set into the partition
containing the DBSession and then passes proxies or creates copies into
the partition where the SQL code is located. These are some of the
largest performance hits you can take in Forte.

Re: (forte-users) access violation caught in debugmode

Eric,
There has been a problem with Forte debug mode for sometime now when the app
is silent. If you attempt to inspect the variables when the app is in the
'silent' mode, i.e., waiting on an event loop for a user input or a system
event, then you get the "Access violation caught ..." exception message and
the workspace including the launch server crashes.
If you are getting this problem in the 'step-through' mode, you should look
at the lauch server immediately after you get the exception before
everything disappears. There could be a stack backtrace due to some illegal
reference. We have faced a similar situation before but the error appeared
both in the 'debug' and 'run' modes.
Hope this helps.
Braja K Chattaraj.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Eric,
Another possibility has to do with the repository. You said you recently
migrated 30G2 to release 30L2.
Many strange problems have been traced to release migrations with old
repositories. If the repository was properly migrated another thing you can try
is to export the project(s) to PEX files, delete them from the repository, and
then re-import. I know this can be time consuming but I have solved more than
one unexplained problem in the IDE by doing it.
---------------------- Forwarded by Charlie Shell/Bsg/MetLife/US on 09/23/99
01:19 PM ---------------------------
"Ajith Kallambella" <[email protected]> on 09/23/99 12:08:54 PM
To: [email protected], [email protected]
cc: (bcc: Charlie Shell/Bsg/MetLife/US)
Subject: Re: (forte-users) access violation caught in debug mode
Eric,
Sometimes( 90% ) you can solve this problem by
checking out the class that is causing the crash
and force-compiling it.
If it doesn't help, run through this checklist.
1. Do you have enough memory resources.?
2. Is the object you are inspecting held in a lock ?
( mutex, transaction lock etc )
3. Does it work when you wait for sometime at the
breakpoint before inspecting the values? I mean
are you interrupting some process thread?
4. Does it work if you log the attributes using logmgr?
5. Are you using any call-outs/call-ins? Any external
systems integration? Sometimes( for reasons beyond
my comprehension ) the objects allocated outside
Forte gets corrupted when its passed back and forth.
6. ...finally...Santa Clause, help me!
Ajith Kallambella M.
Forte Systems Consultant.
From: Eric Decossaux <[email protected]>
To: forte mailing <[email protected]>
Subject: (forte-users) access violation caught in debug mode
Date: Thu, 23 Sep 1999 17:31:39 +0200
Hello,
I have a problem using Forte in debug mode. If I run my program on my NT
machine from the partition workshop (distributed run), the program works
fine except that some object does not display what I'm expecting. So I
want to use the debug mode to inspect the objets of this window. When I
choose the "local variables" option to see the content of my window, I
have a "access violation caught" and forte disappears. If I just let my
program run without choosing this option, everything is the same than
with the distributed run.
Does somebody have an idea what to look for ? I really want to look the
inside the attributes of this window.
We recently upgraded from release 30G2 to release 30L2. Could it be the
problem ?
Eric Decossaux
Cliniques Universitaires St Luc
Informatique des Laboratoires
av Hippocrate 10 / 1730
1200 Bruxelles
+32+2+764 17 53
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

RE: (forte-users) Changing replication options in Fscript? -Tric k

There was one attribute of a service object you couldn't change in fscript..
I think it was whether the service was replicated at all or not (not the
same as setting rep count to 1!).
As Clint would say, "improvise.."
We exported the project containing the service object and snipped out the
part pertaining to the service object in to a little export file.
Then in an fscript script you can branch/checkout the service object and
import the snipped out export file to change the replicated yes/no flag.
Then do whatever other fscript commands make sense.. We tended to leave the
system baseline with the "true" replication flags and let developers run
this little script (only branching the services) to de-replicate all the
replicated services prior to trying to run from their workspace, etc.
Worked like a charm.
-Greg
-----Original Message-----
From: Taras Katkov
To: [email protected]
Sent: 12/1/99 2:57 PM
Subject: Re: (forte-users) Changing replication options in Fscript?
"setappcompcompiled", "setPARTrepcount" can be used in fscript during
application build.
I mean PERIOD!
Taras Katkov
f.e.
FindAppComp AppNAme_PartXX
SetAppCompCompiled MyNode 1
SetPartRepCount MyNode YY
SetPartArgs MyNode \"Whatever\"
SetPartThreadPkg MyNode DCE
commit
[email protected] wrote:
>
Yes through escript one can achieve changing the properties but onecannot
do it when one is partitioning the app where the router gets createdand
assigned ( which is fscript) and the single threadedness of thepartition
takes effect ( for loadbalancing ) except from the partitioningworkshop
(GUI) itself.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 3:39 PM
To: [email protected]; [email protected];
[email protected]
Subject: RE: (forte-users) Changing replication options in Fscript?
Yes you can do it, but you actually do it in EScript not FScript lookfor
the following types of command "assignappcomp", "unassignappcomp",
"setappcompcompiled", "setrepcount", "findagent", "findsubagent",
"findparent" etc.. So start with your EScript manual.
Happy scripting.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 1:36 PM
To: [email protected]; [email protected]
Subject: RE: (forte-users) Changing replication options in Fscript?
no it is not. One can compiling properties but not replicationproperties
through Fscript.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 3:24 PM
To: [email protected]
Subject: (forte-users) Changing replication options in Fscript?
Before making a distribution, we modify replication options on some ofour
service objects from within the Partition Workshop (to get rid of the
router partition on some of our applications). Does anyone know ifit is
possible to do this in Fscript? Thanks for your help.
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a
new
email the word: 'Unsubscribe' to: [email protected]

You can set the the number of replicas through fscript BUT the service
object in that partition has to be marked for LOADBALANCE. I didn't find a
fscript command to do that (that was what mnasser was trying to tell you).
But you can get around it by exporting the plan that has the service object
and look for the string LoadBalance = FALSE, then change it to LoadBalance =
TRUE. Import back the plan and you should be fine.
Norocel Popa
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 8:28 PM
To: [email protected]; [email protected]
Subject: RE: (forte-users) Changing replication options in Fscript? -
Tric k
There was one attribute of a service object you couldn't change in fscript..
I think it was whether the service was replicated at all or not (not the
same as setting rep count to 1!).
As Clint would say, "improvise.."
We exported the project containing the service object and snipped out the
part pertaining to the service object in to a little export file.
Then in an fscript script you can branch/checkout the service object and
import the snipped out export file to change the replicated yes/no flag.
Then do whatever other fscript commands make sense.. We tended to leave the
system baseline with the "true" replication flags and let developers run
this little script (only branching the services) to de-replicate all the
replicated services prior to trying to run from their workspace, etc.
Worked like a charm.
-Greg
-----Original Message-----
From: Taras Katkov
To: [email protected]
Sent: 12/1/99 2:57 PM
Subject: Re: (forte-users) Changing replication options in Fscript?
"setappcompcompiled", "setPARTrepcount" can be used in fscript during
application build.
I mean PERIOD!
Taras Katkov
f.e.
FindAppComp AppNAme_PartXX
SetAppCompCompiled MyNode 1
SetPartRepCount MyNode YY
SetPartArgs MyNode \"Whatever\"
SetPartThreadPkg MyNode DCE
commit
[email protected] wrote:
>
Yes through escript one can achieve changing the properties but onecannot
do it when one is partitioning the app where the router gets createdand
assigned ( which is fscript) and the single threadedness of thepartition
takes effect ( for loadbalancing ) except from the partitioningworkshop
(GUI) itself.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 3:39 PM
To: [email protected]; [email protected];
[email protected]
Subject: RE: (forte-users) Changing replication options in Fscript?
Yes you can do it, but you actually do it in EScript not FScript lookfor
the following types of command "assignappcomp", "unassignappcomp",
"setappcompcompiled", "setrepcount", "findagent", "findsubagent",
"findparent" etc.. So start with your EScript manual.
Happy scripting.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 1:36 PM
To: [email protected]; [email protected]
Subject: RE: (forte-users) Changing replication options in Fscript?
no it is not. One can compiling properties but not replicationproperties
through Fscript.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, December 01, 1999 3:24 PM
To: [email protected]
Subject: (forte-users) Changing replication options in Fscript?
Before making a distribution, we modify replication options on some ofour
service objects from within the Partition Workshop (to get rid of the
router partition on some of our applications). Does anyone know ifit is
possible to do this in Fscript? Thanks for your help.
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in anew
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a
new
email the word: 'Unsubscribe' to: [email protected]
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

RE: (forte-users) Object Request Brokers.....

Similar Messages

Maybe you are looking for