SLD server and UME configuration

Dear Portal Gurus,
I have configured the UME as ABAP datasource (R/3) with client (001). all the things sld is running and able to create jco connections .
iam not able to create users from user adminstration when the client is 001
when i modify the ume configuration with client as 800 and giving proper username and password after restarting the j2ee server iam able to create users . but the problems iam facing are.
1) SLD is not runnining.
2)Logon page language is changed.
3) All the JCO's are not working.
what are the steps to be taken in j2ee server to modify the ume configuration . and successfull running of sld and logon page.
Regards
prasad

solved by me

Similar Messages

Mail server and DNS configuration

I have an XServe G4 running Mac OS X 10.4 Tiger Server, and I have successfully configured two domains that I purchased from GoDaddy as websites on this XServe. It's behind an Airport Extreme, and I have forwarded a bunch of ports in order to enable FTP, SSH, Web, remote Server Administration, webmail, and I have also forwarded the IMAP and SMTP ports. All of these services work except for email, so I am wondering if there is any special DNS settings that I need to configure in the GoDaddy total dns configuration page. I have the MX record pointed directly to my IP, just like the A record. I also have mail.mydomain.com pointed to the A record's IP (maybe I described that poorly, but I hope it gets the point across). I am able to log into webmail and send email out to other people, but when I try replying back to the email which I sent from webmail, I get a bounced message. I also cannot configure a Mail client, but I think I need to get the accounts at least working first. Can someone provide a list of DNS requirements or server configuration requirements for me to check off in order to make this happen? Does anyone know of any great resources to learn this kind of stuff? I'm kinda new to the server thing.
Thanks!
Paul

postconf -n results:
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
html_directory = no
inet_interfaces = localhost
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = $myhostname,localhost.$mydomain,localhost,rubenkalath.com
mydomain = rubenkalath.com
mydomain_fallback = localhost
myhostname = mail.rubenkalath.com
mynetworks = 127.0.0.0/8
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdtls_certfile = /etc/certificates/Default.crt
smtpdtls_keyfile = /etc/certificates/Default.key
smtpdusetls = no
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains = hash:/etc/postfix/virtual_domains
virtual_transport = lmtp:unix:/var/imap/socket/lmtp
ps U _postfix results:
ps: _postfix: no such user
tail -20 /var/log/mail.log results:
May 15 15:55:27 sincity postfix/cleanup[1257]: 765DC4517A: message-id=<[email protected]>
May 15 15:55:27 sincity postfix/qmgr[1239]: 765DC4517A: from=<[email protected]>, size=881, nrcpt=1 (queue active)
May 15 15:55:27 sincity postfix/smtpd[1254]: disconnect from localhost[127.0.0.1]
May 15 15:55:27 sincity postfix/pipe[1259]: 765DC4517A: to=<[email protected]>, relay=cyrus, delay=0, status=sent (mail.rubenkalath.com)
May 15 15:55:27 sincity postfix/qmgr[1239]: 765DC4517A: removed
May 15 15:58:09 sincity postfix/smtpd[1338]: connect from localhost[127.0.0.1]
May 15 15:58:13 sincity postfix/smtpd[1338]: lost connection after CONNECT from localhost[127.0.0.1]
May 15 15:58:13 sincity postfix/smtpd[1338]: disconnect from localhost[127.0.0.1]
May 15 16:06:09 sincity postfix/postfix-script: refreshing the Postfix mail system
May 15 16:06:09 sincity postfix/master[590]: reload configuration
May 15 16:12:48 sincity postfix/smtpd[1709]: connect from localhost[127.0.0.1]
May 15 16:12:54 sincity postfix/smtpd[1709]: lost connection after CONNECT from localhost[127.0.0.1]
May 15 16:12:54 sincity postfix/smtpd[1709]: disconnect from localhost[127.0.0.1]
May 15 16:28:58 sincity postfix/smtpd[2068]: connect from localhost[127.0.0.1]
May 15 16:28:58 sincity postfix/smtpd[2068]: 1FA354537C: client=localhost[127.0.0.1]
May 15 16:28:58 sincity postfix/cleanup[2071]: 1FA354537C: message-id=<[email protected]>
May 15 16:28:58 sincity postfix/qmgr[1530]: 1FA354537C: from=<[email protected]>, size=776, nrcpt=1 (queue active)
May 15 16:28:58 sincity postfix/smtpd[2068]: disconnect from localhost[127.0.0.1]
May 15 16:29:02 sincity postfix/smtp[2072]: 1FA354537C: to=<[email protected]>, relay=mercury.gatech.edu[130.207.192.26], delay=4, status=sent (250 Ok: queued as 67542CDF86)

WSUS server and client configuration issues

I just inherited WSUS from my predecessor (it was turned off because of a full disk) so I’m still learning how to use it. Turning it back on I changed where updates should come from, they were stored locally and now I’m pulling them down off of the Microsoft
Update location. What I’m seeing is that I have a bunch of computers that WSUS “sees” but are showing “Failed or Needed” status. Unless I visit each machine and manually do the updates this status does not change. Additionally I have some client computers
(Windows 7) that are not showing up as managed by WSUS. If I reading this right I’m running version Update Services 6.2.9200.16384 on Management Console 3.0 Version 6.2 (build 9200) on Windows Server 2012.
How can I force WSUS to automatically update the “Failed and Needed” devices?
How can I get those clients that are not being managed by WSUS to be managed?
Some of the things that I have done so far on the server and clients are:
Create a GPO (see attached for WSUS)
wuauclt
/detectnow
wuauclt /reportnow
wuauclt.exe /detectnow
gpupdate /force after
modifying the GPO
I even ran the SolarWinds WSUS diagnostic (as a non-administrator) and got this as the output:
# Solarwinds® Diagnostic Tool for the WSUS Agent # 1/23/2015
Machine state
User rights: User does not have administrative rights (Administrator rights are not available)
Update service status: Running
Background Intelligent Transfer service status:
Running
OS Version: Windows 8.1 Pro
Windows update agent version:   7.9.9600.17489 (WU Agent is OK)
Windows Update Agent configuration settings
Automatic Update:    Enabled
Options: Automatically download and notify of installation
Use WSUS Server: Not found (There is no such key)
Windows Update Server: Not found (There is no such key)
Windows Update Status Server: Not found (There is no such key)
WSUS URLs are identical: Values are empty
WSUS Server Connectivity -- Connectivity check is impossible
So, my questions are:
What tool do I use to configure the client machine?
How do I get WSUS to update my clients?
Thanks
Sam

Steven,
I'm pretty sure that this is not the right forum to discuss this in but just so we can close this case.
On my computer I ran the command gpupdate /force I
then rebooted my computer to make sure that the group policy would be updated. The first screen shot is from my domain controller and the second is from my computer. As you can see the Domain Controller has the correct settings but the local machine doesn't.
Other parts of the DC GPO settings have worked so I'm somewhat comfortable that it is being propagated properly.

Mail Server and SMTP Configuration (Leopard Server)

