Forte Upgrade to L ?

Hello Everybody,
Background
We are running several applications on Forte' 3.0.J.1, and we also have
applications running on Conductor 1.0.J.0.
the problem,
is as per defect # 44269 a bug fix can be taken careof by upgrading the
Conductor to 1.0.L.0 from C.1.0.J.0,
my question is,
do we have to Upgrade Forte to 3.0.L.0 from 3.0.J.1.
I will appreciate all the help. Thanks.
arabsdteenergy.com

That model can be upgraded to Mavericks (10.9)
To install Mavericks, you need one of these Macs:
iMac (Mid-2007 or later)
MacBook (13-inch Aluminum, Late 2008), (13-inch, Early 2009 or later)
MacBook Pro (13-inch, Mid-2009 or later),
MacBook Pro (15-inch or 17-inch, Mid/Late 2007 or later)
MacBook Air (Late 2008 or later)
Mac mini (Early 2009 or later)
Mac Pro (Early 2008 or later)
Xserve (Early 2009)
Your Mac also needs:
OS X Mountain Lion, Lion, or Snow Leopard v10.6.8 already installed
2 GB or more of memory
8 GB or more of available space

Similar Messages

Regarding Forte Upgrade to L

Hello Everybody,
I did some digging around and found that Forte recommends using same
revision in
order to avoid problems. A good reading on this subject was found in
ID # 310
Subject: Forte Product Mix
Category: Product/Platform alerts.
Tech Note: 11803.
Thanks for everybody's help.
Sanjeev.

Answer is NO. It will cost you $129.00.
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
iTunes: MacOSG Podcast
 An Apple User Group 

Errors in Forte 3.5 -Upgrade issue

hello ,
We are having a frequent disruption in the communication SO which has an
externalConnection Class. Did anything change in 3.5? We did not have
these errors in 3L!
After these erros, we have a mutex locking problem which leaves our
application hanging.
Any help will be greatly appreciated!
thanks
suma
Here is an Excerpt of the log file
Task 9: extConn4030a808.Write: 194 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
24-May-2001 09:16:47: VH.G.G..GUIT/GUI0/PLAXRC172.23.4.401/../..;PGYX;
Task 9: extConn4030a808.Write: 233 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:47
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:47
regards,
Suma Venkatesh

-----Original Message-----
From: Venkatesh, Suma
Sent: Thursday, May 24, 2001 2:39 PM
To: '[email protected]'
Subject: Errors in Forte 3.5 -Upgrade issue
hello ,
We are having a frequent disruption in the communication SO which has an
externalConnection Class. Did anything change in 3.5? We did not have
these errors in 3L!
After these erros, we have a mutex locking problem which leaves our
application hanging.
Any help will be greatly appreciated!
thanks
suma
Here is an Excerpt of the log file
Task 9: extConn4030a808.Write: 194 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment
laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:29
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
24-May-2001 09:16:47: VH.G.G..GUIT/GUI0/PLAXRC172.23.4.401/../..;PGYX;
Task 9: extConn4030a808.Write: 233 bytes written to 10
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Error #: [501, 152]
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Thu May 24 09:16:47
Exception occurred (locally) on partition "MerlinWindows_cl41_Part8",
(partitionId = F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105, taskId =
[F2E11800-5003-11D5-BF99-AE145F2AAA77:0x105.7]) in application
"MerlinWindows_cl41", pid 23406 on node laxrc2 in environment
laxrc2.
INFORMATION: Error parameters for Set:0 Msg:0:
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Thu May 24 09:16:47
regards,
Suma Venkatesh

Re: (forte-users) Unstable server ENV after upgrade to Forte30M2.

