Determinations-Server multiple version

Hi,
We are using Haley Determinations Server (9.4) and are planning to upgrade to OPA Determinations-Server (10.2). Is there any issue with hosting Haley Determinations Server (HDS) and OPA 10.2 Determinations-Server on the same IIS server?
Recently I hosted HDS on the same IIS (7.0) as Determinations-Server and since then, I am getting the following error with OPA 10.2 Determinations-Server:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Note: HDS Web Service is working and I am able to access the WSDL.
Please let me know how I can fix this issue.
Thanks in advance,
Aditya

There is no problem with running 9.4 Determinations Server and 10.2 in the same IIS.
There is a known bug with the 10.2 .NET Determinations Server where you are not re-directed to the determinations-server home page on some versions of IIS. This won't stop the determinations server from functioning, but can make it a little annoying when trying to see the deployed rulebases.
Luckily there is a simple work around. The normal URL is
http://<host>:<port>/determinations-server/ If the above URL does not work, use
http://<host>:<port>/determinations-server/default.aspxFor example, when I was testing on port 80 on my local machine I used
http://localhost/determinations-server/default.aspxEdited by: frank.hampshire on Oct 12, 2011 9:03 AM

Similar Messages

  • Determinations Server - SOAP version

    I have generated a java client from my WSDL file (http://localhost:9000/determinations-server9000/interview/soap/MyRuleBase?wsdl) using JAX-WS wsimport.
    However when I attempted to use the Java client, I get the following run time exception.
    SEVERE: SAAJ0140: No NamespaceURI, SOAP requires faultcode content to be a QName
    javax.xml.ws.WebServiceException: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: No NamespaceURI, SOAP requires faultcode content to be a QName
    After a bit of googling, I found that the my JAX-WS client is using SOAP1.2 whereas the Determinations server is using SOAP 1.1?
    How do I force my JAX-WS client to use SOAP 1.1?
    I understand that I can generate a client using Axis2 as well- but my preference would be to use JAX-WS.

    Actually I don't think this has anything to do with the soap version that jax-ws uses.
    In some 10.2 versions of the Determination Server a fault was being incorrectly returned as "SOAP-ENVClient" instead of "SOAP-ENV:Client". This is probably causing the error you are seeing.
    This bug was fixed in 10.3 which has just been released as General Availability and you can get it from Oracle E-Delivery (https://edelivery.oracle.com/)
    Also, the fact that you are getting a soap fault means that you are sending wrong information to the determinations server. I suggest using a tool like tcpmon to trap the request and response so you can see what the error is.

  • Multiple versions of an application on one Forms Server

    Is it possible to have multiple versions of an application available via one Forms Server?
    We have a DEV, TEST and PROD version of an application and we would like to have the versions seperate on one Forms Server.
    Would this be possible using any other Oracle tools (Portal)?
    Thanks for your help.

    Yes, all you have to do is create a batch file which sets the env variables you want and also starts up the forms listener on a different port. This way you can have a forms listener on e.g.
    Port 9000 With Forms60_Path - c:\temp
    Port 9001 With Forms60_Path - c:\Production
    Port 9002 With Forms60_Path - c:\test
    That way you will pick up different files as well.
    Regards
    Grant Ronald.

  • Unlimted License Patch fails for multiple versions of  Server Express

    I'm following the directions for installing and licensing two versions of Microfocus Server Express for a PeopleTools 8.52 upgrade. When I get to the point where I apply the Unlimited License Patch (ULP), the application to the first version goes fine, showing a successful "installed" message. After installing the other version of Server Express, I try to apply the ULP again and this time it returns an "uninstalled" message. Eventhough I had COBDIR set to the 2nd installation, the ULP deinstalled the patch for the first installation. I'm doing this as the root user but I have su'ed to root. This worked fine 2 years ago. What am I missing in the environment that prohibits me from installing the ULP for multiple versions of Server Express?

    LD_LIBRARY_PATH

  • Weblogic server not starting in multiple version Environment of JDeveloper

    Hi,
    I first installed Jdev 11.1.1.1 version (now working fine ) and then Jdeveloper 11.1.1.3(problematic now) keeping Jdev 11.1.1.1 aside..in windows xp Operating system.
    I created Middleware Home for Jdev 11.1.1.1 ----> D:/Oracle/Middleware1 and for 11.1.1.3 ------> D:/Oracle/Middleware2. There is also a folder structure C:/Oracle/Middleware containing some files in C: drive.
    On starting weblogic server in 11.1.1.3 ,it shows the following error.The Class path for weblogic server should be start with D: drive and not C: drive.
    Please tell me how to change the class path to refer the correct weblogic server.
    Additional Detail:
    The Environmental variable named CLASSPATH has value "D:\product\10.1.3.1\OracleAS_1\jdk\bin;D:\product\10.1.3.1\OracleAS_1\ant\bin;C:\Oracle11gDB\product\11.2.0\dbhome_1\bin;c:\windows\system32;D:\product\10.1.3.1\OracleAS_1\MOBILE\sdk\bin"
    and other variable PATH has value D:\product\10.1.3.1\OracleAS_1\MOBILE\Sdk\bin\OLITE40.JAR;
    LOG FILE:
    *** Using port 7101 ***
    "C:\Documents and Settings\navinkumark\Application Data\JDeveloper\system11.1.1.3.37.56.60\DefaultDomain\bin\startWebLogic.cmd"
    [waiting for the server to complete its initialization...]
    The system cannot find the path specified.
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
    WLS Start Mode=Development
    CLASSPATH=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\oracle_common\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;D:\product\10.1.3.1\OracleAS_1\MOBILE\Sdk\bin\OLITE40.JAR;_
    PATH=D:\product\10.1.3.1\OracleAS_1\jdk\bin;D:\product\10.1.3.1\OracleAS_1\ant\bin;C:\Oracle11gDB\product\11.2.0\dbhome_1\bin;c:\windows\system32;D:\product\10.1.3.1\OracleAS_1\MOBILE\sdk\bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\oracle_common\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1 -Doracle.server.config.dir=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.security.jps.config=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\oracle_common\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\oracle_common\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\DOCUME~1\NAVINK~1\APPLIC~1\JDEVEL~1\SYSTEM~1.60\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= weblogic.Server
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    java.lang.NoClassDefFoundError: weblogic/Server
    Caused by: java.lang.ClassNotFoundException: weblogic.Server
         at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    Could not find the main class: weblogic.Server. Program will exit.
    Exception in thread "main" Process exited.
    Please help me ,
    Thanks in Advance..
    Regards,
    Navin

    Hi Timo ,Thank you very much..Its working..
    I renamed the folder name system11.1.1.3.37.56.60 to something and the restart the JDev ,it automatically created that folder and ask for to migrate from a previous version ,answered no ..
    Its works now..
    Timo ur Great..

  • Solaris 11 IPS:  How do you post multiple versions of the same package?

    How do you post multiple versions of the same software package on a single IPS instance(port)? Oracle was able to do it here with versions 151 and 175 of S11:
    http://pkg.oracle.com/solaris/release/
    Unfortunately, based on my searches, no where in the documentation (http://www.oracle.com/technetwork/server-storage/solaris11/technologies/ips-323421.html) does it explain to the development community how this is done. The best I can do is create pkg repo instances on different ports to host each different software version.
    We are trying to deploy an IPS repository for our drivers and utilities that our customers can link to and pull updates from. We have been able to post a software package to the repository using the command:
    pkgsend publish -s http://localhost:1234 -d ./ Appv1.p5m
    This posts the package on the IPS repository instance at port 1234 on the server. However, we would like to post multiple versions of the package on the server at the same URL. Why the same URL? So that our customers and end-users need only point to a single URL to pull down our software rather than having to add a new URL to the publisher list each time we have an update. We want at least 5 of the previous software versions to be available on the server. Posting each version of the application or driver on a different IPS instance on a different port will require customers to add multiple URLs to their publisher list and they also will not be able to initiate remote scans for updates.
    Has anybody been able to do this? Is any documentation forthcoming?
    Edited by: user13489824 on Jun 25, 2012 10:17 AM

    dhduvall: Thanks for your response. Yes, one would think that as long as the version numbers are different, you should be able to accumulate multiple versions of a package in a repository. It looks like Oracle has done it in their S11 repository unfortunately, as far as I know, they have not shared the steps on how to do this. I would like to publish two versions of the same package. I.E. two different manifests with two different fmri.pkg version strings and two different binaries.
    If I publish one package after another like this:
    pkgsend publish -s http://localhost:1234 Appv1.p5m
    pkgsend publish -s http://localhost:1234 Appv2.p5m
    Then only the second package shows up in the repository, as if it over-wrote the first one.
    Running pkgsend with two manifest, like this:
    pkgsend publish -s http://localhost:1234 Appv1.p5m Appv2.p5m
    Will cause pkgsend to combine the packages and manifests as if they were a single package... not what I am trying to do.
    Both approaches are complete without errors but neither achieves what I am trying to do.
    alan.pae: Thank you. Unfortunately, the link didn't really help. I've read Oracle's white papers and IPS developer guide so I'm familiar with the topics covered.
    Lex: Yes, I know. I specified the versions in the pkg.fmri value string.

  • Multiple versions of the same RAW image

    Hi All,
    It's posible to have multiple versions of the same RAW file. Let's say I work my RAW file and make some changes, can those changes become an independent file? I want to be able to go back to the original RAW file without loosing any other version already created.
    Best regards,
    Jose

    Hi Kim,
    May be you can try this and see if this works for you. I am not 100% sure if it will work for you, but worth a try I guess. Create a Test WebDynpro project and try the following steps on this project. If they work  out correctly and serve the purpose for you only then try them on your actual Web Dynpro project.
    1. Create a test Web Dynpro project  say "TestWDProject" with Component say "Comp1" and the default views and windows etc.
    Also create some working application our of this component and Windows using the Context.
    2. Right click the "Comp1" and select Copy.
    3. Right click 'Components" node in the project structure and select "Paste"
    4.This step will try to paste the copy of Comp1 as a new Component.
    5. You can change the Name and Package of the Component.
    6.Similarly you'll get the prompts for views,windows etc.
    7.Once you have copied everything, Just check if everything looks good.
    8.Now you can create a new Application using this new component and the Component Interface View and Deploy it.
    9.Test whether the Application created out of this copy works same as the original component.
    You can also try to create another Web Dynpro project and paste the Comp1 in the Components node of that new project and perform the same steps.
    Again, try with these Test Projects and see if this serves your purpose before applying the steps on actual projects.
    Regards,
    Ajay

  • Multiple versions of the same Web Dynpro application on the same SAP Portal

    I have a single application (local development) and deploy directly to a SAP Portal(NW 7.0) from NWDS Version: 7.0.15
    No problems there, works like a charm.
    But I want to have multiple versions of the same application on one portal. Eg. ill build a version 1.0 for test and deploy this. Then continue to work on version 1.1 deploying this directly on the portal. The two versions should now co-existing under different names and/or packages.
    Please help.

    Hi Kim,
    May be you can try this and see if this works for you. I am not 100% sure if it will work for you, but worth a try I guess. Create a Test WebDynpro project and try the following steps on this project. If they work  out correctly and serve the purpose for you only then try them on your actual Web Dynpro project.
    1. Create a test Web Dynpro project  say "TestWDProject" with Component say "Comp1" and the default views and windows etc.
    Also create some working application our of this component and Windows using the Context.
    2. Right click the "Comp1" and select Copy.
    3. Right click 'Components" node in the project structure and select "Paste"
    4.This step will try to paste the copy of Comp1 as a new Component.
    5. You can change the Name and Package of the Component.
    6.Similarly you'll get the prompts for views,windows etc.
    7.Once you have copied everything, Just check if everything looks good.
    8.Now you can create a new Application using this new component and the Component Interface View and Deploy it.
    9.Test whether the Application created out of this copy works same as the original component.
    You can also try to create another Web Dynpro project and paste the Comp1 in the Components node of that new project and perform the same steps.
    Again, try with these Test Projects and see if this serves your purpose before applying the steps on actual projects.
    Regards,
    Ajay

  • Distributing multiple versions of an app within a single Windows Store app

    The company I work for creates Point Of Sale (POS) software using Software As A Service (SAAS), so we host our clients' databases.  We do not force all of our clients to all be on the same version of our software; i.e. some clients are on version 3,
    others v4, others v5, etc.  As you would expect, the database schema for each of these versions is different, so each of these clients also use a different version of our client-side app.
    We are looking at making a Windows Store app that acts as a light-weight POS app that clients can use to sell their products.  The problem is, we will require having multiple versions of our Windows Store app in production; the version of the app that
    the client uses must correspond to their database version.  We were initially hoping to have our Windows Store app detect which version of the app the client should be using, and then automatically update itself to the correct version, but
    were told on this post that it violates the Windows Store certification criteria, so that's not an option.
    It has been suggested that we put multiple apps into the Store; one for each version of our software. We really don't want to do this though, as when we upgrade a client's database from one version to the next it would require that they uninstall their current
    app and install the newer versions app, causing them to lose all of their custom settings. We would like the updates to remain as transparent to the end users as possible; the store clerk shouldn't need to worry about which version their database is on so
    they know which app to download from the Store.
    As a possible workaround, is it ok for us to package all 3 versions of our app into a single Windows Store app, and then just have the app check at runtime which version it should run?  I assume that this is alright, since we will not be downloading
    any other code or installing any software/apps, as was the case with our original solution that violates the certification criteria.  Essentially we would just have 3 different classes and determine at run-time which classes code we should run. 
    I know that this solution isn't ideal, as it means our app will be 3 times larger than it needs to be, and that an update to any one of the 3 versions of our software will require an update to the Store app (so potentially users may download a new version
    of the Store app, even though it doesn't have any changes for the particular code version (i.e. class) that they will use), but it's one of the best alternatives we have come up with.  I just want to check that this solution doesn't also violate any certification
    criteria before we go down this road.
    If this is not allowed then our only other alternative might be to go with sideloading (as
    I discuss on this thread) and avoid using the Windows Store all together, but we would prefer to use the Store if possible as it eliminates a lot of overhead that we would have to deal with if we use sideloading.
    Any insights or suggestions that you can give are appreciated. Thanks!
    - Dan - "Can't never could do anything"

    Hey Mr_bigworlds, thanks for the reply.  The moderator on this post actually told me that this
    would be a better forum for my inquiries.  I agree that there may be another forum better suited for this question (there are so many that I don't know about), but since this relates to Windows Store certification criteria, I don't think the Windows Desktop
    Development forums are the place for it.
    - Dan - "Can't never could do anything"

  • How to manage multiple version of PLSQL application in database?

    Hi all,
    What are the recommended approaches for managing multiple version of plsql program in a single database?
    We can't afford to have different db instance for different version due to server resource.
    We need to keep different version so that easier to support our users who are using different version of our application.
    Please advise.
    Regards,
    Jap.

    Hi Guido,
    Yes, I thought of that as well. If really so, then schema name will have to be different.
    Anyway, just exploring if there's any other possibilities.
    Regards,
    Jap.

  • How to determine the JDK version required to use a jar?

    Hi all.
    I am using a hosted server that uses JDK 1.4.2 and I cannot upgrade the VM. I have been finding it extremely difficult to install web applications on this server since I find that after installing the app, the web server complains the bytecode used in the jar is newer than the VM can understand (or it complains that the app uses JEE servlet or JSP methods it cannot find).
    To compound the problem, only about 25% of the sites I've visited that provide jars for download mention the minumum JDK version required to use them. (Some do not mention any system requirements at all besides 'requires Java and a Java application server').
    Do any of you know of any tools that can analyze a jar and determine the bytecode version it uses?
    (Another helpful tool would be one that can determine the minimum JEE APIs required to run a web app..., but that's probably wishful thinking :)).
    Thanks for your help.
    Michael N. Christoff

    The major/minor version of the class file is the way to go.
    Also, it's not necessary to write a separate program to get to those. javap prints them out when being passed the -v flag.
    Note, however that "JDK version" is not a correct term, as I can create 1.4-compatible class files with a Java 6 JDK (by passing the -target flag to javac). Those won't look any different than .class files written with a 1.4 JDK.

  • In windows how do we install and activite multiple versions of tuxedo at the same time ?

    Hi All,
    In windows how do we install and activate multiple versions of tuxedo at the same time ?
    Advance wishes

    You can run different versions of Tuxedo on the same server, as long as they are installed in different directories.
    See PeopleTools 8.53 installation manual Task 3-1: Installing Oracle Tuxedo
    You can install Oracle Tuxedo once for each release on a machine, regardless of the number of PeopleSoft
    applications or databases the server supports. For example, if you are a PeopleSoft 9.1 customer and have
    Oracle Tuxedo 6.5 installed, you may install Oracle Tuxedo 6.5 and Oracle Tuxedo 11gR1 on the same
    machine in separate directories. For example:
    On Windows, you may install into C:\oracle\tuxedo11gR1_VS2010 and C:\tux65.
    On UNIX, you may install into /home/oracle/tuxedo11gR1 and /prod/tuxedo/6.5.
    E-TUX: Can Multiple Versions of Tuxedo Coexist on One Physical UNIX or Linux Server? (Doc ID 607828.1)

  • Handling source files for multiple versions

    Ok, I've looked around on the web and multiple discussions and have yet to find an answer. We currently have two authors working on the same help project that we have handled relatively successfully under RoboSource. Our development environment has changed so that we need to be able to support multiple versions of the help at once ie- release branch vs development branch that we want documented but it is not yet slated to be in the release.
    I've looked at the help for RoboSource and there is an idea of branching but not much help on how this is done or if it really maintains two sets of the files, etc. I've also seen some postings on the forum for this that have gone unanswered. Makes me suspect that perhaps RoboSource doesn't really support multiple versions of help source files. I would be happy to admit that I'm wrong here.
    Another option to solve our challenge is by committing our source files to the development source system, SVN. I've noticed some threads discussing this. I'm unsure from reading these posts if RoboHelp alerts you when you are about to modify a file, such fpj or hhk, that is being used by someone else like RoboSource does. Since we still have two authors playing in the same help project it would be most efficient if it would notify us before letting us write over one another's work.
    Can anyone shed some light on:
    1) does RoboSource really support multiple versions of the help source files and how it is done?
    2) does RoboHelp notice when a file is locked in SVN and notify the other author to keep hands off until it is committed again?
    3) is there somewhere better for me to research this?
    Thanks you for any assistance you can provide,
    Nita

    We're using RSC 3.1 with RH 8 and with RH X5, and we've found that this is actually a two-step process:
    Branching is the method for copying a snapshot of a folder (to establish two branches of the same source).
    Reconciling (AKA forward/back patching) is the method for synchronizing edits between branches (or not, as the case may be).
    For example, a "V12.3" branch of the "main" source has been prepared for one customer's specific needs. All edits to "main" will be forward patched to "V12.3," but edits to specific areas of "V12.3" will not be back patched to "main."
    Tim, my boss, prepared the tutorials below, as much for himself as for us, and I have only stripped the screenshots to protect our intellectual property. Note also that we reference two publish locations, one for internal reviewing, and one for Release Engineering to include in our nightly product builds. Your environment might only have a single publish destination. Note also that the output files are never added to RSC.
    Pay special attention to your folder naming process before you start, by anticipating any potential future branching needs. Folder renaming after the fact can be problematic in RH and RSC.
    Good luck,
    Leon
    ===================================
    Branching Projects in RoboSource 3.1
    Since the Help for RoboSource and Robohelp lack a proper explanation for branching and updating configuration files to support proper branching, this document has been created to assist in creating future branches.
    Creating New Local Directories
    Individuals must create new local path directories on their systems. We use the following conventions:
              Ex. C:\902_imsmerge\projects (source folder)
              Ex. C:\902_imsgenerate\mergedProjects (output folder)
    Create New Server Directories
    New server directories need to be created in two locations for holding the output files.
    One is for the Robohelp output that gets put in the nightly .war file and checked into Perforce.
    The other is in the wwwroot of our IIS server for our doc web site.
    They are defined as follows:
    \\docsql01\Documentation\RoboHelp\9.0.3\imsgenerate
    \\docsql01\Inetpub\wwwroot\help_sys\9.0.3
    Create new directories with the correct branch number.
    Using RoboSource View Manager to Create a Branch
    You use the View Manager to create a new branch. In RoboSource 3.1, a branch is just a different type of view.
    Assume the version_903 branch has already been created. To create a new branch, click the Create button and name the new branch (version_910), leaving a blank root folder.
    Click on Set Root to define the root folder for the new branch.
    Select the root for the branch and click OK.
    Select the view (branch) and click Properties. In the Properties window, select Branch as the Type, then click Close.
    In the View Manager, check the check box to enable the view.
    Setting the Local Path for the New Branch
    Select the new branch and right-click.
    Type in or browse to the correct local path, check the Apply Recursively box, click Apply. Close the Properties window.
    Editing .xpj Files
    The .xpj files in the new branch need to be edited to point to the new branch. THIS IS VERY IMPORTANT. IF NOT DONE ROBOHELP WILL CHECK IN CHANGES TO BOTH THE BRANCH AND THE ROOT.
    One line in each project’s .xpj needs to change. See below.
    This value must match the branch the project lives in. In our above new branch example this would be changes to %version_910.
    In a merged project, you can change all these at once with the FAR tool.
    Edit the .ssl and .sss files
    These files need to be edited to redefine the generating and publishing paths. Note that this can also be accomplished with the FAR tool, or by having each writer do it through the GUI.
    ssl Files
    The .ssl files contain the data for the generate path. Although there might be seven .ssl files for each project, you only need to edit the ones for your Primary Layout and one or two others that you might also use.
    Make sure the generate path is defined correctly.
    sss Files
    The .sss file defines the publishing paths. This edit can also be done through the GUI if necessary.
    ====================================
    Forward and Back Patching in RoboSource
    This document describes the procedure of forward or back patching files (.htm or .gif) between branches in the RoboSource system. The RoboSource product uses a feature called Reconcile Changes to accomplish patching between branches.
    Example Scenario
    Throughout this document we will use a real life example from the refwindows project.
    We have edited the version 9.0.3 security_master_folder.htm file in RoboHelp.
    Now, we need to backpatch it to version 9.0.2.
    Selecting Folders or Files to Reconcile
    You can select either:
    A single file for reconciliation
    The source folder, or
    The destination folder
    If you have just one file to reconcile, you will probably want to use the single file method. If you have several files to reconcile, you will need to use the folder method.
    Working from the Source Folder
    Select the source folder (folder that contains the updated file) in source control. In our case, %version_903/refwindows.
    Select Reconcile Changes … from the Action menu. This opens the Reconcile window.
    Select the appropriate option in the Reconcile window.
    In our example we select the first option to reconcile from %version_903 because that is where our updated file is. Make sure the correct project is selected in the drop-down list. ($/version_902/refwindows).
    Other Options
    Reconcile changes made in another branch *into %verison_903/refwindows. This is the option you would use if you have an updated file in another branch that you want to put in 903.
    Reconcile changes made locally (in c:\903_imsmerge\projects\refwindows) and %version_903/refwindows. We would most likely never use this option.
    Reconcile changes made in another database *into* this database. Do not use.
    None of the above, let me select what to Reconcile. This one sounds like it would be a good option, but it gets even more complicated.
    Wildcard Filter. Use this to display only certain file types. For example, *.htm;*.gif;*.jpg would filter on those file types.
    Click OK to open the Difference Reconciliator window.
    Notice that this window shows all files in the project that have differences such as the .ssl and .xpj files.
    IMPORTANT: NEVER reconcile these files, they are supposed to be different.
    You can prevent these files from displaying by using the Wildcard Filter discussed above.
    Select the appropriate file (security_master_folder.htm). This window will allow you to replace the file in the version_902 project unfortunately, it will also allow you to replace the updated file with the older one. Be Careful Here.
    You can also View Differences from this window by clicking the View Differences link.
    Click the Replace button in the $/version_902 pane.
    You will get a confirmation dialog. Before clicking OK, take the time to read the question. This is your opportunity to catch potential mistakes!
    You will then get the Reconcile Checkout dialog.
    Be sure Perform the action directly on the Server is checked, click OK.
    You see that the Difference Reconciliator window now indicates No changes to merge from %version_903/rewindows/security_master_folder.htm in the $version_902 pane.
    Close the window.
    Check the Destination Folder
    In the source control window go to the destination branch and check the project. You can see in this shot that the security_master_folder.htm file now shows the date it was replaced, and that the server version is now different from your local version.
    Working from the Destination Folder
    If you had chosen the destination folder and select Reconcile Changes, the same window would have opened but with different options.
    Here you would have selected the second option to reconcile into $/version_902.
    You can do it either way, just pay careful attention to the options. The rest of the process is the same.

  • Workflow multiple versions in production

    Hi Experts,
    when i transport my work flow from development to production
    multiple versions are getting created.
    e.g
    in development i have version 0001
    and production also have version 001
    i did some changes in development in version 0001
    now i transported it to production
    then in production new version is getting created. version 0002
    I did check the SAP help which says
    If a workflow definition is transported into another system,
    only the active version is transported.
    If the workflow definition exists in the target system with the same
    version number,  it is overwritten by the transported version if it has
    no workflows running. Otherwise, the transported workflow definition
    is saved with a free version number. The transported workflow
    definition becomes the active workflow definition in the target system
    but i checked the production server and work flow is not running. still multiple versions are getting created.
    any clue experts
    Regards,
    Umesh Chaudhari.

    Hi Umesh,
    Yes in your scenario you would get a new version created as an instance has already been started using the older version.  This state of affairs used to worry me from a QA perspective as well, but I have seen it now in many sites - both ones where I have built the workflows and ones where I have not - and I can state pretty conclusively that from an operational perspective it is not an issue.
    You could generate a new version in your DEV system whenever you transport, but I would not advise this as in this case it is possible to get your versions out of synch and actually deprecate your changes.  This is not only poor but proved very difficult to analyse (for my small brain anyway) at the site where this was attempted.
    In this case I am firmly of the opinion that I will let the transport system manage the versions in my production system.
    Kind Regards
    Gareth

  • Multiple versions of help - Are areas the answer?

    I have a scenario where we need to be able to have multiple products with multiple versions of that product's help file being published to RoboHelp Server. We are using RoboHelp 8 to publish to RoboHelp Server 8. I am happy with the concept of areas but do not want to have to get the developers to change the path to a new area each time there is a new product version. I want it to be seemless from the application. I am assuming that this would mean always publishing to the same area in which case I can not have multiple versions.
    For example ProductA could have Version1 and Version2. By defining areas called PRODAV1 and PRODAV2 you could change the SSL properties in the project to point to the relevant area. However the server path would need to change to point to either the PRODAV1 or PRODAV2 area.
    Has anyone else already done this and therefore has some advice to offer?
    Read the RoboColum(n).

    Hi Colum
    Colum McAndrew wrote:
    ...do not want to have to get the developers to change the path to a new area each time there is a new product version....
    It would seem to me that this would be a routine thing for developers. To code new help calls with new versions of the product.
    I'm wondering if perhaps you could ease some of that by including a version number in the path. Bear in mind that I don't use RoboHelp Server, so maybe I'm tilting at windmills a bit here.
    I was thinking if you published currently to \\server\product\startpage.htm that maybe you could change things so that you instead published to \\server\productA\startpage.htm. Then when productB comes along the path changes slightly to \\server\productB\startpage.htm.
    That way everything would be in the same server, just in different folders. From the developer standpoint, they would only need to worry with coding a call to the correct product version folder.
    Just thinking out loud a bit... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

Maybe you are looking for