Hello,
Our setup: Mac OS X SERVER 5.2 - LEOPARD SERVER
PowerPC G5
Orange Internet connection via a router / DHCP
We try to find such assistance in configuring your Mac book
OS Server at your service.
We set our server with a local area "domaine.intranet"
We created users with the interface, and have an address
"[email protected]."
Our messaging system works internally with the client MAIL.
We also have an Internet domain "domaine.fr", this area is hosted
In online.net.
We have personal e-mail addresses such as "[email protected]" always
Hosted by online.
We can check our e-mails via the client MAIL by IMAP.
However, we do not send emails to the outside world, and especially
"Domaine.fr" or "[email protected]."
In the console admin Server:
-- LETTERS: we have turned the SMTP protocol allowing mail
Entrant, authorizing "Relayer outgoing mail over the host:
Smtp.orange.fr "
At the tab relay, we leave the config classic 127.0.0.0 / 8
And 192.168.1.0/24.
In the history of mail, there are "postfix / postfix-7563]: fatal: the
Postfix mail system is not running, why then that the service operates on
Priori!
How can I be able to send emails to the outside knowing that we
Use addresses' [email protected]. "
Please tell us a direction to follow or procedure.
Sincerely,
ORIGINAL IN FRENCH
Notre configuration : Mac OS X SERVER 5.2 - LEOPARD SERVER
PowerPC G5
Connexion internet orange via un routeur/DHCP
Nous avons essayer de trouver cette aide à la configuration dans votre livre Mac
OS Server à votre service.
Nous avons configuré notre serveur avec un domaine local en "domaine.intranet"
Nous avons créé des utilisateurs à l'aide de l'interface, et avons une adresse
"[email protected]".
Notre système de messagerie fonctionne en interne avec le client MAIL.
Nous avons également un domaine internet "domaine.fr", ce domaine est hébergé
chez online.net.
Nous avons des adresses mail personnel du type "[email protected]" toujours
hébergé chez online.
Nous pouvons consulter nos emails via le client MAIL par IMAP.
Par contre, nous n'arrivons pas à envoyer des emails à l'extérieur, et notamment
sur "domaine.fr" ou "[email protected]".
Dans la console d'admin Serveur :
- COURRIER : nous avons activé le protocole SMTP en autorisant le courrier
entrant, en autorisant "Relayer le courrier sortant via l'hôte :
smtp.orange.fr"
Au niveau de l'onglet relais, nous avons laisser la config classique 127.0.0.0/8
et 192.168.1.0/24.
Dans l'historique de courrier, il y a "postfix/postfix-script[7563]: fatal: the
Postfix mail system is not running", pourquoi alors que le service fonctionne à
priori !
Comment faire pour pouvoir envoyer nos emails à l'extérieur sachant que nous
utilisons les adresses "[email protected]".
Merci de nous indiquer une direction à suivre ou une procédure.
Cordialement,
Message was edited by: serveurbense

Hello,
Thanks for the reply.
I modified according to your advice and tried to send mail, but it does only internally. My mail.log gives me the following information:
Apr 21 10:59:30 domaine postfix/smtp[4521]: 46D302308BE: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.84]:25, delay=0.27, delays=0.05/0.01/0.16/0.05, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.84] said: 554 <[email protected]>: *Recipient address rejected: Missing Authentication (in reply to RCPT TO command))*
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 2147323090F: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 022FF230937: to=<[email protected]>, relay=cyrus, delay=0.28, delays=0.01/0.04/0/0.23, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: *Sender address rejected: Domain not found (in reply to MAIL FROM command))*
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: Sender address rejected: Domain not found (in reply to MAIL FROM command))
Apr 21 11:00:27 domaine postfix/cleanup[4600]: 602A423094E: message-id=<[email protected]>
Apr 21 11:00:27 domaine postfix/bounce[4612]: 022FF230937: sender non-delivery notification: 602A423094E
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: from=, size=3531, nrcpt=1 (queue active)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 022FF230937: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 602A423094E: to=<[email protected]>, relay=cyrus, delay=0.06, delays=0.01/0/0/0.05, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: removed
Apr 21 11:01:10 domaine postfix/postfix-script[4664]: refreshing the Postfix mail system
Apr 21 11:01:10 domaine postfix/master[2938]: reload configuration /etc/postfix
Apr 21 11:01:26 domaine postfix/smtpd[4516]: disconnect from domaine.intranet[192.168.1.11]
Apr 21 11:02:10 domaine postfix/postfix-script[4734]: refreshing the Postfix mail system
I am looking for solutions to correct mistakes 553 and 554, hoping that this will allow us to send mail out.
Do you have any other suggestions?
Thank you.
Bonjour
merci pour la réponse.
J'ai modifié selon vos conseils et essayé d'envoyer des mails, mais ça ne marche qu'en interne. Mon mail.log me donne les informations suivantes:
Apr 21 10:59:30 domaine postfix/smtp[4521]: 46D302308BE: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.84]:25, delay=0.27, delays=0.05/0.01/0.16/0.05, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.84] said: 554 <[email protected]>: *Recipient address rejected: Missing Authentication (in reply to RCPT TO command))*
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 2147323090F: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 022FF230937: to=<[email protected]>, relay=cyrus, delay=0.28, delays=0.01/0.04/0/0.23, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: *Sender address rejected: Domain not found (in reply to MAIL FROM command))*
Apr 21 11:00:27 domaine postfix/smtp[4606]: 022FF230937: to=<[email protected]>, relay=smtp.orange.fr[193.252.22.86]:25, delay=0.31, delays=0.01/0.04/0.18/0.08, dsn=5.0.0, status=bounced (host smtp.orange.fr[193.252.22.86] said: 553 <[email protected]>: Sender address rejected: Domain not found (in reply to MAIL FROM command))
Apr 21 11:00:27 domaine postfix/cleanup[4600]: 602A423094E: message-id=<[email protected]>
Apr 21 11:00:27 domaine postfix/bounce[4612]: 022FF230937: sender non-delivery notification: 602A423094E
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: from=, size=3531, nrcpt=1 (queue active)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 022FF230937: removed
Apr 21 11:00:27 domaine postfix/pipe[4608]: 602A423094E: to=<[email protected]>, relay=cyrus, delay=0.06, delays=0.01/0/0/0.05, dsn=2.0.0, status=sent (delivered via cyrus service)
Apr 21 11:00:27 domaine postfix/qmgr[4582]: 602A423094E: removed
Apr 21 11:01:10 domaine postfix/postfix-script[4664]: refreshing the Postfix mail system
Apr 21 11:01:10 domaine postfix/master[2938]: reload configuration /etc/postfix
Apr 21 11:01:26 domaine postfix/smtpd[4516]: disconnect from domaine.intranet[192.168.1.11]
Apr 21 11:02:10 domaine postfix/postfix-script[4734]: refreshing the Postfix mail system
Je cherche des solutions pour corriger les erreurs 553 et 554, espérant que cela nous permettra d'envoyer des mails à l'extérieur.
Avez-vous d'autres propositions?
Merci d'avance.

SAP Content Server and DMS configuration

Hello,
I need help in configuring the relation between DMS and SAP Content Server. I need to make documents to be stored in a Content Server Repository and can't see clearly how to configure it from SPRO transaction.
Thanks!
Patricia

Hello,
can you tell as the solution for this problem please?
i got the some error message - but only on one server?!
the note 925327 dosn't help's
thank you
thomas berger

NAC guest server and pre-configured duration of accounts

There seems to be a bug in the way the NAC guest server handles the pre-configured duration of guest accounts.
I have followed the manual and I did:
- Configured 3 durations (24h, 48h and 1 week) under the templates/accounts/accounts durations.
- And set "maximun duration of account" under User Groups
As I understand I should now be able to select one of the three configured durations when I login as a sponsor.
However I only get the number which I specified under User Group.
The odd thing is that if I change the Maximum duration under User Group, I get this as the only choice (e.g. 14 days).
Have other experienced this?
Best regards,
Steffen Lindemann