I see/suggest a few things:
1) In your #1, you mention ".... development and test environments which use the
same Forte 3M installs through links ...". This concerns me. On our UNIX box
each environment has it's own directory containing it's own install. If your
environments are some how sharing a node manager, log directory or processes (to
name a few things) that is a recipe for disaster. They may be competing for
resources and usually the first one started will win.
2) I haven't done a lot with compatibility levels, but if an application built
in dev is to run in test it may be important that node managers and services
(autocompile, codegen etc.) be at the same level (????).
3) Check the definition files, to make sure the two environments operate
independently. If they are both trying to write to the same log file the one
started up first will work while the second will not as the file will be "busy".
4) We usually use rpcreate (newer version) to create brand new repositories.
Than we export/import the source code that we need. Also it is important to
force compile ALL plans in a workspace at least once after doing the import.
This will ensure that all of the code is "speaking the same language". The other
compile, only compiles those pieces of code that changed from the last compile.
Hope this helps.
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!
"Braja Chattaraj" <forte_brajachotmail.com> on 09/13/2000 03:43:57 PM
Please respond to chattaraj_braja_NONLILLYlilly.com
To: forte-userslists.xpedior.com
cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
Subject: (forte-users) Unstable server ENV after upgrade to Forte 30M2.
We are running Forte 3M2 clients and server in our test environment with
clients on NT and server on Solaris 2.6. Eversince the upgrade from 3L to 3M
we have been having an unstable environment that does not remain alive for >
10 mins. These are the details of the Forte installs and server setups :
1. The server hosts the development and test environments which use the same
Forte 3M installs through links (same ftcmd, ftexec, nodemgr, etc.). The
environments are at compatibility levels 0 and 1 respectively.
2. The two environments have the same definition files (defining the ENV
variables), though seperate copies and the two environments are hosted on
different ports on the same server.
3. While building the new 3M environmnets in DEV and TST, we exported the
old 3L repositories and imported them into the new 3M repositories and
deployed the applications.
While the DEV environment is stable the TST environment is not. This has
been observed while moving plans between the environments (export and
import) using fscript commands, deploying the apps after the move using
fscript, and testing the apps. Sometimes it has come down right after a
startup. There is no programatic reference to the environment agent in the
code. So, a programatic shutdown is ruled out.
Does anybody have a clue or a similar experience ?
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BRAJA KISHORE CHATTARAJ
Consultant, Analysts International.
Work : Sphinx Pharmaceuticals (A division of Eli Lilly & Co.)
(919) 314-4134
Home : 1801, Williamsburg Rd., #41H, Durham, NC 27707.
(919) 463-7802
E-mail : forte_brajachotmail.com
Visit us www.analysts.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://profiles.msn.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

We found a solution to our issue.Their desktops were in a lockdown environment and the essbase.id file located in the windows directory was locked as well. This file is responsible for assigning ports etc and it couldn't be updated for the 6.5.4p2 upgrade. Once the file was deleted and the user reconnected to Essbase, the essbase.id was reset and they could connect.

Unstable server ENV after upgrade to Forte 30M2.

We are running Forte 3M2 clients and server in our test environment with
clients on NT and server on Solaris 2.6. Eversince the upgrade from 3L to 3M
we have been having an unstable environment that does not remain alive for >
10 mins. These are the details of the Forte installs and server setups :
1. The server hosts the development and test environments which use the same
Forte 3M installs through links (same ftcmd, ftexec, nodemgr, etc.). The
environments are at compatibility levels 0 and 1 respectively.
2. The two environments have the same definition files (defining the ENV
variables), though seperate copies and the two environments are hosted on
different ports on the same server.
3. While building the new 3M environmnets in DEV and TST, we exported the
old 3L repositories and imported them into the new 3M repositories and
deployed the applications.
While the DEV environment is stable the TST environment is not. This has
been observed while moving plans between the environments (export and
import) using fscript commands, deploying the apps after the move using
fscript, and testing the apps. Sometimes it has come down right after a
startup. There is no programatic reference to the environment agent in the
code. So, a programatic shutdown is ruled out.
Does anybody have a clue or a similar experience ?
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BRAJA KISHORE CHATTARAJ
Consultant, Analysts International.
Work : Sphinx Pharmaceuticals (A division of Eli Lilly & Co.)
(919) 314-4134
Home : 1801, Williamsburg Rd., #41H, Durham, NC 27707.
(919) 463-7802
E-mail : forte_brajachotmail.com
Visit us www.analysts.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Michael,
thanks for your reply. Sorry I forgot to mention that our application server is running on windows 2003 server. Our variable and the corresponding value is uppercase. It is not the name of our reports server. For the test I used a hard coded reports server name. The same reports server name is also included in the call to web.show_document whitch worked fine.
I also tried to read other variables defined in .env file. The only variable I could read was 'FORMS_PATH' which is defined in our application specific .env files. But the value I got had nothing in common with the value defined in these files ???
regards gisela.

Re: (forte-users) Partial live upgrade

