Upgrading to Headstart Ruleframe

At the moment we have several applications running. Some have been build using
Headstart Desinger/2000, while others have been build using Headstart
Ruleframe.
Of course, because of this we have to maintain both versions of Headstart. We
would like to use only one version of headstart, Headstart Ruleframe.
Is there any information on how to easily migrate the applications using Headstart
Designer/2000 to Headstart Ruleframe?
Is it possible to regenerate an application replacing Headstart Designer templates and libraries with those of Headstart Ruleframe?
Which steps are involved?
Appreciate your help!
null

Matthijs,
Yes, it is possible to migrate the Headstart software to the new versions (i.e. patch 12) without really starting to use CDM RuleFrame.
In each form that will be recompiled after you upgraded Headstart to patch 12, there will be a call to qms_transaction_mgt.open_transaction and close_transaction. So these packages should be installed but because no business rules are put on the rule stack (TAPI does not call CAPI package), the close_transaction will always succeed.
Notice that several utilities will be disabled after installation of CDM RuleFrame (e.g. the utility to workaround the Mutating Table problem, which has become obsolete as soon as you start using CDM RuleFrame).
Kind Regards, Marc

Similar Messages

Designer and Headstart 6 upgrade to 6i questions

One of my customer is using Developer 6i, Designer 6.0 and
Headstart 6.0
He is considering upgrading to Designer 6i and possibly
Headstart 6i
New features of Designer 6i are well documented on technet but
what about Headstart 6i?
What are the new features?
Is it worth it or can you keep on using Headstart 6 with
Designer 6i?
My customer was quoted roughly $2500 per upgrade.
He is not ready to pay this amount of money without first
knowing exactly what he'll get, obviously.
From what I have read on technet, Headstart 6i is now part of a
broader tool called iDevelopment Accelerators.
Yet, what does Headstart 6i offer that Headstart 6 does not?
And do you HAVE to upgrade to Headstart 6i if you upgrade to
Designer 6i?
All comments welcome,
Xavier Neys
[email protected]
The DOC b.v.
www.thedoc.nl

Not the easiest thing to find, try patch no: 2686763
In the simple patch search in metalink choose Oracle Designer - Respository Family and Designer/Repository 9i Release.
Cheers.

Upgrading Headstart

Hi there,
I have been tasked with upgrading 9 applications to Developer 6i
suite. All applications have been generated with Headstart. I
have read many of the other listings regarding upgrading but I
feel that I am not getting the full picture. I have also read
of references to the 'migration guide' but I cannot find it on
the CD. So, I would like assistance by either getting a copy og
the migration guide or general advice on how to approach the
upgrade. Installtion information is as follows:
Existing:
Headstart 3.4.2
Forms 4.5
Reports 2.5
Designer 1.3.2
Database 8i.
Need to upgrade to:
Headstart 6.5
Forms 6i
Reports 6i
Designer 6i
Database - unchanged on 8i.
Many thanks in advance.
Sajit

When you purchase the iDevelopment Accelerators (which contain
Headstart 6i), it comes with a Migration Guide for moving from
Headstart 2.1.2 (for Des 212/60) to 6i. However, I see that you
are still on Headstart 3.4 (for Des 132). I will email you the
migration guide for Headstart 3.4.x to 6i.
Regards,
Lauri

UPGRADE Headstart 6523 TO Headstart for 9i 6530 concise step by step proc

Hello,
We are using Headstart for Designer 6i. We have upgraded our designer repository to 9i and therefore have to upgrade the headstart to "Headstart for Designer 9i 6530, 6531 and then 6532". The upgrade pdf file states that we should patch upgrade to 6521, 6522, and 6523 before applying the main UPGRADE to Headstart for 9i (6530). We have successfully patch upgraded to 6523 without problems. However when we run the patch script 6530 against the repository, we have come out with so many invalid objects under the HSU65 schema. WHY ?
Could someone give us a concise step by step procedure for doing this upgrade.
Your response will be very much appreciated.

Oracle 9i WEB-forms, with or without Headstart?

We have some applications that are created with Designer 2.1.2 and Headstart 2.1.2 and we are about to migrate these to Oracle9i Web Forms and here are my questions:
1) What are the advantages/disadvantages if we continue to use Headstart?
2) What do we need to get Headstart working together with Oracle 9i Web Forms?
3) Where do we order new software/license for "Headstart for 9i"?
4) Are there any way we can get support on Headstart except the forum on OTN?
5) Briefly explained, if we remove Headstart and replace it with own-developed code, what would our main tasks/problems be?
6) Are there any functionality we cannot have if we remove Headstart from our applications?