You can use any one of the option ie number of days or number of hours.
For days;
Authentication > User Groups > Add Group | Edit Group includes two new settings for Number of days in the future the account can be created and Maximum duration of account (in days)
For hours:
User Interface > Templates > Add Template | Edit Template > Accounts > Account Duration
http://www.cisco.com/en/US/docs/security/nac/guestserver/release_notes/11/gsrn110.html

Update to 10.9.1 whips out Server and Apple Configurator Settings

I just updated my mac Mini Server that was already running Mavericks and Server App. When the reboot was done and I started the server is was like I had just installed the app. All the cache and settings were gone. Went to use Apple Configurator. Same thing. All profiles and managed devices and groups are gone. Is there anyway to get these configurations back?

Actually, this is an id10T mistake. I rebooted to the wrong hard drive. Please disregard this problem. It is solved.

ICal server and external invitations via 3rd party mail server

Hi everyone,
OS 10.6.5 Server:
Services running
AFP
DNS
iCal
Open Directory
Push Notification
We are currently testing iCal server and have configured it to send out invites via our mail server (which is running on a different server) by creating the com.apple.calendarserver user on our mail server.
Email notifications are then configured under the Enable Email Invitations tab in the iCal service of Server Admin as follows:
IMAP
Email address: [email protected]
Incoming server: mail.mytest.com
Port: 143 (not using SSL)
Username: com.apple.calendarserver
Password: secret
SMTP: mail.mytest.com
Port: 25 (not using SSL)
Server requires authentication
Username: com.apple.calendarserver
Password: secret
My test OD users are able to send out invites both internally to other iCal users and externally via email.
So for example, I invite someone to a meeting and enter their gmail address ([email protected]), the invitation goes out correctly - when I log into gmail I see the invitation.
When responding to the invitation (clicking Yes), the mail server receives the response from gmail and the iCal server collects the message via IMAP.
However, the iCal server doesn't seem to parse the received email correctly as I get the following error in the iCal error logs:
[twistedcaldav.extensions#info] Cannot authenticate proxy user 'com.apple.calendarserver' without X-Authorize-As header
2011-03-03 17:44:03+1100 [-] [mailgateway] 2011-03-03 17:44:03+1100 [AuthorizedHTTPGetter,client] [twistedcaldav.mail#error] Mail gateway failed to inject message <[email protected]> (Reason: 400 Bad Request)
2011-03-03 17:44:03+1100 [-] [mailgateway] 2011-03-03 17:44:03+1100 [AuthorizedHTTPGetter,client] [twistedcaldav.mail#debug] Failed calendar body: BEGIN:VCALENDAR
2011-03-03 17:44:03+1100 [-] [mailgateway] VERSION:2.0
2011-03-03 17:44:03+1100 [-] [mailgateway] CALSCALE:GREGORIAN
2011-03-03 17:44:03+1100 [-] [mailgateway] METHOD:REPLY
2011-03-03 17:44:03+1100 [-] [mailgateway] PRODID:-//Google Inc//Google Calendar 70.9054//EN
2011-03-03 17:44:03+1100 [-] [mailgateway] BEGIN:VEVENT
2011-03-03 17:44:03+1100 [-] [mailgateway] UID:43121576-1183-40C8-82D8-A052754AD1CE
2011-03-03 17:44:03+1100 [-] [mailgateway] DTSTART:20110406T080000Z
2011-03-03 17:44:03+1100 [-] [mailgateway] DTEND:20110406T090000Z
2011-03-03 17:44:03+1100 [-] [mailgateway] ATTENDEE;[email protected];CUTYPE=INDIVIDUAL;PARTSTAT=DECLINED;RO
2011-03-03 17:44:03+1100 [-] [mailgateway] LE=REQ-PARTICIPANT;X-NUM-GUESTS=0:mailto:[email protected]
2011-03-03 17:44:03+1100 [-] [mailgateway] CREATED:20110303T062518Z
2011-03-03 17:44:03+1100 [-] [mailgateway] DESCRIPTION:
2011-03-03 17:44:03+1100 [-] [mailgateway] DTSTAMP:20110303T064335Z
2011-03-03 17:44:03+1100 [-] [mailgateway] LAST-MODIFIED:20110303T064335Z
2011-03-03 17:44:03+1100 [-] [mailgateway] LOCATION:
2011-03-03 17:44:03+1100 [-] [mailgateway] ORGANIZER;CN=com.apple.calendarserver+07b1c044-9d98-4cdc-afe3-48139218ee35
2011-03-03 17:44:03+1100 [-] [mailgateway] @mytest.com:urn:uuid:B72794FB-3242-48D7-AC22-A584D279B9F9
2011-03-03 17:44:03+1100 [-] [mailgateway] SEQUENCE:3
2011-03-03 17:44:03+1100 [-] [mailgateway] STATUS:CONFIRMED
2011-03-03 17:44:03+1100 [-] [mailgateway] SUMMARY:one more test
2011-03-03 17:44:03+1100 [-] [mailgateway] TRANSP:OPAQUE
2011-03-03 17:44:03+1100 [-] [mailgateway] END:VEVENT
2011-03-03 17:44:03+1100 [-] [mailgateway] END:VCALENDAR
2011-03-03 17:44:03+1100 [-] [mailgateway]
I have set a rule on our mail server to bypass any spam filtering for all messages sent to the [email protected] address, but this doesn't seem to make any difference.
Does anyone else have this working ? Any ideas ?
Many thanks
Message was edited by: gen_bunty
null

The issue is not "user authorization". The issue is that the 3rd-party service does not accept all incoming relay requests unless there is authentication with a registered account (which we have). This protects the 3rd-party service from becoming the relaying host for the universe's spoofed and anonymous spam. My deduction is that there is no mechanism in UTL_MAIL to designate not only the 3rd-party ip-address:port (by-passing the local sendmail server) but also providing the username:password for the account there for authentication.
Plan A: I have attempted to follow directions for client-side SMTP Authentication for Relaying on the sendmail.org site.
I have not been successful in completing a simple mailx interactive test, much less completing a UTL_MAIL configuration.
I am scouring the user universe for someone who has put all the pieces together successfully and can advise. . . .
Edited by: StevenInTallyFl on Mar 26, 2010 3:50 PM
to clarify that I cannot get from UTL_MAIL to 3rd-party IP directly

Integrating Messaging Server and Identity Server

I've got JES 2004Q2, and I'm trying to install the various components on different workstations to prove that a) the software works, and b) it's a viable alternative to Exchange (so please please help me get it working!)
The problem I have is getting Messenger Server and Directory Server talking properly so that I can create users and then log in as those users. After days of frustrating searching for solutions to this problem (and also find people who have successfully done this), I decided to install the components onto one server.
And it worked. Installing Messaging Server, Identity Server, Web Server (contained for Identity Server), Directory Server, and Admin Server all on the same box, configuring them all to use the same directory server for UG and preferences, running the various configuration tools that come with the software, and it all works together fine. Using "./commadmin domain modify .... -S mail", I get "OK". I can add users with the "-S mail" option, log in as those users, and send emails between those users. So this tells me that the software does work, albeit on one box.
When I try to separate the services out to separate boxes, they don't seem to integrate properly. I thought that maybe the order in which you configured applications made a difference (ie. configuring Identity Server after Messenger Server means IS will pick up on the changes made to the directory by MS, and enable it). I also tried to see if using the same options directory server from different boxes helped, but nothing. I've even tried patching them using 116568-52 and 116585-10 but no luck.
Therefore, I've found that installing all servers on one box works, but installing them on separate boxes doesn't (despite using the same directory servers). My conclusion in this is that one of two things must be the case:
a) there's something in the install that has to be changed to reflect the fact that the services are running on different boxes
b) the install of the services adds files to the system somewhere which other packages in JES pick up on (hence the reason why installing everything on one box works), and this isn't documented anywhere
Unfortunately, the output of commadmin when it fails isn't that helpful (nothing against the developers, however it doesn't really help in the fault finding process). I do believe however that the problem is with Identity Server and its configuration, rather than Messaging Server.
Here's some (possibly) useful info:
kipling# ./imsimta version
Sun Java(tm) System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004)
libimta.so 6.1 HotFix 0.01 (built 12:52:04, Jun 24 2004)
SunOS kipling 5.8 Generic_117350-02 sun4u sparc SUNW,Sun-Blade-1500
kipling#
(on UG server)
# ./commadmin domain modify -D admin -w <password> -d uwe.ac.uk -n uwe.ac.uk -S mail -H kipling.uwe.ac.uk
FAIL
Unable to set attribute(s)
(some verbose mode output)
[Debug]: Contacting : http://bronte.uwe.ac.uk:10080/commcli/TaskManager
[Debug]: To servlet: task=ModifyDomain&objecttype=Domain&domain=uwe.ac.uk&add_services=mail&add_preferredmailhost=kipling.uwe.ac.uk
[Debug]: RECV: FAIL
[Debug]: RECV: Unable to set attribute(s)
[Debug]: CLITask: status returned =FAIL
FAIL
Unable to set attribute(s)
[Debug]: DBG: doOne returned code=6
[Debug]: Contacting : http://bronte.uwe.ac.uk:10080/commcli/logout
[Debug]: Logout ...
[Debug]: RECV: SSOToken id AQIC5wM2LY4SfcyW5hbVBGXqCdsYYDjVarSFRMd6HIxsGho=@AAJTSQACMDE=#
[Debug]: RECV: destroyed
Root suffix: dc=uwe,dc=ac,dc=uk (all "o=" references have been dropped)
All services have their own local options directory server.
Can anyone give me any suggestions? If I log a support call with Sun, what is the likely resolution time? My ultimate goal is to get the whole suite running together, then install Portal server. Once that's working, download the connectors for Outlook and get it all working with Outlook. As I said at the start, we're hoping to show this is a viable alternative to Exchange (certainly for the backend) so any help will be greatly appreciated!
Iain