Hi,
It should be possible using the Compatibility Level for instance. Then, you
will be able to install the CL1 having the CL0 still running. You could test
the CL1 in an IVP to verify that the installation is correct and then,
uninstall the CL0. May be the partition should be seen as a reference
partition. You can find some information on the Nomadic PC section of the
documentation (you can find a sample on
http://perso.club-internet.fr/dnguyen/). The normal case is that you need to
upgrade your server, having still old versions of your clients.You can use
converters to manage the interface modifications between versions.
Other ways are possible with libraries, also using Compatibility Level, like
Conductor does with processes (they are conditionned as libraries with their
own compatibility level at each distribution). The engine creates the processes
instances with the last level of the library, but the instances already there
are still running the old version.
One last solution is to manage services reconnection, using the
ReleaseConnection to rebind service objects from the client. So you can
reinstall a new instance of your partition and then use it without restarting
your client. Depending on the OS, you may have a lock on the file. So you will
need to stop your partition, reinstall it and restart the partition. To make
this possible, you should not have the autostart activated on your environment
during the manipulation. This solution does not need to use the Compatibility
Level.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
http://perso.club-internet.fr/dnguyen/
andrea harper a écrit:
I have made a partial distribution and I would like to perform a live
upgrade. The partition that is being upgraded has been identified however,
I am not able to implement the live upgrade.
Has anyone ever tried to implement code changes while an application is
still running and if so how were you able to accomplish the upgrade?
Thank you.
Reserve your name now at http://www.email.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

Hi,
It should be possible using the Compatibility Level for instance. Then, you
will be able to install the CL1 having the CL0 still running. You could test
the CL1 in an IVP to verify that the installation is correct and then,
uninstall the CL0. May be the partition should be seen as a reference
partition. You can find some information on the Nomadic PC section of the
documentation (you can find a sample on
http://perso.club-internet.fr/dnguyen/). The normal case is that you need to
upgrade your server, having still old versions of your clients.You can use
converters to manage the interface modifications between versions.
Other ways are possible with libraries, also using Compatibility Level, like
Conductor does with processes (they are conditionned as libraries with their
own compatibility level at each distribution). The engine creates the processes
instances with the last level of the library, but the instances already there
are still running the old version.
One last solution is to manage services reconnection, using the
ReleaseConnection to rebind service objects from the client. So you can
reinstall a new instance of your partition and then use it without restarting
your client. Depending on the OS, you may have a lock on the file. So you will
need to stop your partition, reinstall it and restart the partition. To make
this possible, you should not have the autostart activated on your environment
during the manipulation. This solution does not need to use the Compatibility
Level.
Hope this helps,
Daniel Nguyen
Freelance Forte Consultant
http://perso.club-internet.fr/dnguyen/
andrea harper a écrit:
I have made a partial distribution and I would like to perform a live
upgrade. The partition that is being upgraded has been identified however,
I am not able to implement the live upgrade.
Has anyone ever tried to implement code changes while an application is
still running and if so how were you able to accomplish the upgrade?
Thank you.
Reserve your name now at http://www.email.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

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

Metaframe Servers Flaky Since Forte Runtime Upgrade from 'J'to ' L'

Our Metaframe users ahve to repeatedly try to login to Metaframe, generally
successfully connecting to our application after x number of trys. This
has just begun occuring since we upgraded the Metaframe servers from the 'J'
runtime to 'L'.
Has anyone else experienced this type of problem? We've lost our Metaframe
people and have not yet succeeded in contacting Citrix.
Bob Mueller
Concert USWest, Work: 408-501-4822, Page: 408-231-0036
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.
http://www.concert.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Il suffit de mettre les BTD/BTX sur un drive réseau (net use X:
\\server\share_point),
puis d'installer des icônes pour les clients: ftexec -fi bt:x:\MyApp.
Pour que les noeuds ne s'auto-enregistrent pas, peut-être mettre un password
Ou bien définir les noeuds comme un 'groupe' et donc seul le groupe est
connu.
Si mettre le mot de passe suffit pas, et si vraiment le model node gêne,
alors il
faut un autre environment manager.
I think that to avoid install, the software could be located on a shared
drive,
and users linking to it through running 'ftexec' or directly the compiled
binaries.
For nodes not to appear in the environment as nodes, they could be defined
as members
of a model node '(which then would be in the environmnet)'
Putting a password in the environment could prevent nodes to be registered
there, but
might prevent the apps from being executed.
Cheers,
j-paul gabrielli
Sema DTS
-----Message d'origine-----
De: Thomas Felix [mailto:tfelixaxialog.fr]
Date: mardi 2 mai 2000 14:14
À: forte-userslists.xpedior.com
Objet: (forte-users)
bonjour a tous
je souhaites installer une application distribuée sur des postes clients.
Y'a t'il moyen de ne pas installer les noeuds de ces postes clients sur l'
active environnement lié au développement et si oui comment?
hi
I would like to install an application on clients workstation
Can i install this nodes in a different Active environnement than this one
that we use for the developpement ?
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

Problems with 2011 Kia Forte hands free following upgrade to ios 7.1

I have had nothing but problems with the Bluetooth hands free feature in my 2011 Kia Forte ever since I upgraded to IOS7.1. I have removed and repaired the device to no avail. I have discovered the following behavior through the troubleshooting I have done so far:
If I use hands free to dial, the phone will dial but nothing is heard on either end of the call. If I switch the audio feed from the car to iPhone, both parties can then talk, but as soon as I switch it back to the car there is silence on both ends. I have determined that streaming Bluetooth audio still works in my car in spite of the hands free issues. I can switch audio back and forth during the entirety of the call and as long as audio is set to either iPhone or speaker it works, it just won't work when the car is selected.
I have checked and there is no new firmware available from Kia for my vehicle's Bluetooth.
Any thoughts?

Same problem for me after the update. No matter what movie I try to download, it stalls halfway. Interestingly, could be a wider iTunes issue as I ended up with the same problem trying to download movies to my MacBook Air.

Oracle Upgrade - any need to reinstall Forte?

Hi Folxs
We will upgrade VMS and Oracle and I like to know if there are any nasties
that anyone might know about with Forte after the event.
TIA
Dirk Haben
+61 (08) 9265 5758
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

No opinions/replies on this???
. . . . Pete

Re: Oracle Upgrade - any need to reinstall Forte?

Hi Folxs
We will upgrade VMS and Oracle and I like to know if there are any nasties
that anyone might know about with Forte after the event.
TIA
Dirk Haben
+61 (08) 9265 5758

kalvinhui wrote:
do i need to install all my softwares and will it change all my current setting on my mac after i have done the installation from leopard to snow leopard?
No. That will all remain the same. Here's the instructions: http://manuals.info.apple.com/enUS/Snow_Leopard_InstallationInstructions.pdf

Oggetto: (forte-users) Unstable server ENV after upgrade toForte 30M2.

We experienced a similar behaviour.
On a solaris 3500 we contiuned to have core dump anytime we tryed to run any
fortè process.
We found no solution (neither had SUN), but to change the motherboard, this
thing made a miracle, now we are using that server as the development server for
50 project.
Maybe there is some bug with some firmware or hardware config.
Luca Gioppo

Question about creating libraries in Forte'

I'm looking into creating compiled libraries in Forte' to create a
"plug-and-play" interface among different implementation products. This
would allow us the ability to remove one library and upgrade it with
another assuming that the interfaces were the same. I'm using the
AddProjToLib to create a "super library" and am setting all of the
components as compiled. I am able to make the application distribution
with no problem. The problems that I am having are two-fold:
1) First auto-compile services cannot handle this "super project"
correctly. Don't get me wrong I HATE autocompile services but I decided to
give it a shot and see what happened. With that avenue gone, I went to
fcompile the individual libraries...these have to be done by supplier plan
order which is no big deal. The problem I ran into was that Forte' lower
cases all of the directory names, but the linker expected in some cases
that the directories would have some uppercase letters. The general rule
of thumb I found was that the directory name has to match the library name
generated. Forte' generated the library name with the proper letters
uppercase, but failed to do this to the directory structure. Obviously
this makes automating library creation a little more painful. This really
isn't a show stopper just a point I'd like to bring up in case and Forte'
people actually read these threads.
2) The major road block I ran into is the fact the Forte' statically
stores the full path of the libraries it is using during link/compilation
in the generated shared library. Forte's solution of just creating
symlinks (solution I found from their Technical Notes) is appalling at best
and does not support having multiple versions of libraries built from a
single installation running on the same machine (Unless you do simulated
environments to create a pseudo-new area...but I don't want to get into
that). Currently we are doing something extremely hoaky to solve this
problem with the few libraries that we have, but if we move to a more large
scale library solution this will not work.
I would love to hear any comments or suggestions about any of this. It is
sad that Forte' does not implement such a basic concept as SHLIB_PATH in
their shared libraries. By not doing this, it makes compiled libraries a
major hassle and potentially a waste of time.
Thanks for any comments that you might have in advance,
Scott Francis
Security First Technologies
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'm looking into creating compiled libraries in Forte' to create a
"plug-and-play" interface among different implementation products. This
would allow us the ability to remove one library and upgrade it with
another assuming that the interfaces were the same. I'm using the
AddProjToLib to create a "super library" and am setting all of the
components as compiled. I am able to make the application distribution
with no problem. The problems that I am having are two-fold:
1) First auto-compile services cannot handle this "super project"
correctly. Don't get me wrong I HATE autocompile services but I decided to
give it a shot and see what happened. With that avenue gone, I went to
fcompile the individual libraries...these have to be done by supplier plan
order which is no big deal. The problem I ran into was that Forte' lower
cases all of the directory names, but the linker expected in some cases
that the directories would have some uppercase letters. The general rule
of thumb I found was that the directory name has to match the library name
generated. Forte' generated the library name with the proper letters
uppercase, but failed to do this to the directory structure. Obviously
this makes automating library creation a little more painful. This really
isn't a show stopper just a point I'd like to bring up in case and Forte'
people actually read these threads.
2) The major road block I ran into is the fact the Forte' statically
stores the full path of the libraries it is using during link/compilation
in the generated shared library. Forte's solution of just creating
symlinks (solution I found from their Technical Notes) is appalling at best
and does not support having multiple versions of libraries built from a
single installation running on the same machine (Unless you do simulated
environments to create a pseudo-new area...but I don't want to get into
that). Currently we are doing something extremely hoaky to solve this
problem with the few libraries that we have, but if we move to a more large
scale library solution this will not work.
I would love to hear any comments or suggestions about any of this. It is
sad that Forte' does not implement such a basic concept as SHLIB_PATH in
their shared libraries. By not doing this, it makes compiled libraries a
major hassle and potentially a waste of time.
Thanks for any comments that you might have in advance,
Scott Francis
Security First Technologies
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

