Re: issue with VO substitution

Hi All,
I ve downloaded the right patch. I successfully ran the tutorial pages and also ran the HRMS self service pages from jdeveloper. I am trying to do the VO substitution and check it from jdeveloper. So i added the following "–Djbo.project=OAProject3" to the java option in the project settings. But when i run the page I am getting the following error.
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\Jdeveloper\jdevbin\jdk\bin\javaw.exe -client -classpath C:\Jdeveloper\jdevbin\j2ee\home\oc4j.jar;C:\Jdeveloper\jdevbin\jdev\lib\jdev-oc4j.jar -Xbootclasspath/p:C:\Jdeveloper\jdevbin\jdev\appslibrt\ojdbc14.jar;C:\Jdeveloper\jdevbin\jdev\appslibrt\nls_charset12.zip -DFND_JDBC_STMT_CACHE_SIZE=200 -DCACHENODBINIT=true -DRUN_FROM_JDEV=true -mx256m –Djbo.project=OAProject3 -Xverify:none -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 com.evermind.server.OC4JServer -config C:\Jdeveloper\jdevhome\jdev\system9.0.3.5.1453\oc4j-config\server.xml
[waiting for the server to complete its initialization...]
java.lang.NoClassDefFoundError: –Djbo/project=OAProject3
Exception in thread "main"
Process exited with exit code 1.
Can anybody plz look into this and let me know if any thing is wrong here. I checked it in the forum for similar issues but could not find solutions.
Thanks,
Sree.

Hi Sudhakar,
Thanks for the reply..
Yes. I get 0 errors when i rebuild my project. and also i ve done the substitution. Below are the steps i followed.
1. Got all relevant files from unix box.
2. created a custom package fro my bc4j's.
3. created a VO with Extends property set ti the seed VO i wish to extend.
4. Created the substitution.
Also I could see the substitution in the .jpx file.
<?xml version="1.0" encoding='windows-1252'?>
<!DOCTYPE JboProject SYSTEM "jbo_03_01.dtd">
<JboProject
Name="OAProject3"
SeparateXMLFiles="true"
PackageName="" >
<DesignTime>
<Attr Name="_version" Value="9.0.3.14.00" />
<Attr Name="_jprName" Value="OAProject3.jpr" />
<Attr Name="_ejbPackage" Value="false" />
<Attr Name="_NamedConnection" Value="VOND" />
</DesignTime>
<Containee
Name="server"
FullName="oracle.apps.ap.oie.history.server.server"
ObjectType="JboPackage" >
</Containee>
<Containee
Name="server"
FullName="xxvon.oracle.apps.ap.oie.history.server.server"
ObjectType="JboPackage" >
</Containee>
<Substitutes>
<Substitute OldName ="oracle.apps.ap.oie.history.server.HistoryReportsVO" NewName ="xxvon.oracle.apps.ap.oie.history.server.xxvonHistoryReportsVO" />
</Substitutes>
</JboProject>
Thanks,
Sree