slo_chewie wrote:
Does the email recipient address change when the email is sent to gmail i.e. does an email sent to [email protected] become [email protected]?
We've got google for domains setup, so users would retain a @domain.com address regardless if there mailbox was hosted on the internal server or hosted at google.You can make use of the mailRoutingAddress: user attribute and source routing to get the desired behaviour e.g.
=> Set the following value to the LDAP entry of the user who is hosted on the gmail server. The "[email protected]" address should match the users mail: address:
mailRoutingAddress: @gmail.com:[email protected]=> Ensure the following option has been tcp_local channel in your imta.cnf file. This option strips off the "@gmail.com" value of the recipient address before sending the email to the gmail.com servers.
dequeue_removerouteMake sure you run "./imsimta cnbuild;./imsimta restart" after modifying the imta.cnf file.
Regards,
Shane.

Ethernet to Server to AE configuration

Hi,
I'm trying to configure MacOSX Server using NAT as I have one fixed IP and about 6 clients to connect (wirelessly). The server software is already installed, so I am trying to add a server and to configure it to serve a wireless network provided by an Airport Extreme (A/E). I have read the manuals, "Getting Started v10.6.pdf" and "Network_Services_Admin_v10.6.pdf", yet I find I cannot connect to the Internet. What am I doing wrong? Here's what I have done....
I am doing everything locally. I follow "Network_Services_Admin_v10.6.pdf" on page 133 "Linking a LAN to the Internet Through One IP Address" I connect the ethernet to port 1 (en0) on my server. I then connect my A/E to en1. I begin by setting up the A/E with Airport Utilities to provide a wireless network. I have Sys. Preferences open and it tells me that ethernet 1 (en0) has a self assigned IP address (ok), same with en1 and en2. I then need to change the settings on ethernet 1 (en0). I choose to configure manually and I enter the fixed IP into the box, 137.x.x.x, subnet mask 255.255.255.0, router 192.168.1.1
(I am only sure about the IP address here, why I need a router number makes no sense to me. I am only going by the fact that there is normally a router number in the Network pane when I am connected to the internet with my own computer). Anyway, I go ahead and start Server Admin, I 'add server' name.com (again I'm guessing this is the right form to go here and not name.local or something else). I then sit back and wait for the serial number to appear. I then save and connect to the server. I then navigate to "services" and see everything box is ticked, so I expand the arrow beside name.com and click NAT...I follow the manual...so I choose ethernet 1 as my WAN gateway, then Ethernet 2 as my LAN (I think this is correct although I had my doubts since I have the A/E connected to Ethernet 2 and this will eventually be what the clients wil connect to). So I could chose both Ethernet 2 and Airport as my LAN but I just stick to the manual and pick ethernet 2. It then does its thing and back over in Sys Preferences both Ethernet ports are reporting being connected. Ethernet 1 has the fixed IP I gave it, Ethernet 2 has gone from DHCP to manual and it has configured itself with a 192.x.x.x address...all seems ok. The Airport also has a 192.x.x.x address.
Somehow I have gone wrong?...No internet. Have I left out a router number? The subnet mask numbers are different for ethernet 1 and 2; should they be the same? Is there something else I am overlooking. I have checked the firewall, which is reporting it is on?
I'm lost...:(

When I start up Server Admin and want to add a server I am asked for an address, username and password. Is the address the full public address as in example.place.com or just example.local?
You can use any hostname or IP address that maps to this server. You can use its .local hostname too - any of them should work.
Does it matter in what order I set things up?
Sort of.
Changing the IP address of a server in production is a PITA, so spend some time to get that right first before you start configuring services.
Should I setup the Airport (in bridge mode) first, then the Network Preferences en0 (DHCP with manual address), then start Server Admin and let NAT do everything else?
You're setting this up in the 'wrong' way - the right way is to use the base station as your gateway but if you really, truly, absolutely have to use the Mac as the gateway then so be it, but I'd really explore that option first - it will be easier and more secure to use the base station as the gateway. So if that really is the case:
Ignore the base station. it's irrelevant at this point.
Connect the wall socket to en0
Configure the server en0 with the public address (137.x.x.x/255.255.255.0) with the router address as provided by the network admins
Connect en1 to one of the LAN ports on the AirPort Extreme
Configure en1 with the LAN address (192.168.x.x/255.255.255.0). Since you're not routing over this interface, just using NAT there is no need to set a router address (even though Server Assistant may complain)
Configure the base station with a LAN address (192.168.x.x/255.255.255.0) with the router address set to the Mac's LAN address.
Configure the base station to be a simple wireless bridge (not a router)
Now you can enable the NAT service on the server.
Nowhere, ever, at any time will you ever, ever use DHCP with Manual Addressing. Ever.
Now you can connect the other LAN devices to either the additional LAN ports on the base station, or wirelessly. Clients can be configured either Manually (using a 192.168.x.x address) or to use DHCP to get an address from the server.

Integrating SOA and Peoplesoft: Configuring JMSTARGET Connector in IB.

Hi All,
I have created JMS queue/topic in oracle application server. Can anybody idea how can we configure JMS connector of peoplesoft integration broker.
Let me first explain my requirement, I am working in peoplesoft outbound interface design with SOA integration.
So my approach will be creating JMS queue in oracle application Server and then configuring this JMS to any node of peoplesoft IB.
Then extracted information from peoplesoft need to send to the above node so that once the node receive the message it should
populate the JMS queue inturn SOA BPEL will be triggered to write into third party file/database.
Please give your inputs on this approach if you any other suggetion for peoples soft outbound integration with SOA.
Thanks inadvance.

Its published, but somehow you are unable to see it..issues with Meatlink for sure..
Here is its content :
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version: 8.4 - Release: 8.4
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 201077819
Symptoms
Please see below.
Cause
Not Applicable
Solution
<<Document:664816.1>> E-IB: Configuring Integration Broker with IBM MQ on AIX
SPECIFIC TO: Enterprise, PeopleTools, Integration Broker Release 8.49
ISSUE:
How to setup Integration Broker to PUT messages to an IBM MQ Server on a remote machine?
SOLUTION:
<See attachment for documentation with screenshot examples.>
Configuring Integration Broker with IBM MQ on AIX
The following guide is intended to outline the setup between Peoplesoft Integration Broker and IBMs Websphere MQ version 6 client on AIX. Note: This is not a certification, but a working example, specifically using the MQ client to connect to a remote machine running the MQ server.
Platform Information:
PeopleSoft PeopleTools 8.49
IBM Websphere MQ Release 6
AIX
Steps
1) Install and IBM Websphere MQ (WMQ) client
2) Configure WMQ connection
3) Configure Peoplesoft
4) TEST using PING and a Peoplesoft message to PUT data onto the WMQ server
Steps
1) Install and configure Websphere MQ client on AIX where Peoplesoft is located
NOTE: This is one optional architecture. It is also possible to install Peoplesoft and MQ on the same server, which avoids the client software altogether.
a. IBM deliveres an MQ client that is installed on the same box as the Peoplesoft with the following options.
i. Installed to /usr/mqm, all objects owned by local user mqm
ii. Ensure that the MQ Extended Transactional Client is installed
1. This includes com.ibm.mqetclient.jar file
iii. Mq specific environment variables
1. $MQ_JAVA_DATA_PATH=/usr/mqm
2. $MQ_JAVA_INSTALL_PATH=/usr/mqm/java
3. $MQ_JAVA_LIB_PATH=/usr/mqm/java/lib
4. jms.jar, fscontext.jar, jndi.jar, providerutil.jar, stcjms.jar
iv. CLASSPATH
1. Includes the following MQ jar files
i. com.ibm.mqetclient.jar
ii. providerutil.jar
iii. com.ibm.mqjms.jar
iv. ldap.jar
v. jta.jar
vi. jndi.jar
vii. jms.jar
viii. connector.jar
ix. com.ibm.mq.jar
2. Example
a. > echo $CLASSPATH
i. echo $CLASSPATH /usr/mqm/java/lib/com.ibm.mqetclient.jar:/usr/mqm/java/lib/providerutil.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/ldap.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/fscontext.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib:/usr/mqm/java/bin
3. When setting up Peoplesoft, add these jar files to the classpath setting in the setenv.sh file and reboot PIA
2) Configure WMQ
a. Edit JMSAdmin.config (located in /usr/mqm/java/bin)
ii. Set Initial Context Factory = com.sun.jndi.fscontext.RefFSContextFactory
# The following line specifies which JNDI service provider is in use.
# It currently indicates an LDAP service provider. If a different
# service provider is used, this line should be commented out and the
# appropriate one should be uncommented.
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
iii. Set PROVIDER_URL=file:/usr/mqm/java
# The following line specifies the URL of the service provider's initial context. It currently refers to an LDAP root context. Examples of a file system URL and WebSphere's JNDI namespace are also shown, commented out.
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
PROVIDER_URL=file:/usr/mqm/java
#PROVIDER_URL=iiop://localhost/
b. Run JMSAdmin to setup queue and qcf to the MQ server
i. def qcf(PLAS160_QCF) HOSTNAME(GSPLVP006-VM2) PORT(1414) CHANNEL(SYSTEM.DEF.SVRCONN) QMANAGER(QM_gsplvp006_vm2) TRANSPORT(CLIENT)
ii. NOTE: When connecting from a client to a remote server, it is important to specify the hostname, port and transport along with the other values.
iii. def q(PLAS160_Q) queue(PLAS160_Q)
1. Note: The q is a local naming alias, whereas the queue is the physical queue name on the MQ server
iv. Screenshot:
v. This creates a .bindings file
vi. NOTE: It is also possible to use IVTSetup for this, but JMSAdmin is recommended.
vii. NOTE: It is possible to gain a .bindings file from your MQ server administrator. Be sure that this format is correct, and the location on the client is referenced correctly.
viii. JMSAdmin can also be used to determin what connections are available from this machine using command dis ctx as shown
b. Optional: Test the connection to the MQ server using IBM software.
NOTE: Testing the ivtQ and ivt QCF can be accomplished using the IVTRun program, provided that the ivtQ and ivtQCF have been setup in the .bindings file with the same available on the MQ server (some mq administrators do not enable this by default)
i. Example IVTRun, see Appendix 1
ii. Example .bindings file see Appendix 2
3) Configure PeopleSoft
a. Create an external NODE representing the target JMS queue
i. Example node, see appendix 3
b. Setup the connectors properties for the new node
i. Use the connector ID= JMSTARGET
ii. Example properties screenshot, see Appendix 4
1. Notes
a. JMSProvider is MQSeries
b. JMSFactory, JMSQueue are those specified in the .bindings file representing that on the JMS server. In this case, PLAS160_QCF and PLAS160_Q are used for this example.
c. JMSUrl is the location of the working .bindings file on the web server (in this case file:/D:/apps/IBM/WebSphereMQ/Java )
c. Setup Gateway Properties
i. Access the Gateway Properties using PIA and add the JMS information for MQSeries to the integrationgateway.properties file as shown:
## JMS configuration Section
# <the following line is required>
ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
ii. Queue information here is only needed if going to GET message using the JMSListeningConnector. Not needed for the target PUT (or ping)
iii. Example integrationgateway.properties, See appendix 5
4) Test PUT connection from Peoplesoft to WMQ
1. Ping the JMS node from the node definition
b. Setup routings to PUT messages to the MQ node
i. Example using USER_PROFILE
ii. Submit the message and check the Operations Monitor
iii. Verify that the message made it to MQ (this is viewed by browsing the queue on the Websphere MQ Explorer, message browser. A better utility is rfhutil which is included in the MQ windows client development kit)
NOTE: This document is intended for 1 way communication TO Mq from Peoplesoft. Setup for GET using the JMSListeningConnector is a separate topic for documentation.
Appendix 1 IVTRun
Appendix 2 .bindings file.
NOTE: The PLAS160_QCF and PLAS160_Q references are applicable to this example.
#This file is used by the JNDI FSContext.
#Wed Sep 17 11:43:13 PDT 2008
PLAS160_QCF/RefAddr/9/Type=SRC
PLAS160_Q/RefAddr/5/Encoding=String
PLAS160_QCF/RefAddr/13/Content=5000
PLAS160_QCF/RefAddr/3/Content=GSPLVP006-VM2
PLAS160_Q/RefAddr/8/Content=PLAS160_Q
PLAS160_QCF/RefAddr/13/Type=PINT
PLAS160_QCF/RefAddr/1/Type=TRAN
MYPUT/RefAddr/2/Content=-2
PLAS160_QCF/RefAddr/6/Encoding=String
PLAS160_QCF/RefAddr/17/Type=RINT
PLAS160_QCF/RefAddr/5/Type=CHAN
PLAS160_QCF/RefAddr/18/Encoding=String
PLAS160_Q/RefAddr/2/Content=-2
PLAS160_PUT/RefAddr/1/Encoding=String
PLAS160_QCF/RefAddr/20/Content=SYSTEM.DEFAULT.MODEL.QUEUE
PLAS160_PUT/RefAddr/3/Type=PER
MYPUT/RefAddr/6/Encoding=String
PLAS160_Q/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/8/Content=PLAS160_PUT
PLAS160_Q/RefAddr/6/Encoding=String
MYPUT/RefAddr/0/Type=VER
PLAS160_PUT/RefAddr/7/Type=FIQ
PLAS160_QCF/RefAddr/7/Encoding=String
MYPUT/RefAddr/4/Type=CCS
PLAS160_PUT/RefAddr/2/Content=-2
PLAS160_QCF/RefAddr/19/Encoding=String
PLAS160_PUT/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/2/Encoding=String
PLAS160_Q/RefAddr/3/Type=PER
MYPUT/RefAddr/8/Type=QU
MYPUT/RefAddr/7/Encoding=String
PLAS160_Q/RefAddr/7/Encoding=String
MYPUT/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_Q/RefAddr/7/Type=FIQ
PLAS160_QCF/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/6/Type=CCS
MYPUT/RefAddr/9/Content=
PLAS160_QCF/RefAddr/10/Type=SFIPS
PLAS160_QCF/RefAddr/10/Encoding=String
PLAS160_PUT/RefAddr/3/Encoding=String
PLAS160_QCF/RefAddr/20/Type=TM
MYPUT/RefAddr/8/Encoding=String
PLAS160_Q/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/14/Type=MBS
PLAS160_QCF/RefAddr/17/Content=5000
PLAS160_QCF/RefAddr/2/Type=QMGR
PLAS160_PUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
PLAS160_QCF/RefAddr/7/Content=\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
MYPUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
MYPUT/RefAddr/3/Content=-2
PLAS160_PUT/RefAddr/0/Type=VER
MYPUT/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/18/Type=TCM
PLAS160_QCF/RefAddr/9/Encoding=String
PLAS160_QCF/RefAddr/11/Content=false
PLAS160_QCF/RefAddr/1/Content=1
PLAS160_Q/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/11/Encoding=String
PLAS160_QCF/RefAddr/20/Encoding=String
PLAS160_PUT/RefAddr/4/Type=CCS
PLAS160_PUT/RefAddr/4/Encoding=String
PLAS160_QCF/RefAddr/14/Content=10
PLAS160_QCF/RefAddr/4/Content=1414
PLAS160_Q/RefAddr/9/Content=
MYPUT/RefAddr/9/Encoding=String
MYPUT/RefAddr/0/Content=6
MYPUT/RefAddr/1/Type=EXP
PLAS160_Q/RefAddr/9/Encoding=String
PLAS160_PUT/RefAddr/8/Type=QU
PLAS160_Q/RefAddr/0/Content=6
PLAS160_Q/RefAddr/0/Type=VER
MYPUT/RefAddr/5/Type=TC
PLAS160_Q/RefAddr/3/Content=-2
PLAS160_QCF/RefAddr/0/Encoding=String
PLAS160_PUT/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/21/Content=
PLAS160_Q/RefAddr/4/Type=CCS
MYPUT/RefAddr/9/Type=QMGR
PLAS160_QCF/RefAddr/21/Encoding=String
PLAS160_PUT/RefAddr/9/Content=
PLAS160_QCF/RefAddr/12/Encoding=String
PLAS160_PUT/RefAddr/5/Encoding=String
MYPUT/RefAddr/0/Encoding=String
PLAS160_Q/RefAddr/8/Type=QU
PLAS160_Q/RefAddr/0/Encoding=String
PLAS160_PUT/RefAddr/0/Content=6
PLAS160_Q/FactoryName=com.ibm.mq.jms.MQQueueFactory
PLAS160_PUT/RefAddr/3/Content=-2
PLAS160_QCF/RefAddr/7/Type=CT
PLAS160_QCF/RefAddr/1/Encoding=String
PLAS160_QCF/RefAddr/11/Type=SPAG
PLAS160_QCF/RefAddr/21/Type=TQPFX
PLAS160_QCF/RefAddr/13/Encoding=String
PLAS160_QCF/RefAddr/22/Encoding=String
PLAS160_PUT/RefAddr/6/Encoding=String
PLAS160_QCF/RefAddr/15/Type=FIQ
PLAS160_QCF/RefAddr/3/Type=HOST
MYPUT/RefAddr/1/Encoding=String
PLAS160_PUT/RefAddr/1/Type=EXP
PLAS160_QCF/RefAddr/19/Type=MNST
PLAS160_QCF/RefAddr/2/Encoding=String
PLAS160_PUT/RefAddr/5/Type=TC
PLAS160_QCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
PLAS160_QCF/RefAddr/14/Encoding=String
PLAS160_QCF/RefAddr/18/Content=true
MYPUT/RefAddr/2/Type=PRI
PLAS160_QCF/RefAddr/8/Content=0
MYPUT/RefAddr/4/Content=1208
MYPUT/RefAddr/2/Encoding=String
PLAS160_PUT/RefAddr/9/Type=QMGR
PLAS160_Q/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_Q/RefAddr/1/Encoding=String
MYPUT/RefAddr/7/Content=1
PLAS160_Q/RefAddr/1/Type=EXP
MYPUT/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/12/Content=true
PLAS160_QCF/RefAddr/2/Content=QM_gsplvp006_vm2
PLAS160_Q/RefAddr/7/Content=1
PLAS160_QCF/RefAddr/3/Encoding=String
PLAS160_Q/RefAddr/5/Type=TC
PLAS160_QCF/RefAddr/15/Content=1
PLAS160_QCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
MYPUT/RefAddr/1/Content=-2
PLAS160_PUT/RefAddr/7/Encoding=String
PLAS160_QCF/RefAddr/15/Encoding=String
PLAS160_Q/RefAddr/9/Type=QMGR
MYPUT/RefAddr/3/Encoding=String
PLAS160_Q/RefAddr/1/Content=-2
PLAS160_Q/RefAddr/2/Encoding=String
PLAS160_Q/RefAddr/4/Content=1208
PLAS160_QCF/RefAddr/8/Type=CTO
PLAS160_PUT/RefAddr/7/Content=1
PLAS160_QCF/RefAddr/22/Content=1
PLAS160_QCF/RefAddr/12/Type=UCP
PLAS160_QCF/RefAddr/0/Type=VER
PLAS160_QCF/RefAddr/4/Encoding=String
PLAS160_QCF/RefAddr/22/Type=MRET
PLAS160_QCF/RefAddr/16/Type=LA
PLAS160_PUT/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_QCF/RefAddr/4/Type=PORT
PLAS160_PUT/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/16/Encoding=String
PLAS160_PUT/RefAddr/1/Content=-2
PLAS160_PUT/RefAddr/4/Content=1208
PLAS160_Q/RefAddr/3/Encoding=String
PLAS160_PUT/RefAddr/2/Type=PRI
PLAS160_PUT/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/5/Encoding=String
MYPUT/RefAddr/3/Type=PER
PLAS160_PUT/RefAddr/9/Encoding=String
PLAS160_QCF/RefAddr/17/Encoding=String
MYPUT/RefAddr/4/Encoding=String
PLAS160_Q/RefAddr/2/Type=PRI
MYPUT/RefAddr/7/Type=FIQ
PLAS160_Q/RefAddr/4/Encoding=String
PLAS160_QCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
PLAS160_QCF/RefAddr/16/Content=
PLAS160_Q/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/6/Content=819
PLAS160_QCF/RefAddr/19/Content=true
PLAS160_QCF/RefAddr/9/Content=0
MYPUT/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/0/Encoding=String
MYPUT/RefAddr/8/Content=PLAS160_PUT
PLAS160_QCF/RefAddr/10/Content=false
MYPUT/RefAddr/5/Encoding=String
PLAS160_QCF/RefAddr/0/Content=6
Appendix 3 Node definition
Appendix 4 - Node JMSTarget Connectors Properties
Appendix 5 integrationgateway.properties JMS configuration section
## JMS configuration Section
#The JNDIFactory Classnames for Weblogic, IPlanet, MQSeries.
#ig.jms.JMSProvider.JNDIFactory.Weblogic=weblogic.jndi.WLInitialContextFactory
#ig.jms.JMSProvider.JNDIFactory.IPlanet=com.sun.jndi.fscontext.RefFSContextFactory
ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
#ig.jms.JMSProvider.JNDIFactory.OracleApplicationServer=com.evermind.server.rmi.RMIInitialContextFactory
# Enter the number of Queue listners to instantiate
#ig.jms.Queues=1
# For each queue specify the following properties
# Name
# Provider
# JMSFactory name (which is binded to the JNDI)
# MessageSelector (optional Message Filter)
# JNDI System File URL
# JMS User
# JMS Password
# Example :
#ig.jms.Queue1=QUEUE_VAS
#ig.jms.Queue1.Provider=MQSeries
#ig.jms.Queue1.JMSFactory=QCF
# ig.jms.Queue1.MessageSelector=
#ig.jms.Queue1.Url=file:/D:/apps/IBM/WebSphereMQ/Java
# ig.jms.Queue1.User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.Password=EncryptedPassword
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
#IBInfoHeaders
#ig.jms.Queue1.MessageName=QE_F18_ASYNC
#ig.jms.Queue1.MessageVersion=VERSION_1
#ig.jms.Queue1.RequestingNode=FromNode
#ig.jms.Queue1.DestinationNode=ToNode
# Use the supplied encryption utility to provide an encrypted password for the entry below
#ig.jms.Queue1.NodePassword=EncryptedRequestingNodePassword
#ig.jms.Queue1.SubChannel=SubChannel
# Enter the number of Topic Subscribers to instantiate
# ig.jms.Topics=1
# For each Topic specify the following properties
# Name
# Provider
# JMSFactory name (which is binded to the JNDI)
# MessageSelector (optional Message Filter)
# JNDI System File Url
# JMS User
# JMS Password
# Example :
# ig.jms.Topic1=ExampleTopic
# ig.jms.Topic1.Provider=MQSeries
# ig.jms.Topic1.JMSFactory=TopicConnectionFactory
# ig.jms.Topic1.MessageSelector=
# ig.jms.Topic1.Url=file:c:/
# ig.jms.Topic1.User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Topic1.Password=EncryptedPassword
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
#IBInfo Headers
#ig.jms.Topic1.MessageName=QE_F18_ASYNC
#ig.jms.Topic1.MessageVersion=VERSION_1
#ig.jms.Topic1.RequestingNode=FromNode
#ig.jms.Topic1.DestinationNode=ToNode
# Use the supplied encryption utility to provide an encrypted password for the entry below
#ig.jms.Topic1.NodePassword=EncryptedRequestingNodePassword
#ig.jms.Topic1.SubChannel=SubChannel
#For sending error either ErrorQueue or ErrorTopic must be configured
#If both exists, errors are only sent to ErrorQueues.
#Configure the Error-Queue configuration
# ig.jms.ErrorQueue=ErrorQ
# ig.jms.ErrorQueue-Provider=Weblogic
# ig.jms.ErrorQueue-User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.ErrorQueue-Password=sam
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
# ig.jms.ErrorQueue-JMSFactory=TopicConnectionFactory
# ig.jms.ErrorQueue-Url=file:c:/
#Configure the Error-Topic configuration
# ig.jms.ErrorTopic=Error
# ig.jms.ErrorTopic-Provider=IPlanet
# ig.jms.ErrorTopic-User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.ErrorTopic-Password=sam
# ig.jms.ErrorTopic-JMSFactory=TopicConnectionFactory
# ig.jms.ErrorTopic-Url=file:c:/
## End of JMS configuration Section
# Profile Information
# Set it to either TRUE or FALSE
ig.ProfileInformation=FALSE
#End-Of Profile Information
##EIPTestTool Properties
#Class name of the Gateway Manager to use during processing
#ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.EIPTestToolGatewayManager
#Contains a true or false value.
#True for LoopBack
#ig.EIPLoopBack=TRUE
#Contains the directory path that will be used
#to store request/response files during recording.
#ig.EIPOutputDirectory=c:/temp/output
# Number of ig.EIPMsgProp.N.propFile's
#ig.EIPMsgProp.count=0
#Certification root directory
#ig.EIPInputDirectory=c:/temp/input
#MessageProperty file names with locations.
#ig.EIPMsgProp.1.propFile=c:/temp/input/properties/pro1.xml
#ig.EIPMsgProp.2.propFile=c:/temp/input/properties/pro2.xml
#Overrides input directory for an EIP
#ig.EIPMsgProp.1.inputDirectory=c:/temp/input/properties1/
#EIPNodemapFileName
#ig.EIPNodeMap=c:/temp/nodemap.xml
##End of EIPTestToolProperties
#File connector password.
# Use the supplied encryption utility to provide an encrypted password for the entry below
ig.fileconnector.password=EncryptedPassword
#End of file connector properties.
## Query Access Services (QAS) Configuration Section.
# QAS Repository Home Directory. This is the directory where Query result blocks will be
# temporarily persisted.
# Example:
#ig.qas.repositoryHomeDir=C:/QASRepository
# Uncomment the following line and replace the value with the actual QAS Repository Home Directory.
#ig.qas.repositoryHomeDir=<Full-Path-For-Directory>
## END of QAS Configuration.
## AS2 Connector Properties.
# These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
# REQUIRED:
# AS2 KeyStore Properties
# Uncomment the following two lines to specify your key keystore path and password.
# Use the PSCipher.bat utility to encrypt the keystore password.
# example:
# ig.AS2.KeyStorePath=C://pt846//webserv//peoplesoft//keystore//pskey
# ig.AS2.KeyStorePassword=GD9klUFw8760HVaqeT4pkg==
# OPTIONAL:
# AS2 Log Directory, logs all incoming and outgoing AS2 requests and responses.
# Uncomment and specify the correct directory name to enable logging.
# example:
# ig.AS2.LogDirectory = c://temp//as2//logs
## End of AS2 Connector Properties
## AS2ListeningConnector Only Properties.
# OPTIONAL:
# AS2From and AS2To http header parameters are required on all incoming AS2 messages. These parameters must
# map to PeopleSoft node definitions either directly or indirectly via AS2 From & To map specifications.
# AS2 From & To Map
# This map translates incoming AS2From and AS2To http header parameters into PeopleSoft node names.
# This property is not required if your incoming messages use AS2From and AS2To parameters that match
# existing PeopleSoft node definitions.
# ig.AS2.AS2ListenerMap.From.<AS2From>= Specify the PSFT Source Node Name.
# ig.AS2.AS2ListenerMap.To.<AS2To>= Specify the PSFT Target Node Name.
# This example translate AS2From from AS2SENDER to PSFT_SRC_NODE, and AS2To from AS2RECEIVER to PSFT_TGT_NODE.
# example:
# ig.AS2.AS2ListenerMap.From.AS2SENDER=PSFT_SRC_NODE
# ig.AS2.AS2ListenerMap.To.AS2RECEIVER=PSFT_TGT_NODE
# AS2 Message name
# Message name used to publish AS2 transactions.
# Use this property if the incoming AS2 Message Name is not in the HTTP Header or the URL.
# Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters .
# when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
# AS2 From & To map above.
# ig.AS2.<source>.<target>.MessageName= Specify the Message Name
# example:
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.MessageName=AS2_ORDER_REQUEST
# These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
# REQUIRED:
# AS2 Certificates
# CertificateAlias is the certificate of the AS2 Listening Node used to decrypt incoming messages.
# SignerCertificateAlias is the certificate of the AS2From trading partner of Listening Node used to verify
# the incoming signature.
# Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters
# when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
# AS2 From & To map above.
# ig.AS2.<source>.<target>.CertificateAlias = Specify the target AS2 Listening Node certificate alias.
# ig.AS2.<source>.<target>.SignerCertificateAlias = Specify the source AS2From trading partner certificate alias.
# example:
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.CertificateAlias=<GeneratedAS2certificatealias>
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.SignerCertificateAlias=<GeneratedAS2certificatealias>
## End of AS2ListeningConnector Only Properties
## AS2 Target Connector Properties
# These Properties need to be set to use the AS2TargetConnector
# AS2 Original Request Information Log Directory
# This is required for Async MDN only. The Async MDN receiver uses this directory
# to find original request information.
# example:
# ig.AS2.AS2Directory=c://temp//as2
## END of AS2 Target Connector Properties.
#XML dtd lookup flag
# true - enable dtd reference lookup dtd on gateway. this is also the default value.
# false - disable dtd reference lookup on gateway.
ig.dtdLookup=true
# Maximum active connections to be cached on gateway
# These are connections from gateway to peoplesoft application server
# Caching connections will improve integration broker throughput
ig.connection=10
#####################

