Skip to Main Content
Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Status Not under consideration
Created by Marc Zimmermann
Created on Nov 2, 2018

Configurable WebSphere Application Server (WAS) profile path

The build files included in the Curam Server Development Environment (CuramSDEJ) that help manage the deployment of Curam on WebSphere Application Server do not allow an administrator to specify a target profile path for the installation/deployment. However, administrators want/need to have control over where in the file system the profile is stored.

  • Attach files
  • Guest
    Reply
    |
    Feb 25, 2019

    Hi Marc,

    We have evaluated your request and have determined that it cannot be implemented at this time.

    Your request may be resubmitted for consideration after 12 months from the date of decline.

    Thank you for your interest in the Cúram SPM product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Nov 8, 2018

    Hi Marc,

    This functionality is supported by WebSphere but we have not heard previously (up to now) of a requirement to place the profile in some other location outside of the base default WebSphere directory (where our OOTB scripts place it).

    We would need further information on why this is required.
    You mention the following "administrators want/need to have control over where in the file system the profile is stored." Why do they need this and for what environments is this required for by your customer?

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |
    Nov 2, 2018

    Hi Marc,

    Thank you for your enhancement request.
    We require some further analysis to determine whether or not this enhancement can be considered in a future release.
    I will provide another response when our investigation is complete.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team