Similar Messages

  • Issue with activated substitution role disappearing

    Hello,
    We have an example of a user that is experiencing problems accessing her substitution role. Her approver is off on long term sick, hence, her substitution role has been activated in 'Maintain Substitutions' in the ERP portal to enable her to authorise purchase orders on behalf of her approver. However, the drop down menu that usually appears when the substitutor is activated does not appear in the universal worklist. Therefore, this means that the user cannot access/view any purchase orders for approval delaying payment to vendors.
    The delegator has deleted and re-installed the substitute in 'Maintain Substitutes' but has failed to do anything. I have checked the users roles and they are all up to date.
    The only inconsistancy I can see is in the users universal worklist connection status. Comparing this to another users universal worklist connection status (that is not experiencing any problems with their substitutions) highlights a difference in message. There is an error message stating AdHocSystem/AdHocWorkflowConnector/Failure/ActionFailed. Any suggestions?

    Hi Sarah
    Most probably the issue is occuring due to an inconsistency or problem with the user which is receiving this error. As you mentioned, other users are perfectly able to access the popup to maintain substitutes without any error in the "Display Connection Status" popup and the same are able to see the combo to select a possible user to substitute.
    So the reason for the portal not to show the combo to select the user is that from substitution perspective, the connection to all the systems registered within UWL need to be working. As for this affected user the AdHocWorkflowConnector is failing, the combo is not showing.
    Maybe you could try checking the latest trace messages (from the default trace file) which are written right after the user entered the UWL application and check whether this would help on finding what the problem with this user would be.
    Also other thing which you could try checking is regarding how this problematic user is maintained in Identity Management. Another prerequisite for substitution is that the users should have both a first name and last name in the respective fields. Check about the possibility of this user being set in disagreement with this.
    Hope this helps
    Best regards
    Armando Zaro

  • Issue with FI substitution in Miro

    Hi Friends,
    I have a substitution created in FI. According to substitution, if cost center entered in document is 'xyz', then it will substitute tax code from x1 to x2. It is working fine for any FI document posted in FI (like FB01 and so on)
    I am expecting this should work fine with MIRO postings also.
    (X1 is input tax and X2 is irrecoverable tax)
    But when I try to post a transaction MIRO with this cost center and tax code X1, it is not substitute to X2 and it is giving error as follows:
    Tax statement item missing for tax code X2
    Message no. FF805
    Diagnosis
    No tax item exists for tax code X2 in a G/L account item. A possible cause is an incorrect transfer of parameters by the application to the Accounting interface.
    Procedure
    Enter an OSS message.
    Please could any one help me?
    Thanks and Regards,
    Krishna.

    Hi,
    If it is working fine for FB01 document type XYZ,then it should work for MIRO also.
    Please check the FI document type which is generating from MIRO.
    I guess the document type from MIRO is not XYZ.
    Thats why it is not substituting the Tax value.
    Regards
    jabeen

  • Issue with Variable Substitution

    Hi,
    We have a scenario where we need to use the data from Payload for further processcing of the messeges.The payload looks like the one given below.
    <?xml version="1.0" encoding="utf-8" ?>
    - <ns1:MT_NOTIFICATION xmlns:ns1="http://WM_ERRHAND"   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    - <PROXYRESPONSE>
      <STATUS>YES</STATUS>
      <NAMESPACE>WM_INVOICE</NAMESPACE>
      <INTERFACENAME>MI_INVOICE_MOORE_ACK_IN</INTERFACENAME>
      <PROXYNAME>ZXIII_MI_INVOICE_MOORE_ACK_IN</PROXYNAME>
      </PROXYRESPONSE>
      </ns1:MT_NOTIFICATION>
    In adapter, for variable substitution we have specified as below:
    payload:MT_NOTIFICATION,1,PROXYRESPONSE,1,NAMESPACE,1
    but getting an error "Message processing failed: Error during variable substitution: java.text.ParseException: Variable 'namespace' not found in variable substitution table"
    Is the variable that we have declared is right or is there anything we have missed out. Any helpful answers will be rewarded
    Thanks and regards,
    Ram.

    Hi Ram,
    The substitution looks fine.
    Did you read this,
    <i>To disable the check the adapter performs for the element data, set the Disable Security Checks indicator.
    Otherwise, the adapter checks whether the element data contains characters that could lead to security risks in the file system environment. The check includes the characters “/“, “\“, and “..“.</i>
    Try seleting this option and checking the same.
    Regards,
    Bhavesh

  • Issue with minor substitution in sql

    I have spend a lot of time trying to get this to work but no joy.
    I am using sql developer and the db version is 10.2.0.5
    Your help and contribution will be greatly appreciated.
    It is a long sql and I am just pasting the FROM statement as that seems the problems is coming from there... It was working before I change the bold from scj_moac to crs.crs_moac. The problems seem to be the left join which I dont really understand
    select ..........
    FROM SRS_SCJ scj
    INNER JOIN srs_cqa cqa
    ON cqa.cqa_crsc = scj.scj_crsc
    INNER JOIN( INS_STU
    LEFT JOIN srs_nat
    ON nat_code = stu_natc)
    ON stu_code = scj_stuc
    LEFT JOIN ( ins_spr spr
    LEFT JOIN ( CAM_SAW saw
    LEFT JOIN ins_awd awd
    ON awd.awd_code = saw.awd_code)
    ON saw.spr_code = spr.spr_code
    AND saw.aws_code = 'CONF')
    LEFT JOIN ins_awd awd2
    ON awd2.awd_code = spr.awd_code
    ON spr.spr_code = scj_sprc
    LEFT JOIN ins_moa moa
    ON moa.moa_code = crs.crs_moac
    LEFT JOIN srs_crs crs
    LEFT JOIN ins_dpt dpt
    ON dpt.dpt_code = crs.crs_dptc
    ON crs.crs_code = scj.scj_crsc
    INNER JOIN srs_sta sta
    ON sta.sta_code = scj.scj_stac
    The error is:
    ORA-00904: "CRS"."CRS_MOAC": invalid identifier
    00904. 00000 - "%s: invalid identifier"
    *Cause:   
    *Action:
    Error at Line: 44 Column: 20

    Hi,
    The join criteria is referencing table alias "prior to its " definition which is CRS.
    Example...
    with t
    (select 'A' x from dual)
    , t1 as
    (select 'B' x from dual)
    , t2 as
    (select 'C' x from dual)
    select * from a
    left outer join b
    on a.x = c.x
    left outer join c
    on b.x = c.x
    Error at Command Line:2 Column:1
    Error report:
    SQL Error: ORA-00904: : invalid identifier
    00904. 00000 -  "%s: invalid identifier"However, if you rearrange the "order of tables and join predicates" such that definition of alias is prior to its reference, it'll work fine.
    vr

  • Issues with substitution

    Hi Gurus,
    Our substitution does not work even though all necessary pre-steps were done, such as importing the substitutions, bounce. But the original VO is still being used.
    Are there any issues with the substitution mechanism.
    Thanks for your advise in advance.

    Hi Gurus,
    Our substitution does not work even though all necessary pre-steps were done, such as importing the substitutions, bounce. But the original VO is still being used.
    Are there any issues with the substitution mechanism.
    Thanks for your advise in advance.

  • Issue with Substitution in UWL

    Hi Friends,
    I have a problem with the substitution rules within the EP7.0 (our back end system is ECC6.0).
    I have created a substitution rule and have set it active.
    When I have a look later on to the management of substitution rules, i always get an error message: "Problems reported (repairable)" --> "Substitution rule is not defined in the system" . When I push "retry" the substitution rule is successfully registered again.
    But the next time when I have a look onto it, i get the same error message.
    What could be the issue. Please advice.
    Regards,

    Hi,
    Check the below link,
    1) [Substitution|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/707439da-ead9-2910-5c97-af6ca0b6fbb1]
    2) [User Substitution Utility |https://wiki.sdn.sap.com/wiki/x/0j0 ]
    Regards,
    Surjith

  • Issue with substitution variable with @MDSHIFT in BR in Calc Manager

    Hi Experts,
    We have a BR in EAS which is working fine.
    and exported to Calcmanager, now while validation it is giving error "@BaseScenario" is not found.
    the code is
    @MDSHIFT("LFLSalesIncVAT_GBP_C_DHP"->&BaseScenario->"Final"->"CD_FinalPlanPL",-1,"Year",,1,"Period",);
    if i hard code it like @MDSHIFT("LFLSalesIncVAT_GBP_C_DHP"->"P7PP"->"Final"->"CD_FinalPlanPL",-1,"Year",,1,"Period",); working fine.
    is there any limitation with calc manger and substitution variables?
    Thanks
    GP

    There seems to be many issues with validations in calc manager, does the rule run if you dont validate.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • UWL Issue with Substitution

    Hi,
    Here's a detail description of issue we are facing with UWL substitution.
    1. When  User A assigns User B on his behalf, User B is only able to see a few items and not all items. Ideally the expectation is that the User B should be able to see all of User A.
    2. Refresh issue: The refresh isn't working properly. When user process a workitem, sometimes the task remian in the UWL and clears the UWL after a refresh. We have tried to set the refresh timing, but it created another issue where the user is scrolling to some 1000th entry, refresh occurs and it goes back to the first tab.
    Just to update, we have tried substitution at both front end and backend, still the issue persists.
    Any inputs, greatly appreciated.
    Thanks,
    SV

    Hi SV,
    Are there any roles mention in System Admin -> System Configuration -> UWL Admin
    Check in system register whether you have any User role defined for the registered system.
    Hope this will be helpful.
    Thanks
    Arun

  • [SOLVED]Issue with Postfix sending to external mail addresses

    I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
    I get the error:
    550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
    Here is what the logs say:
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
    May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
    May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
    main.cf
    # Global Postfix configuration file. This file lists only a subset
    # of all parameters. For the syntax, and for a complete parameter
    # list, see the postconf(5) manual page (command: "man 5 postconf").
    # For common configuration examples, see BASIC_CONFIGURATION_README
    # and STANDARD_CONFIGURATION_README. To find these documents, use
    # the command "postconf html_directory readme_directory", or go to
    # http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
    # For best results, change no more than 2-3 parameters at a time,
    # and test if Postfix still works after every change.
    # SOFT BOUNCE
    # The soft_bounce parameter provides a limited safety net for
    # testing. When soft_bounce is enabled, mail will remain queued that
    # would otherwise bounce. This parameter disables locally-generated
    # bounces, and prevents the SMTP server from rejecting mail permanently
    # (by changing 5xx replies into 4xx replies). However, soft_bounce
    # is no cure for address rewriting mistakes or mail routing mistakes.
    #soft_bounce = no
    # LOCAL PATHNAME INFORMATION
    # The queue_directory specifies the location of the Postfix queue.
    # This is also the root directory of Postfix daemons that run chrooted.
    # See the files in examples/chroot-setup for setting up Postfix chroot
    # environments on different UNIX systems.
    queue_directory = /var/spool/postfix
    # The command_directory parameter specifies the location of all
    # postXXX commands.
    command_directory = /usr/bin
    # The daemon_directory parameter specifies the location of all Postfix
    # daemon programs (i.e. programs listed in the master.cf file). This
    # directory must be owned by root.
    daemon_directory = /usr/lib/postfix
    # The data_directory parameter specifies the location of Postfix-writable
    # data files (caches, random numbers). This directory must be owned
    # by the mail_owner account (see below).
    data_directory = /var/lib/postfix
    # QUEUE AND PROCESS OWNERSHIP
    # The mail_owner parameter specifies the owner of the Postfix queue
    # and of most Postfix daemon processes. Specify the name of a user
    # account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
    # AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
    # particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
    # USER.
    mail_owner = postfix
    # The default_privs parameter specifies the default rights used by
    # the local delivery agent for delivery to external file or command.
    # These rights are used in the absence of a recipient user context.
    # DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
    #default_privs = nobody
    # INTERNET HOST AND DOMAIN NAMES
    # The myhostname parameter specifies the internet hostname of this
    # mail system. The default is to use the fully-qualified domain name
    # from gethostname(). $myhostname is used as a default value for many
    # other configuration parameters.
    #myhostname = host.domain.tld
    myhostname = mail.sendingdomain.com
    # The mydomain parameter specifies the local internet domain name.
    # The default is to use $myhostname minus the first component.
    # $mydomain is used as a default value for many other configuration
    # parameters.
    mydomain = www.sendingdomain.com
    # SENDING MAIL
    # The myorigin parameter specifies the domain that locally-posted
    # mail appears to come from. The default is to append $myhostname,
    # which is fine for small sites. If you run a domain with multiple
    # machines, you should (1) change this to $mydomain and (2) set up
    # a domain-wide alias database that aliases each user to
    # [email protected].
    # For the sake of consistency between sender and recipient addresses,
    # myorigin also specifies the default domain name that is appended
    # to recipient addresses that have no @domain part.
    #myorigin = $myhostname
    myorigin = $mydomain
    append_dot_mydomain = no
    # RECEIVING MAIL
    # The inet_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on. By default,
    # the software claims all active interfaces on the machine. The
    # parameter also controls delivery of mail to user@[ip.address].
    # See also the proxy_interfaces parameter, for network addresses that
    # are forwarded to us via a proxy or network address translator.
    # Note: you need to stop/start Postfix when this parameter changes.
    inet_interfaces = all
    #inet_interfaces = loopback-only
    #inet_interfaces = $myhostname
    #inet_interfaces = $myhostname, localhost
    # The proxy_interfaces parameter specifies the network interface
    # addresses that this mail system receives mail on by way of a
    # proxy or network address translation unit. This setting extends
    # the address list specified with the inet_interfaces parameter.
    # You must specify your proxy/NAT addresses when your system is a
    # backup MX host for other domains, otherwise mail delivery loops
    # will happen when the primary MX host is down.
    #proxy_interfaces =
    #proxy_interfaces = 1.2.3.4
    # The mydestination parameter specifies the list of domains that this
    # machine considers itself the final destination for.
    # These domains are routed to the delivery agent specified with the
    # local_transport parameter setting. By default, that is the UNIX
    # compatible delivery agent that lookups all recipients in /etc/passwd
    # and /etc/aliases or their equivalent.
    # The default is $myhostname + localhost.$mydomain. On a mail domain
    # gateway, you should also include $mydomain.
    # Do not specify the names of virtual domains - those domains are
    # specified elsewhere (see VIRTUAL_README).
    # Do not specify the names of domains that this machine is backup MX
    # host for. Specify those names via the relay_domains settings for
    # the SMTP server, or use permit_mx_backup if you are lazy (see
    # STANDARD_CONFIGURATION_README).
    # The local machine is always the final destination for mail addressed
    # to user@[the.net.work.address] of an interface that the mail system
    # receives mail on (see the inet_interfaces parameter).
    # Specify a list of host or domain names, /file/name or type:table
    # patterns, separated by commas and/or whitespace. A /file/name
    # pattern is replaced by its contents; a type:table is matched when
    # a name matches a lookup key (the right-hand side is ignored).
    # Continue long lines by starting the next line with whitespace.
    # See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
    #mydestination = $myhostname, localhost.$mydomain, localhost
    #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
    #mydestination = localhost
    # mail.$mydomain, www.$mydomain, ftp.$mydomain
    # REJECTING MAIL FOR UNKNOWN LOCAL USERS
    # The local_recipient_maps parameter specifies optional lookup tables
    # with all names or addresses of users that are local with respect
    # to $mydestination, $inet_interfaces or $proxy_interfaces.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown local users. This parameter is defined by default.
    # To turn off local recipient checking in the SMTP server, specify
    # local_recipient_maps = (i.e. empty).
    # The default setting assumes that you use the default Postfix local
    # delivery agent for local delivery. You need to update the
    # local_recipient_maps setting if:
    # - You define $mydestination domain recipients in files other than
    # /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
    # For example, you define $mydestination domain recipients in
    # the $virtual_mailbox_maps files.
    # - You redefine the local delivery agent in master.cf.
    # - You redefine the "local_transport" setting in main.cf.
    # - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
    # feature of the Postfix local delivery agent (see local(8)).
    # Details are described in the LOCAL_RECIPIENT_README file.
    # Beware: if the Postfix SMTP server runs chrooted, you probably have
    # to access the passwd file via the proxymap service, in order to
    # overcome chroot restrictions. The alternative, having a copy of
    # the system passwd file in the chroot jail is just not practical.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify a bare username, an @domain.tld
    # wild-card, or specify a [email protected] address.
    #local_recipient_maps = unix:passwd.byname $alias_maps
    local_recipient_maps = proxy:unix:passwd.byname $alias_maps
    #local_recipient_maps =
    # The unknown_local_recipient_reject_code specifies the SMTP server
    # response code when a recipient domain matches $mydestination or
    # ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
    # and the recipient address or address local-part is not found.
    # The default setting is 550 (reject mail) but it is safer to start
    # with 450 (try again later) until you are certain that your
    # local_recipient_maps settings are OK.
    unknown_local_recipient_reject_code = 550
    # TRUST AND RELAY CONTROL
    # The mynetworks parameter specifies the list of "trusted" SMTP
    # clients that have more privileges than "strangers".
    # In particular, "trusted" SMTP clients are allowed to relay mail
    # through Postfix. See the smtpd_recipient_restrictions parameter
    # in postconf(5).
    # You can specify the list of "trusted" network addresses by hand
    # or you can let Postfix do it for you (which is the default).
    # By default (mynetworks_style = subnet), Postfix "trusts" SMTP
    # clients in the same IP subnetworks as the local machine.
    # On Linux, this does works correctly only with interfaces specified
    # with the "ifconfig" command.
    # Specify "mynetworks_style = class" when Postfix should "trust" SMTP
    # clients in the same IP class A/B/C networks as the local machine.
    # Don't do this with a dialup site - it would cause Postfix to "trust"
    # your entire provider's network. Instead, specify an explicit
    # mynetworks list by hand, as described below.
    # Specify "mynetworks_style = host" when Postfix should "trust"
    # only the local machine.
    #mynetworks_style = class
    #mynetworks_style = subnet
    mynetworks_style = host
    # Alternatively, you can specify the mynetworks list by hand, in
    # which case Postfix ignores the mynetworks_style setting.
    # Specify an explicit list of network/netmask patterns, where the
    # mask specifies the number of bits in the network part of a host
    # address.
    # You can also specify the absolute pathname of a pattern file instead
    # of listing the patterns here. Specify type:table for table-based lookups
    # (the value on the table right-hand side is not used).
    #mynetworks = 168.100.189.0/28, 127.0.0.0/8
    #mynetworks = $config_directory/mynetworks
    #mynetworks = hash:/etc/postfix/network_table
    # The relay_domains parameter restricts what destinations this system will
    # relay mail to. See the smtpd_recipient_restrictions description in
    # postconf(5) for detailed information.
    # By default, Postfix relays mail
    # - from "trusted" clients (IP address matches $mynetworks) to any destination,
    # - from "untrusted" clients to destinations that match $relay_domains or
    # subdomains thereof, except addresses with sender-specified routing.
    # The default relay_domains value is $mydestination.
    # In addition to the above, the Postfix SMTP server by default accepts mail
    # that Postfix is final destination for:
    # - destinations that match $inet_interfaces or $proxy_interfaces,
    # - destinations that match $mydestination
    # - destinations that match $virtual_alias_domains,
    # - destinations that match $virtual_mailbox_domains.
    # These destinations do not need to be listed in $relay_domains.
    # Specify a list of hosts or domains, /file/name patterns or type:name
    # lookup tables, separated by commas and/or whitespace. Continue
    # long lines by starting the next line with whitespace. A file name
    # is replaced by its contents; a type:name table is matched when a
    # (parent) domain appears as lookup key.
    # NOTE: Postfix will not automatically forward mail for domains that
    # list this system as their primary or backup MX host. See the
    # permit_mx_backup restriction description in postconf(5).
    relay_domains = $mydestination
    # INTERNET OR INTRANET
    # The relayhost parameter specifies the default host to send mail to
    # when no entry is matched in the optional transport(5) table. When
    # no relayhost is given, mail is routed directly to the destination.
    # On an intranet, specify the organizational domain name. If your
    # internal DNS uses no MX records, specify the name of the intranet
    # gateway host instead.
    # In the case of SMTP, specify a domain, host, host:port, [host]:port,
    # [address] or [address]:port; the form [host] turns off MX lookups.
    # If you're connected via UUCP, see also the default_transport parameter.
    #relayhost = $mydomain
    #relayhost = [gateway.my.domain]
    #relayhost = [mailserver.isp.tld]
    #relayhost = uucphost
    #relayhost = [an.ip.add.ress]
    default_transport = error: Local delivery only!
    # REJECTING UNKNOWN RELAY USERS
    # The relay_recipient_maps parameter specifies optional lookup tables
    # with all addresses in the domains that match $relay_domains.
    # If this parameter is defined, then the SMTP server will reject
    # mail for unknown relay users. This feature is off by default.
    # The right-hand side of the lookup tables is conveniently ignored.
    # In the left-hand side, specify an @domain.tld wild-card, or specify
    # a [email protected] address.
    #relay_recipient_maps = hash:/etc/postfix/relay_recipients
    # INPUT RATE CONTROL
    # The in_flow_delay configuration parameter implements mail input
    # flow control. This feature is turned on by default, although it
    # still needs further development (it's disabled on SCO UNIX due
    # to an SCO bug).
    # A Postfix process will pause for $in_flow_delay seconds before
    # accepting a new message, when the message arrival rate exceeds the
    # message delivery rate. With the default 100 SMTP server process
    # limit, this limits the mail inflow to 100 messages a second more
    # than the number of messages delivered per second.
    # Specify 0 to disable the feature. Valid delays are 0..10.
    #in_flow_delay = 1s
    # ADDRESS REWRITING
    # The ADDRESS_REWRITING_README document gives information about
    # address masquerading or other forms of address rewriting including
    # username->Firstname.Lastname mapping.
    # ADDRESS REDIRECTION (VIRTUAL DOMAIN)
    # The VIRTUAL_README document gives information about the many forms
    # of domain hosting that Postfix supports.
    # "USER HAS MOVED" BOUNCE MESSAGES
    # See the discussion in the ADDRESS_REWRITING_README document.
    # TRANSPORT MAP
    # See the discussion in the ADDRESS_REWRITING_README document.
    # ALIAS DATABASE
    # The alias_maps parameter specifies the list of alias databases used
    # by the local delivery agent. The default list is system dependent.
    # On systems with NIS, the default is to search the local alias
    # database, then the NIS alias database. See aliases(5) for syntax
    # details.
    # If you change the alias database, run "postalias /etc/aliases" (or
    # wherever your system stores the mail alias file), or simply run
    # "newaliases" to build the necessary DBM or DB file.
    # It will take a minute or so before changes become visible. Use
    # "postfix reload" to eliminate the delay.
    #alias_maps = dbm:/etc/aliases
    #alias_maps = hash:/etc/aliases
    #alias_maps = hash:/etc/aliases, nis:mail.aliases
    #alias_maps = netinfo:/aliases
    alias_maps = hash:/etc/postfix/aliases
    # The alias_database parameter specifies the alias database(s) that
    # are built with "newaliases" or "sendmail -bi". This is a separate
    # configuration parameter, because alias_maps (see above) may specify
    # tables that are not necessarily all under control by Postfix.
    #alias_database = dbm:/etc/aliases
    #alias_database = dbm:/etc/mail/aliases
    #alias_database = hash:/etc/aliases
    #alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
    alias_database = $alias_maps
    # ADDRESS EXTENSIONS (e.g., user+foo)
    # The recipient_delimiter parameter specifies the separator between
    # user names and address extensions (user+foo). See canonical(5),
    # local(8), relocated(5) and virtual(5) for the effects this has on
    # aliases, canonical, virtual, relocated and .forward file lookups.
    # Basically, the software tries user+foo and .forward+foo before
    # trying user and .forward.
    #recipient_delimiter = +
    # DELIVERY TO MAILBOX
    # The home_mailbox parameter specifies the optional pathname of a
    # mailbox file relative to a user's home directory. The default
    # mailbox file is /var/spool/mail/user or /var/mail/user. Specify
    # "Maildir/" for qmail-style delivery (the / is required).
    #home_mailbox = Mailbox
    home_mailbox = Maildir/
    # The mail_spool_directory parameter specifies the directory where
    # UNIX-style mailboxes are kept. The default setting depends on the
    # system type.
    #mail_spool_directory = /var/mail
    #mail_spool_directory = /var/spool/mail
    # The mailbox_command parameter specifies the optional external
    # command to use instead of mailbox delivery. The command is run as
    # the recipient with proper HOME, SHELL and LOGNAME environment settings.
    # Exception: delivery for root is done as $default_user.
    # Other environment variables of interest: USER (recipient username),
    # EXTENSION (address extension), DOMAIN (domain part of address),
    # and LOCAL (the address localpart).
    # Unlike other Postfix configuration parameters, the mailbox_command
    # parameter is not subjected to $parameter substitutions. This is to
    # make it easier to specify shell syntax (see example below).
    # Avoid shell meta characters because they will force Postfix to run
    # an expensive shell process. Procmail alone is expensive enough.
    # IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
    # ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
    #mailbox_command = /some/where/procmail
    #mailbox_command = /some/where/procmail -a "$EXTENSION"
    # The mailbox_transport specifies the optional transport in master.cf
    # to use after processing aliases and .forward files. This parameter
    # has precedence over the mailbox_command, fallback_transport and
    # luser_relay parameters.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    # Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
    # listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
    #mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
    # Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
    # subsequent line in master.cf.
    #mailbox_transport = cyrus
    # The fallback_transport specifies the optional transport in master.cf
    # to use for recipients that are not found in the UNIX passwd database.
    # This parameter has precedence over the luser_relay parameter.
    # Specify a string of the form transport:nexthop, where transport is
    # the name of a mail delivery transport defined in master.cf. The
    # :nexthop part is optional. For more details see the sample transport
    # configuration file.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must update the "local_recipient_maps" setting in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #fallback_transport = lmtp:unix:/file/name
    #fallback_transport = cyrus
    #fallback_transport =
    # The luser_relay parameter specifies an optional destination address
    # for unknown recipients. By default, mail for unknown@$mydestination,
    # unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
    # as undeliverable.
    # The following expansions are done on luser_relay: $user (recipient
    # username), $shell (recipient shell), $home (recipient home directory),
    # $recipient (full recipient address), $extension (recipient address
    # extension), $domain (recipient domain), $local (entire recipient
    # localpart), $recipient_delimiter. Specify ${name?value} or
    # ${name:value} to expand value only when $name does (does not) exist.
    # luser_relay works only for the default Postfix local delivery agent.
    # NOTE: if you use this feature for accounts not in the UNIX password
    # file, then you must specify "local_recipient_maps =" (i.e. empty) in
    # the main.cf file, otherwise the SMTP server will reject mail for
    # non-UNIX accounts with "User unknown in local recipient table".
    #luser_relay = [email protected]
    #luser_relay = [email protected]
    #luser_relay = admin+$local
    # JUNK MAIL CONTROLS
    # The controls listed here are only a very small subset. The file
    # SMTPD_ACCESS_README provides an overview.
    # The header_checks parameter specifies an optional table with patterns
    # that each logical message header is matched against, including
    # headers that span multiple physical lines.
    # By default, these patterns also apply to MIME headers and to the
    # headers of attached messages. With older Postfix versions, MIME and
    # attached message headers were treated as body text.
    # For details, see "man header_checks".
    #header_checks = regexp:/etc/postfix/header_checks
    # FAST ETRN SERVICE
    # Postfix maintains per-destination logfiles with information about
    # deferred mail, so that mail can be flushed quickly with the SMTP
    # "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
    # See the ETRN_README document for a detailed description.
    # The fast_flush_domains parameter controls what destinations are
    # eligible for this service. By default, they are all domains that
    # this server is willing to relay mail to.
    #fast_flush_domains = $relay_domains
    # SHOW SOFTWARE VERSION OR NOT
    # The smtpd_banner parameter specifies the text that follows the 220
    # code in the SMTP server's greeting banner. Some people like to see
    # the mail version advertised. By default, Postfix shows no version.
    # You MUST specify $myhostname at the start of the text. That is an
    # RFC requirement. Postfix itself does not care.
    #smtpd_banner = $myhostname ESMTP $mail_name
    #smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
    # PARALLEL DELIVERY TO THE SAME DESTINATION
    # How many parallel deliveries to the same user or domain? With local
    # delivery, it does not make sense to do massively parallel delivery
    # to the same user, because mailbox updates must happen sequentially,
    # and expensive pipelines in .forward files can cause disasters when
    # too many are run at the same time. With SMTP deliveries, 10
    # simultaneous connections to the same domain could be sufficient to
    # raise eyebrows.
    # Each message delivery transport has its XXX_destination_concurrency_limit
    # parameter. The default is $default_destination_concurrency_limit for
    # most delivery transports. For the local delivery agent the default is 2.
    #local_destination_concurrency_limit = 2
    #default_destination_concurrency_limit = 20
    # DEBUGGING CONTROL
    # The debug_peer_level parameter specifies the increment in verbose
    # logging level when an SMTP client or server host name or address
    # matches a pattern in the debug_peer_list parameter.
    debug_peer_level = 2
    # The debug_peer_list parameter specifies an optional list of domain
    # or network patterns, /file/name patterns or type:name tables. When
    # an SMTP client or server host name or address matches a pattern,
    # increase the verbose logging level by the amount specified in the
    # debug_peer_level parameter.
    #debug_peer_list = 127.0.0.1
    #debug_peer_list = some.domain
    # The debugger_command specifies the external command that is executed
    # when a Postfix daemon program is run with the -D option.
    # Use "command .. & sleep 5" so that the debugger can attach before
    # the process marches on. If you use an X-based debugger, be sure to
    # set up your XAUTHORITY environment variable before starting Postfix.
    debugger_command =
    PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
    ddd $daemon_directory/$process_name $process_id & sleep 5
    # If you can't use X, use this to capture the call stack when a
    # daemon crashes. The result is in a file in the configuration
    # directory, and is named after the process name and the process ID.
    # debugger_command =
    # PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
    # echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
    # >$config_directory/$process_name.$process_id.log & sleep 5
    # Another possibility is to run gdb under a detached screen session.
    # To attach to the screen sesssion, su root and run "screen -r
    # <id_string>" where <id_string> uniquely matches one of the detached
    # sessions (from "screen -list").
    # debugger_command =
    # PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
    # -dmS $process_name gdb $daemon_directory/$process_name
    # $process_id & sleep 1
    # INSTALL-TIME CONFIGURATION INFORMATION
    # The following parameters are used when installing a new Postfix version.
    # sendmail_path: The full pathname of the Postfix sendmail command.
    # This is the Sendmail-compatible mail posting interface.
    sendmail_path = /usr/bin/sendmail
    # newaliases_path: The full pathname of the Postfix newaliases command.
    # This is the Sendmail-compatible command to build alias databases.
    newaliases_path = /usr/bin/newaliases
    # mailq_path: The full pathname of the Postfix mailq command. This
    # is the Sendmail-compatible mail queue listing command.
    mailq_path = /usr/bin/mailq
    # setgid_group: The group for mail submission and queue management
    # commands. This must be a group name with a numerical group ID that
    # is not shared with other accounts, not even with the Postfix account.
    setgid_group = postdrop
    # html_directory: The location of the Postfix HTML documentation.
    html_directory = no
    # manpage_directory: The location of the Postfix on-line manual pages.
    manpage_directory = /usr/share/man
    # sample_directory: The location of the Postfix sample configuration files.
    # This parameter is obsolete as of Postfix 2.1.
    sample_directory = /etc/postfix/sample
    # readme_directory: The location of the Postfix README files.
    readme_directory = /usr/share/doc/postfix
    inet_protocols = ipv4
    #virtual_mailbox_domains = sendingdomain.com
    virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
    virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
    virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
    virtual_mailbox_base = /home/vmailer
    virtual_uid_maps = static:5003
    virtual_gid_maps = static:5003
    virtual_minimum_uid = 5003
    virtual_mailbox_limit = 51200000
    Any help would be appreciated. Thank you.
    Last edited by nadman10 (2014-05-14 14:36:10)

    Your main.cf seems redundant.
    For example:
    if you specify:
    virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
    you don't need this:
    alias_maps = hash:/etc/postfix/aliases
    and i think you have a lot of more options you don't need.
    This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
    smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
    biff = no
    # appending .domain is the MUA's job.
    append_dot_mydomain = no
    readme_directory = no
    # TLS parameters
    smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
    smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
    smtpd_use_tls=yes
    smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
    smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
    message_size_limit = 4194304
    virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
    virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
    virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
    virtual_transport = dovecot
    dovecot_destination_recipient_limit = 1
    it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
    as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

  • Issue with setting a default value to a Tabular Form field

    Hi -
    I'm running into an issue setting the default value of a tabular form column. I'm trying to set the default value to the row number (#rownum#). This used to work in previous versions, but now it's returning 0. Is there a was to set this value in the default value attribute of the field with a substitution string?
    Thank you in advance for help!

    Share with us what worked in previous versions.
    Jeff

  • Issue with filling out form fields in Safari?

    Hello,
    Has anyone noticed any issues with filling out form fields (specifically text boxes) in Safari 6.0.2 on Mac OS 10.8.2?  When I attempt to test forms I've created, there is a delay when typing values into text boxes.  Other types of input controls (check boxes, drop down lists, etc.) appear to work fine.  As far as I can tell, this only occurs with Safari 6.0.2 in Mac OS 10.8.2.  Prior versions of Safari do not have this issue, nor does Firefox in the same OS environment.  When I refresh the form, the delay is not as noticeable.  I'm searching the WebKit bug reports as well, but nothing seems to point to this issue.  Any hints would be greatly appreciated.

    From the menu bar, select
    Edit ▹ Substitutions
    and uncheck Text Replacement.

  • Interlacing issue with AME/Premiere CS5?

    Hi,
    I am having some issues with a file that I am trying to conform using AME CS5 from XDCAM-HD mxf wrapped to wmv output that I need to be able to playout of a black magic card to SDI.
    The source file is 25fps PAL
    If I import the mxf directly into AME (without going via Premiere), I can successfully output an interlaced file at 6Mbit CBR using the main profile and it plays out correctly on the monitor I am using to check playback.
    However, I need to remove 2 channels of audio from the hires and overlay a logo. I have done this by importing the file into Premiere, making the necessary changes and exporting it to AME.
    When I do this, if I chose interlaced as my output from AME the resultant file is terrible and movement is extremely jerky. If I change the output to deinterlaced I see an improvement but it is still not as good as the file that has been imported directly to AME without going via Premiere.
    I need to understand (and resolve) what is happening within Premiere that is making a difference to the output file from AME.
    Changing the output format to something other than wmv is not really an option at present.
    I have tried changing the Interpret Footage settings in AME along with various other options. I appreciate that I may not have supplied enough information here for someone to be able to assist but if you let me know what else you need to know I will happily provide it.
    Thanks

    thanks for the clarification and apologies for the misunderstanding. I don't work in the video editing side of the industry so I'm not familiar with a lot of the lingo.
    Unfortunately I have an absolute requirement to either use the prproj (or ideally the FCP xml option) output so that I can substitue the source media in the project and send multiple jobs to AME using an automated process.
    I'm trying to understand what Premiere is doing to the hires file when it exports it that is causing the difference in the resulting output from AME when compared to submitting the hires directly to AME.
    I'm just in the process of setting up a new project that only contains the hires, with no logo added, no settings changed and I am going to run that through AME using the same epr that I used on the direct import of the hires.

  • Issue with substituition

    Hi Experts,
    I  need some information regarding substituition.
    Assume there are 2 levels of approval and A is the Approver for 1st level and A2 is A's subtitute.
    B is the approver at 2nd level and B2 is B's subtitute.
    Suppose if A is going on leave,how make sure that A assign A2 as his subtititute and not someone else?
    I SEARCHED SDN BEFORE POSTING THIS QUESTION, GOT TO KNOW THAT THIS ISSUE CAN BE SOLVED USING SUBTITUITION PROFILE. SINCE I AM WORKING ON WORKFLOW FOR THE FIRST TIME I COULD UNDERSTAND THE SOLUTION PROVIDED IN SDN. I REQUEST YOU YO BE KIND ENOUGH TO GIVE ME DETAILED SOLUTION TO MY ABOVE QUERY.
    Thanks in advance.
    Regards
      Balu

    Hi,
    If i understand correctly, you want to restrict the user that can be substituted, not the tasks that need to get fwded automatically with the Substitution. This has got nothing to do with Substitution Profile.
    This probably needs a custom development. When the user A goes to create a Substitute, in the Search help of the Users, you need to put a restriction to filter the user id selection based on some criteria, for which only A2 is displayed.
    This would take lot of custom development effort. I don't know if it's worth.
    Other idea would be, defaulting the Substitute. Let user A substitute any user ID and this entry goes to the table HRUS_D2.  You can write a small ABAP pgm to monitor this table periodically (scheduled job) for any new entries. When you see an entry in this table, see if that user id is User A and if the Substitute is not A2, change is to User A2 and may be shoot a mail to user A about the change.
    Hope this helps.
    Any other ideas guys....
    Regards,
    venu

  • Font issues with ATM and new O/S install

    I have had to reformat my h/d and now have issues with fonts. I see that I have several different versions of Minion and Myriad installed on my PC, when viewing through both the windows font manager and ATM, yet these same versions are not availble to me when I am in Pagemaker or Word. I suspect it has to do with Multiple Masters but I am unsure how to fix the problem. Any ideas?

    Multiple master fonts can still be happily used with XP, but Vista doesn't support them or ATM (which is needed to use them). (There is apparently a workround to install MM fonts on Vista, but I haven't read much about it.)
    Anyway, have you installed the multiple master fonts? You've listed the OpenType versions but don't say if you've installed the MM versions. If you haven't, you'll get substitution in files originally created with those fonts. If you have, you still may not have created the specific custom instances used in the files, in which case you'll have to use ATM to create those instances.

Maybe you are looking for