Start SLD server first ?????

Hi,
      I have logged into the SLD and tried to click Administration -> Content Maintanance.
      It is saying "Start the SLD server first"
   But the status of SLD is showing as "Running" on the top of the SLD page.
Please let me know if there is any other way to start the SLD.
Thanks
   Sourav

Hey,
Check scenario 3 : To start your local SLD Server, use your local SAP NetWeaver Administrator, connect your local J2EE Engine to report data to your SLD Server, and have several other J2EE Engines that report data to your SLD Server.
http://help.sap.com/saphelp_nw2004s/helpdata/en/23/b557422d095542e10000000a1550b0/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a0d7c290-0201-0010-bbaa-d8f8af341796
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Registration of systems in SLD and SMSY (Configuration of Managing System)

Hi folks,
I´m following this documentation here "How to Configure Maintenance Optimizer to Use Software Lifecycle Manager to Automatically Download and Deploy Support Packages and SAP Enhancement Packages" and on the pre-requisites are 2 things that i don´t uderstand:
1. The SLD server is running.
2. You are logged on to the Visual Administrator of the J2EE Engine as an administrator
what is it?

Oi Nelson
basicamente o documento diz para vc ter seu SLD configurado corretamente (ou seja, com todos dados do seu landscape atualizado - fundamental para gerar o arquivo XML de upgrade/support package stack apropriadamente) e para vc estar logado no Visual Admin com o usuário J2EE Admin :-)
Pelo tom de sua pergunta, imagino que vc não saiba ao certo o que é e para que serve SLD e Visual Admin. Aqui vão alguns links bem úteis:
http://scn.sap.com/docs/DOC-8042
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1870c690-0201-0010-fca0-b66794ea3ea3
http://help.sap.com/saphelp_nw70/helpdata/en/ee/74b3407e73c57fe10000000a1550b0/content.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/c46577095735b6e10000000a42189d/content.htm
e
http://help.sap.com/saphelp_nw70/helpdata/en/39/83682615cd4f8197d0612529f2165f/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/23/fa1f1e5f6841cf92c64dc19d79f290/content.htm
http://scn.sap.com/people/heidrun.reichart/blog/2006/11/24/how-to-use-sap-netweaver-administrator-with-sap-s-java-platform-enterprise-edition-5
Espero que isso ajude :-)
Abraços,
Tomas Black