1) What are the advantages/disadvantages if we continue to use Headstart?
The advantages would be more or less the same as for Headstart 2.1.2, except for the fact that you can make use of new features, and it runs on the web too! A 'disadvantage' would be that only web forms is supported out of the box (not client/server) and you need to set up an application server. Of course you need to migrate, which sometimes can be a difficult task. However, this depends on things like customizations on top of Headstart, typical client/server features that have been used and that cannot be migrated to web forms etc. A lot of this has been documented in the Headstart Migration Guide.
2) What do we need to get Headstart working together with Oracle 9i Web Forms?
We build Headstart against Designer 9i (+ Developer 9i that comes with it). At this point we still are working on Headstart for Designer 9i.
3) Where do we order new software/license for "Headstart for 9i"?
Contact your Oracle Consulting Manager, or call Oracle and ask for Mike Kruijsdijk.
4) Are there any way we can get support on Headstart except the forum on OTN?
You can hire consultancy from us or one of our partners.
5) Briefly explained, if we remove Headstart and replace it with own-developed code, what would our main tasks/problems be?
To mention some of them:
- It probably would take man-years to build a template package with the same functionality
- Headstart code at some points deals with Forms bugs, which you now have to deal with yourself
- You have no support any more (upgrades) and need to do upgrades for new versions of Designer yourself. I've seen more than one customer that are years behind with upgrading to new versions of Designer, because of this.
And many more. You really should investigate this thouroughly before you start on this. It would not surprise me if you come to the conclusion you might as well rebuild your applications completely.
6) Are there any functionality we cannot have if we remove Headstart from our applications?
You can have anything you like, as long as you build it yourself. But for practical reasons I suppose you will not have RuleFrame for example.
As long as you don't start building new applications with it, the code practically is yours, so you might consider to do the upgrade of Headstart yourself. Of course support will be more difficult, but you still can hire consultancy.
Jan Kettenis

Create CAPI definition problem with Headstart 6i / Designer 6i rel. 4.3

During migration from hsd50/des60 to hsd65/des6i rel 4.3 of an application using CDM ruleframe: according to the migration guide, one step is "Upgrading Existing CDM RuleFrame objects", which includes running the Create CAPI definition (Headstart utility). After that step we assume de created CAPI's should be generated together with the Table API. But executing the CAPI-scripts results in errormessages. After comparing the 60 and 6i versions, we found a bug, probably caused by the Headstart utility: In the package body, after the header of the first function of the Business Rule Check Functions, suddenly the declaration section of the package is again inserted, and after that the first function is again defined followed by the rest, causing also a missing end statement at the end of the package.
Is this known, and if so, is there a fix available?
Regards, Paul.

Paul,
We have found the cause for your other problem (the repeating of the declaration section).
With 6.5 a new package property Private Declaration was introduced in Designer.
This property should officially be used instead of PL/SQL block to specify package body declaration
(assuming you define all package procedures and functions in separate PL/SQL Definitions).
However, at first the migration from an earlier version of Designer did not pose any problems
because of Designer bug 1470283. That's why you won't find anything about this in the Headstart Migration Guide.
Now that Designer bug is fixed, migrating a CAPI causes part of the PL/SQL Block to be moved to the Private Declaration.
If you then generate the CAPI package to the database, it works fine, but when you run the CAPI utility again,
it inserts the package declarations again in the PL/SQL Block (leaving the Private Declaration in tact).
That's when you get duplicate package declarations. We logged this as Headstart bug 2527128.
You already found a workaround: deleting the CAPI and generating it again. Another workaround is
moving the Private Declaration to the top of the PL/SQL Block (this allows you to keep your existing
Revision History).
Hope this helps,
Sandra

How to purchase Headstart Supplement Option (software maintenance)

We own a license of Headstart (version 6.5.1.13) and run it with Designer 6i on Oracle9i database. This Headstart software was purchased at a time when upgrade support was not available or we were not aware of that option. I've been in contact with my "local" Oracle consulting contact team for about a month and they cannot determine how to purchase the software update support. It's not available in the Oracle store unless you purchase a new license. I need the Supplement Option in order to upgrade our Headstart software (and Designer/Developer) to work with Oracle 9iAS. What is the procedure to purchase this support?

This has been resolved.

Simple Upgrade using Patchset 13