VS 2010 Silverlight project upgraded to VS 2013 - not hitting break point.

dear Readers,
thank you for taking the time to read this posting.
we had developed a SL project using VS 2010 and it was successfully upgraded to vs 2013. after a couple of hiccups, the application compiled and ran successfully. the SL app is still in .net framework 4.0.
due to some changes, we wanted to debug the application. Even after marking a couple of break points, we found that vs 2013 did not hit the breakpoints when we ran the app with F5.
We tried the following and it still would not hit the breakpoint:
1. deleted the /bin and /obj directories in SL and .Web projects.
2. deleted .xap file and /bin /obj directories.
We tried attaching/detaching the sl process in Firefox. IE, and chrome - no luck.
any suggestions will be appreciated.
regards
ravi.
Sr GIS App Developer Dallas Fort Worth area, TX

Hi,
Please check the upgrade report details.
Besides, below articles will help you when you upgarde your silverlight application.
https://msdn.microsoft.com/en-us/library/hh397894(v=VS.95).aspx
https://social.msdn.microsoft.com/Forums/silverlight/en-US/475d7dca-eebf-4d50-87f8-957f6415fb63/how-to-upgrade-a-silverlight-4-application-to-silverlight-5?forum=silverlightgen
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Conversion of 1.2 JATO project (non-Forte IDE) to S1AF (JATO) 2.0