SLD installation - easy and quick configuration to activate the SLD

Dear All,
I am installing a SLD in a separate server, base on AS-JAVA usage type.
I am reading guide from http://www.sdn.sap.com/irj/sdn/nw-sld.
After installing the SLD, I read that "You only have to perform the easy and quick configuration to activate the system landscape directory there. No further installation required, only quick configuration to activate SLD in a system."
My question :
Is there a guide to perform the easy and quick configuration" ?
Thanks for your input
Best regards
SAP NetWeaverAdmin

Hello,
When you define iit as SLD in the installation phase it should come as preconfigured.
All you need to do is check whether things are active and bring the system to latest CIM.
Then start adding other system to this new SLD as per standard method.
Once you finish the installation of the system http://hostname:5<instance number>00/sld needs to be run.
Check if that URL is active and in administration link check if the SLD is running.
That should be it.
Regards
Vivek

UME configuration : datasource and logonticket

Hello,
Can somebody explain me or give infos on UME configuration for logonticket and datasource for SAP R/3. System : ABAP/JAVA on the same stack (NW2004s).
Thanks
Best regards

Hi,
    For logon tickets please, refer the link below.
http://help.sap.com/saphelp_nw2004s/helpdata/en/e8/6bc22a4686714d963e9efb77cfbcb5/frameset.htm
For dataSource ABAP configuration, you need to set the following properties in the configtool
ume.persistance.data_source_configuration =    dataSourceConfiguration_abap.xml
r3.connection.master.ashost                       :       <Backend server name>
r3.connection.master.client                        :                  <Client id>
r3.connection.master.sysnr                       :                  <Backend system number>
r3.connection.master.user                          :                 <communication user name> (the sapjsf or communication user which we created in backend system)
r3.connection.master.password                 :                <communication user password> (it is the password of the com user which is in the backend system)
ume.login.guest_user.uniqueids     :           Guest user id     (same as Guest, createed in the backend system)
login.ticket_portalid               : yes (If administrator id length is more than 12 charcters ex: administrator)
                                                           : No (If administrator id length is less than 12 charcters ex: j2ee_admin)
Thanks
R.Murali

SLD server and UME configuration

Similar Messages

Maybe you are looking for