Hi,
I have been following the 'Simple Upgrade' Process and it's not
clear to me how the Headstart Accounts get migrated - HST50
(template package owner) and HSU21 (Headstart Utilities
administrator). I can't see any references to this in the
documentation.
Do they need to be reinstalled after performing the Repository
migration? Should the user accounts be exported and then
imported into the new database ? Should I install the users
again using the new Headstart 6.5 installation disk? I notice
that in the migration guide, it is necessary to run some of the
new utilities, which are only available with the 6.5
imstallation
(These accounts are not included in the migration of Repository
subordinate users as they do not need to be created as
Repository users).
thanks
David

In the Patch 13 instructions (readme13.htm), steps 8 and 9 tell
you how to upgrade your Headstart users.
8. Logon to sqlplus as the Headstart Template Package owner. Run
the following scripts from the <Headstart Home>\hst\scripts
directory.
cg$err.pks
cg$err.pkb
cg$err_msg.sql
new_ofg_msg.sql
recompl.sql
invalid.sql - you should see 'no records selected'.
9. Logon to sqlplus as the Headstart Demo Application owner. Run
the following scripts from the <Headstart Home>\hst\demo
directory.
dropdemo.sql
instdemo.sql
If you want to migrate these users to a new database, you should
just use the regular import and export tools.
Regards,
Lauri

Head Start for Oracle Applications

Has anyone heard of upgrade of headstart for Oracle Apps for
latest Designer version version 6.0, any updates would be
appreciated
Ajit Apte
null

Jan Barlow (guest) wrote:
: Ton van Kooten - Headstart Team (guest) wrote:
: : Ajit Apte (guest) wrote:
: : : Has anyone heard of upgrade of headstart for Oracle Apps
for
: : : latest Designer version version 6.0, any updates would be
: : : appreciated
: : : Ajit Apte
: : Ajit,
: : As you probably know Headstart for Apps is a special flavor
: : of Headstart meant to generate extensions to Oracle
: Applications
: : ensuring the same look and feel as Oracle Applications. Since
: : Oracle Applications is still on forms 4.5 and only with
release
: : 11i will go to forms six there is no version for Headstart
for
: : apps that works on forms 6.0. There are however plans to
: develop
: : a version for forms 6.0 and the first specs are in
development.
: : As we will have more information about that new release we
: will
: : post that on OTN as well.
: : By the way, Headstart for Apps information is not yet
: available
: : on OTN.
: : Ton
: Does the current Headstart for Apps support Forms 4.5.10 web
: deployment or is it only supported for client-server
: implementation? Headstart for Apps was used extensively at
this
: organization to build a custom application. We are assessing
: the feasibilty of deploying portions of this application on a
: Release 11 NCA and need to know if this is supported.
The current version of Headstart for Apps (release 1.2) supports
web deployment. Which means that release 11 NCA is also
supported.
Ton
null

Business Rules framework?

In ancient times I have used Headstart Ruleframe to implement the business rules.
What is the best strategy nowadays to implement business rules in an apex web application. Preferably all the BR's would be applied to in the database through triggers and packages so that the BR's ara always validated even when trying to modify records through sql plus.
Thanks,
Joep

You might want to look at Rules Manager/Expression Filters:
http://download.oracle.com/docs/cd/E11882_01/appdev.112/e14919/exprn_intro.htm#EXPRN001
which has it's own {forum:id=268} forum.
As it sounds like you're looking for something that's independent of the (APEX) front-end, it's probably a good idea to take this question to other DB forums: Database General, SQL & PL/SQL etc.

Quality Check view foreign key

Headstart Ruleframe Designer6i
Running utility quality check view definition
Report states that complete property for _CG foreign key must be set to "NO" to keep from being generated in DB. However if foreign key is used in formmodule error CDG-3436 is raised : " Invalid Linkage ". I'm I correct in assuming that Complete property has to be set to "YES" and Validation property to "CLIENT" to avoid the errors?

You are correct. I will log this as a bug in the quality check report.
Thanks,
Lauri

Unable to delete lookup

Designer 6i Headstart Ruleframe.
I have a form with basetable(vapi) block with an optional lookup value (optional in form, view and table),
on deleting the lookup value (updating to null) the lookup id remains and therefor value appears again on requery. Bug? Workaround?

Set the validation of optional foreign keys to both and generate again.
Now there will be code generated for clearing the id field.

Does Headstart 6.5.4 supported in Oracle 11g R2?

Hello,
In my application I'm using the following components
CM SDK 9.0.4.2.26
Head Start 6.5.4
Can somebody suggest me is Head Start 6.5.4 supported in Oracle 11g r2 please? If not how to upgrade it to JHeadStart.
Kind Regards,
Kam