JATO Team,
First of all, thank you very much for the Studio integration. It
looks very promising in terms of development time consumption,
deployment to S1AS7, etc., etc. It is impossible to observe all
advantages for so short period of time.
The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio 4,
update 1 (EE) with JDK 1.4 along with the Sun One Application Server
7 (W2000). Everything looks okay, at least all basic tasks listed in
the "Getting Started" manual (project/view/model creation, basic db
connection, running of a test application with the usage of the
Studio's default Tomcat container, etc.) work proper.
During the installation of S1AF module on the top of the Sun ONE
Studio 4, update 1 (EE) I've got an invitation to convert the
existing project to the new environment. As I realized the only JATO
project integrated/created with Forte IDE is applicable for this auto-
conversion (please correct me, if I am wrong. It could solve a lot of
my problems).
Since we are using JBuilder5 IDE and our JATO 1.2 project is
integrated with this IDE I manually re-created project in the Studio
with its file structure, adjusted the project web.xml file, etc. This
new project looks like a proper one (Studio recognize all methods,
fields, bean patterns, e.g.) except at least one "small" thing. All
java files (project viewBeans, Models, custom viewBeanHelpers a.k.a.
pure java) came up with the same wizard image:java class. Stutio with
the S1AF module reserves the special images (and appropriate studio
properties, of course!) for View and Model. Namely this allows to see
the following structure for a ViewBean, for example, in the Studio:
Modules
ProjectName.ModuleName
FooViewBean
JavaSource
JSPs
Non-Visual Components
View Components
On the other hand, I could add either new View or Model in my
manually converted project and add any View Component or bind the
Model fields, for example. Also, the ProjectModuleServlet has been
converted proper. I tried to convert each View/Model class inside the
Studio to its proper wizard image and failed. Addition of a View
Components (with an appropriate code fragments) via the Studio or
auto-binding of model fields is an essential part of 2.0 and should
drastically speed up the development process as it is designed.
Questions:
1. What I missed in my manual conversion of 1.2 JATO project to the
SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
compatible classes (Views and Models) to be recognizable by Studio
wizard (JATO 2.0)?
To be more specific. Some deltas between JATO 1.2 and JATO 2.0 are as
follows (related to a ViewBean):
====++++++++++++++======
JATO 1.2 viewBean extension upon creation:
public class FooViewBeanViewBean extends ViewBeanBase
implements ViewBean
========================
JATO 2.0 (S1AF) version: viewBean extension upon creation:
public class FooViewBean extends BasicBeanBase
====++++++++++++++======
JATO 1.2 viewBean createChild(...) method for one static looks
like:
protected View createChild(String name)
if (name.equals(CHILD_STATICTEXT1))
StaticTextField child = new StaticTextField
(this,
getDefaultModel(),
CHILD_STATICTEXT1,
CHILD_STATICTEXT1,
CHILD_STATICTEXT1_RESET_VALUE,
null);
return child;
========================
JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed (as
a least) to createChildReserved(...):
protected View createChildReserved(String name) {
if (name.equals(CHILD_STATICTEXT1)) {
com.iplanet.jato.view.BasicDisplayField child =
new com.iplanet.jato.view.BasicDisplayField(this,
STATICTEXT1);
return child;
====++++++++++++++======
JATO 1.2 viewBean registerChildren() method for the basic field
types looks like:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1, StaticTextField.class);
registerChild(CHILD_TEXTFIELD1, TextField.class);
registerChild(CHILD_BUTTON1, Button.class);
========================
JATO 2.0 (S1AF) version: viewBean registerChildren() method:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_TEXTFIELD1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_BUTTON1,
com.iplanet.jato.view.BasicCommandField.class);
Is it correct to say that all existing custom Views/Models
(compatible with JATO 1.2) should be converted to their JATO 2.0
variants to be visible by the Studio?
On the other hand, fast overview of 2.0 API shows that the JATO 1.2
is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
example). What exactly (only deprecated methods?) should be adjusted
in the project code (1.2), if necessary, to be visible by Studio as a
View or Model component?
2. Where it is possible to find the list of deprecated methods (from
JATO 1.2 to JATO 2.0 versions). It is difficult sometimes to compare
two versions of API docs (1.2 and 2.0) or compare logs between
versions. Also, JATO 2.0 is significantly larger than 1.2 version. If
the later obviously inherits the ND conversion stage (via the
previous versions), the former obviously has additions incoming from
the integration with the Studio (a.k.a. Forte 4.0).
3. What is the current/future Sun/JATO Team policy with regards to
JATO source code access (version 2.0, at least)? The reason of this
question is as follows: in order to display dates formatted on the
screens we adjusted a couple of JATO 1.2 core classes, for example.
The only minimal, absolutely necessary changes in JATO 1.2 was made,
but anyway...
Sorry for so long multiple question. As Todd wrote in his
announcement mail: "We think you will be very pleased with the new
product...". This is exciting moment, I believe, for JATO Team as
well as for any team involved into the conversion of the full size
application/product from ND to J2EE realm with the JATO as
an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally). The
last step is left in this spiral process to enjoy the ND_Studio
attractive features in the open source environment.
Thank you very much in advance.
Vladimir Ivanov