Headstart and JHeadstart are different tools. Headstart is a development accelerator for Oracle Designer/Forms, JHeadstart is a development accelerator for Oracle JDeveloper/ADF.
The prerequisites of Headstart are
* Oracle 10g database in runtime environment (where CDM RuleFrame is used)
* Headstart Oracle Designer 10g, patch 6.5.4.0
* Oracle Designer 10.1.2.0.2 or above.
* Oracle 10g Developer Suite (10.1.2.0.2)
I don't know if Headstart 6.5.4 is supported with Oracle 11gR2. The Oracle Designer version is supported with a 10gR2 and a 11gR1 database. So for your development environment you will need a 10gR2 or 11gR1 database.
Regards,
Mark

Get_num_value return no data found with headstart 6.5.2.3

Hi,
We are migrating an application based on headstart (capi generator 6.0.2.1). Our migration upgrade headstart to 6.5.2.3 (capi generator 6.5.3.4).
The capi generator 6.5.3.4 generate the get_row function, but this function doesn't call the find_on_stack function. With the old version of headstart, the get_row call find_on_stack. On another project I did for another company, I see that the capi generator 6.5.2 generate the get_row and this function call the find_on_stack.
The capi generator change after the version 6.5.2. I search on this forum and I see this "2227746 - ENHANCE RULEFRAME PERFORMANCE BY MINIMIZING CAPI USE OF FIND_ON_STACK" !
Our application has business rules that call get_num_value, get_char_value, etc... These get_???_value call get_row and get_row call slct function of the tapi.
Before the migration, these get_???_value functions returned always a row. Because the get_row scans the pl/sql table with the find_on_stack function.
Now, these get_???_value functions return the error no data found !!!. The function doesn't call the find_on_stack, but call the slct function of the tapi. The slct returns no data found.
I have this bug (no data found) when a business rule is executed from a delete cascade. The parent row is not there and the br returns no data found. The old version search the parent row with the find_on_stack and returns the row.
So, I suppose that the "ENHANCE 2227746" drop too much find_on_stack call !
Do you have a patch for this or I modify the capi generator ?
Thanks.

Geert,
The workaround mentioned above is not sufficient. It makes sure the correct value is returned inside a single transaction, e.g. when a transaction is rolled back, but when a new transaction is opened, it will still return the cached values, even though the database value might have changed between the closing of the first and the opening of the new transaction.
To make sure the correct value is returned, we should also keep track of the id of the transaction in which the cached values are stored. Only when this ID is the same as the ID of the current transaction, we can be sure the cached value is the correct one. In all other cases the database value must be used.
The following changes can be implemented as a workaround:
In the CAPI generator package HSU_CAPF:
- In procedure create_declarations add declarations of package variables to store transaction id for the cached values g_current_row and g_cached_row.
- In procedure create_init fill the transaction id when g_current_row is filled.
- In procedure create_get_row:
- Enclose if-statement as mentioned above, to make sure correct value is returned after transaction is closed
- Add extra restriction to the if-statements to determine whether package variables can be used
- remove part to use value from CAPI stack
- fill transaction id when g_cached_row is filled.
This solution slows down the retrieval of data via the get_% functions. It only uses cached values when they are cached in the same transaction as they are retrieved in.
Hope this helps,
Harold Oortwijn

Migration of forms and reports developed using Headstart VERSION 3.4.1

Hi,
We have developed an application in forms 4.5 reports 2.0 based on repository 1.3.2 and Headstart
Designer/2000 Template Package VERSION 3.4.1
Now we want to migrate to Oracle 9i(web enabled)
1)Is it possible to migrate only the forms and reports in 4,5 to 9i without the designer repository?Can the repository be left out?
2)What about the templates and packages on the 2000 Headstart version.Is it necessary to migrate the same to 9i also?
2)In case the repository has also to be migrated how do i go about migration to 9i??
4)In case the headstart template/packages to be migrated how do i migrate to 9i?
5)Where is the documentation available for headstart?
Kindly help..

Hi 23768 ( ;-) ),
There is a whole wealth on information regarding upgrade/migration of headstart generated application systems.
What you need is a licence on iDevelopment Accellerators and the Supplement Option (cso.oracle.com) to download this material.
Contact your Oracle Consulting representative if you would like to know how to do this.
Best regards, Marc Vahsen
Headstart Team
Oracle Consulting Netherlands

Upgrading to Headstart Ruleframe

Similar Messages

Maybe you are looking for