I'll get some file templates ASAP and provide them to the group.
As for source code, I'm not sure what the policy is. JATO 1.2 is very
close to what JATO 2.0 is, so that should suffice for now.
The community will be informed when we know more about source availibility.
craig
vivanov4114 wrote:
Craig,
Thank you for the answer. To be honest with you I tried to do exactly
the same: I created the small test project and made an attempt to
adjust the existing *.xml files to the new ones. I got some results,
otherwise I couldn't even see my original 1.2 project in the Studio.
Since I am a newcomer in the Studio, I definitely missed something in
my adjustments. I'll try to observe my changes with the fresh head.
On the other hand, I am afraid that my samples are very pure. If you
could post or send me examples of jatoapp.xml and web.xml files (say
for any of you test project) or excerptions from them with the
appropriate patterns (ViewBean and Model peers, at least), I would be
very appreciated. My mail is: vivanov@b...
In the worst-case scenario I see the workaround: to re-create the
project for one of our releases with the Forte 4.1 IDE and auto-
convert it into the JATO 2.0/Studio world using the Studio
facilities. We must get the current project fully
integrated/converted with/to the Studio (at certain point) because,
first, we expect massive coding with the GUI components involved soon
and, secondly, we have around thousand classes related to JATO only
(and a lot of extras).
Coming back to the question #3 from this post. Now we have full
access to the version 1.2, not only to the JATO 1.2 jar file(I
explained some reasons below). Would we expect the same Sun/JATO Team
policy with JATO 2.0?
Thank you again,
Vlad
--- In SunONE-JATO@y..., "cvconover" <craig.conover@s...> wrote:
It doesn't appear that anyone has responded to this so I am goingto
give you the short answer:
The reason you don't see your ViewBeans and Models showing up with
there "wizard created" icons is because of just that. They weren't
created via the wizards. The wizards create xml formatted filesthat
contain metadata of how/what to generate for the ViewBeans and
Models.
ViewBeans will have a .viewbean fiel, Models will have a .sqlmodel
file (for SQL Models), etc. The content of these files describesthe
code that needs to be generated in the corresponding Java classfile.
So LoginViewBean.java will have a peer LoginViewBean.viewbean file.
The code that is generated is place in protected code blocks thatcan
not be modified in the Studio and should not be modified outsidethe
Studio because the code will likely be regenerated and custom mods
inside the protected blocks will be lost.
Now you can make a JATO 1.2 app appear in the Studio just like aJATO
2.0 app by adding a jatoapp.xml file with the proper content and
adjusting your web.xml properly, but it's much more work to getyour
v1.2 ViewBeans and Models to show up like wizard created versions.
Furthermore, even more work to get the display fields to show up
visually.
The good news is that v1.2 ViewBeans will work with newly wizard
created ViewBeans. And if you do go through the trouble of making
your ViewBeans Studio visible like your wizard created ViewBeans,
adding new display fields visually will work along side yourmanually
created fields.
Try creating a new JATO app using the Studio wizards and then go to
the Filesystems tab and look for the jatoapp.xml file and theweb.xml
file.
I am looking for an email that I have that explains how to do a
partial, manual upgrade.
Also, you will get rid of your JATO 1.2 jar and replace with theJATO
2.0 jar in your lib dir.
Hope this will suffice for now.
craig
--- In SunONE-JATO@y..., "vivanov4114" <vivanov@b...> wrote:
JATO Team,
First of all, thank you very much for the Studio integration. It
looks very promising in terms of development time consumption,
deployment to S1AS7, etc., etc. It is impossible to observe all
advantages for so short period of time.
The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio4,
update 1 (EE) with JDK 1.4 along with the Sun One ApplicationServer
7 (W2000). Everything looks okay, at least all basic tasks listedin
the "Getting Started" manual (project/view/model creation, basic
db
connection, running of a test application with the usage of the
Studio's default Tomcat container, etc.) work proper.
During the installation of S1AF module on the top of the Sun ONE
Studio 4, update 1 (EE) I've got an invitation to convert the
existing project to the new environment. As I realized the onlyJATO
project integrated/created with Forte IDE is applicable for thisauto-
conversion (please correct me, if I am wrong. It could solve a
lot
of
my problems).
Since we are using JBuilder5 IDE and our JATO 1.2 project is
integrated with this IDE I manually re-created project in theStudio
with its file structure, adjusted the project web.xml file, etc.This
new project looks like a proper one (Studio recognize all
methods,
fields, bean patterns, e.g.) except at least one "small" thing.All
java files (project viewBeans, Models, custom viewBeanHelpersa.k.a.
pure java) came up with the same wizard image:java class. Stutiowith
the S1AF module reserves the special images (and appropriate
studio
properties, of course!) for View and Model. Namely this allows tosee
the following structure for a ViewBean, for example, in the
Studio:
Modules
ProjectName.ModuleName
FooViewBean
JavaSource
JSPs
Non-Visual Components
View Components
On the other hand, I could add either new View or Model in my
manually converted project and add any View Component or bind the
Model fields, for example. Also, the ProjectModuleServlet hasbeen
converted proper. I tried to convert each View/Model class insidethe
Studio to its proper wizard image and failed. Addition of a View
Components (with an appropriate code fragments) via the Studio or
auto-binding of model fields is an essential part of 2.0 and
should
drastically speed up the development process as it is designed.
Questions:
1. What I missed in my manual conversion of 1.2 JATO project tothe
SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
compatible classes (Views and Models) to be recognizable byStudio
wizard (JATO 2.0)?
To be more specific. Some deltas between JATO 1.2 and JATO 2.0are
as
follows (related to a ViewBean):
====++++++++++++++======
JATO 1.2 viewBean extension upon creation:
public class FooViewBeanViewBean extends ViewBeanBase
implements ViewBean
========================
JATO 2.0 (S1AF) version: viewBean extension upon creation:
public class FooViewBean extends BasicBeanBase
====++++++++++++++======
JATO 1.2 viewBean createChild(...) method for one static looks
like:
protected View createChild(String name)
if (name.equals(CHILD_STATICTEXT1))
StaticTextField child = new StaticTextField
(this,
getDefaultModel(),
CHILD_STATICTEXT1,
CHILD_STATICTEXT1,
CHILD_STATICTEXT1_RESET_VALUE,
null);
return child;
========================
JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed(as
a least) to createChildReserved(...):
protected View createChildReserved(String name) {
if (name.equals(CHILD_STATICTEXT1)) {
com.iplanet.jato.view.BasicDisplayField child =
new com.iplanet.jato.view.BasicDisplayField(this,
STATICTEXT1);
return child;
====++++++++++++++======
JATO 1.2 viewBean registerChildren() method for the basic field
types looks like:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
StaticTextField.class);
registerChild(CHILD_TEXTFIELD1, TextField.class);
registerChild(CHILD_BUTTON1, Button.class);
========================
JATO 2.0 (S1AF) version: viewBean registerChildren() method:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_TEXTFIELD1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_BUTTON1,
com.iplanet.jato.view.BasicCommandField.class);
Is it correct to say that all existing custom Views/Models
(compatible with JATO 1.2) should be converted to their JATO 2.0
variants to be visible by the Studio?
On the other hand, fast overview of 2.0 API shows that the JATO1.2
is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
example). What exactly (only deprecated methods?) should beadjusted
in the project code (1.2), if necessary, to be visible by Studio
as
a
View or Model component?
2. Where it is possible to find the list of deprecated methods(from
JATO 1.2 to JATO 2.0 versions). It is difficult sometimes tocompare
two versions of API docs (1.2 and 2.0) or compare logs between
versions. Also, JATO 2.0 is significantly larger than 1.2
version.
If
the later obviously inherits the ND conversion stage (via the
previous versions), the former obviously has additions incomingfrom
the integration with the Studio (a.k.a. Forte 4.0).
3. What is the current/future Sun/JATO Team policy with regards
to
JATO source code access (version 2.0, at least)? The reason ofthis
question is as follows: in order to display dates formatted onthe
screens we adjusted a couple of JATO 1.2 core classes, forexample.
The only minimal, absolutely necessary changes in JATO 1.2 wasmade,
but anyway...
Sorry for so long multiple question. As Todd wrote in his
announcement mail: "We think you will be very pleased with the
new
product...". This is exciting moment, I believe, for JATO Team as
well as for any team involved into the conversion of the fullsize
application/product from ND to J2EE realm with the JATO as
an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally).The
last step is left in this spiral process to enjoy the ND_Studio
attractive features in the open source environment.
Thank you very much in advance.
Vladimir IvanovTo download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
[Non-text portions of this message have been removed]

Forte Upgrade to L ?

Similar Messages

Maybe you are looking for